. . . . . . . . . . . . . . . . . . . . . . . . . . . till we *) . . .
Hi,
Actually, I think with the current setup, on en: at least, you can type them literally and when you hit submit or preview it'll automatically convert them to the numeric codes. I seem to recall this happening with some Greek text I pasted in (though I could be mistaken).
Yes, you are pretty wrong here. Some browsers actually change those codes to embeds (like Mozilla), which is *illegal*. There is not guarantee at the time of the POST that the server wants _HTML_ (or anyway else) encoded text, so the browser do a _wild_guess_, and pick the most used encoding.
I strongly disagree to cutting backward compatibility. But couldn't we find a technical solution, i.e.:
- storing everything in the database in UTF-8
- converting it automagically into embedded code (maybe even using HTML- entities like ü or ß) before an edit
- converting everything after the edit in UTF-8, including correct UTF8- characters inserted by the edit and embedded code
Best regards, __ . / / / / ... Till Westermayer - till we *) . . . mailto:till@tillwe.de . www.westermayer.de/till/ . icq 320393072 . Habsburgerstr. 82 . 79104 Freiburg . 0761 55697152 . 0160 96619179 . . . . .