Hi,
I like it, but if we choose a non-UTF-8 language, display of many special characters becomes corrupted in the dropdown.
By the way, too bad that at this point (cookie-based login panel) we don't know the MySQL version, so we cannot decide to avoid displaying non-UTF-8 choices.... but now that MySQL 4.0.x can be considered old, why don't we reverse the logic and by default avoid to display non-UTF-8 choices?
Marc
Hi
On Fri 25. 11. 2005 16:50, Marc Delisle wrote:
I like it, but if we choose a non-UTF-8 language, display of many special characters becomes corrupted in the dropdown.
Eh, that's why there is htmlentities. Or it doesn't work as I expect? If not, we should put entities directly to array and don't rely on php functionality.
By the way, too bad that at this point (cookie-based login panel) we don't know the MySQL version, so we cannot decide to avoid displaying non-UTF-8 choices.... but now that MySQL 4.0.x can be considered old, why don't we reverse the logic and by default avoid to display non-UTF-8 choices?
Probably yes, however there still be some servers running older MySQL which will be harder to use in this case. This is first step to dropping non-UTF-8 translations.
Hi
On Fri 25. 11. 2005 17:11, Michal Čihař wrote:
On Fri 25. 11. 2005 16:50, Marc Delisle wrote:
I like it, but if we choose a non-UTF-8 language, display of many special characters becomes corrupted in the dropdown.
Eh, that's why there is htmlentities. Or it doesn't work as I expect? If not, we should put entities directly to array and don't rely on php functionality.
Done.
-
Marc Delisle -
Michal Čihař