WPIntell

Source evidence

Umlaute UTF-8

Recipe Schema · support · 2013-02-26T13:22:00+00:00

mixedsentiment
mediumseverity
0.72relevance
5replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

6 / 31 rows with source links

19.4% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

25 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
twenta resolved
Hi, thanks for the new version. It s so good now, that I want to use it for all my recipes, but the german letters like äöü are completely messed up, so there is some kind of coding problem. It would also be useful to be able to change words like “hours” or “min” for use in other languages. Cheers http://wordpress.org/extend/plugins/recipe-schema/ Thanks Twenta! I will have to go do some testing. I will be the first to admit that I didn’t test for UTF-8. Is that for ingredients or does it also happen in the directions and notes? I am trying to figure out if it is a database thing or something in the coding. I want to create a better system for the recipe templates and language. That might be a bit of work though. If you want to change it around, go into the file recipe-schema-client.php in the /wp-content/plugins/recipe-schema/inc/ directory and look at line 247. You can change the time there. I will work on a better system though. Hi, the transformation seems to take place in both cases (ingredients/directions) and takes place on insert into the db. All collations are utf8_general_ci btw. There must be some step where utf-8 is transformed into windows-1252 or similar… Thanks Thanks, I think I got a fix. I was doing some processing of the HTML in the Ingredients and Directions lists and I need to trick it into using UTF8. The changes are in the main recipe-schema.php files. I will make these changes in the code and get them upload soon. On line 927, it should be: $dom->loadHTML(‘<?xml encoding=”UTF-8″>’ . $ingredients ); On Line 959, it should be: $dom->loadHTML(‘<?xml encoding=”UTF-8″>’ . $directions ); The latest update should fix things, let me know if it doesn’t. Thanks for catching this! Thanks for the fix. I get confirm it works now 🙂

Comments

5 shown
Robotastic 2013-02-27T14:00:00+00:00

Thanks Twenta! I will have to go do some testing. I will be the first to admit that I didn’t test for UTF-8. Is that for ingredients or does it also happen in the directions and notes? I am trying to figure out if it is a database thing or something in the coding. I want to create a better system for the recipe templates and language. That might be a bit of work though. If you want to change it around, go into the file recipe-schema-client.php in the /wp-content/plugins/recipe-schema/inc/ directory and look at line 247. You can change the time there. I will work on a better system though.

twenta 2013-03-10T18:07:00+00:00

Hi, the transformation seems to take place in both cases (ingredients/directions) and takes place on insert into the db. All collations are utf8_general_ci btw. There must be some step where utf-8 is transformed into windows-1252 or similar… Thanks

Robotastic 2013-03-19T02:09:00+00:00

Thanks, I think I got a fix. I was doing some processing of the HTML in the Ingredients and Directions lists and I need to trick it into using UTF8. The changes are in the main recipe-schema.php files. I will make these changes in the code and get them upload soon. On line 927, it should be: $dom->loadHTML(‘<?xml encoding=”UTF-8″>’ . $ingredients ); On Line 959, it should be: $dom->loadHTML(‘<?xml encoding=”UTF-8″>’ . $directions );

Robotastic 2013-03-21T01:23:00+00:00

The latest update should fix things, let me know if it doesn’t. Thanks for catching this!

twenta 2013-03-21T03:26:00+00:00

Thanks for the fix. I get confirm it works now 🙂