Me, too. I’m currently trying to figure out how to make WP (or is it Textile2?) not convert “accented characters” into HTML character entities. It’s really unnecessary.
I don’t know if this is the same problem, but how can I prevent entities like “½” from having the ampersand converted to an entity, killing the entity I was trying to manually enter? (I’m talking about when I write posts.)
Check out the following article in the WordPress Codex.
http://codex.wordpress.org/Writing_Code_in_Your_Posts
It should help you figure out how to keep the ampersand from being converted, by converting the ampersand into an entity.
½
As for foreign language issues, check http://codex.wordpress.org/WordPress_Localization
And to control on a global or per post basis how WordPress converts html and character entities and the quotes, you can use the Text Control Plugin.
Lorelle,
Thanks for the response, but it didn’t work. Making the ampersand into a & just pushed it back another level, and the ampersand in that one was literalized. WordPress seems to be converting the ampersand in the fraction entity to &.
It correctly interprets × and –, but not ½ I got around the problem by substituting &189; for ½ Seems like a bug though.
Took a look at this, and found there is a bug. Several lines in functions-formatting.php that are performing text replacements on the ampersand (for validation purposes), but aren’t correctly excluding entities mixing letters with numbers (I think there’s four of them, including the frac’s).
I’ll try and submit a patch, but for manually fixing this:
http://pastebin.com/296496
EDIT: Thanks forums for reminding me why I don’t post code here…
SECOND EDIT: Made a further refinement to character entity checking in my changes (Pastebin link updated).
