Since version 3, new planes have been added to the original 16 bits code. At the origin, Unicode was fundmentally a 16 bits code.
>>You mean that you don't consider RFC's, W3C standards and IETF
Now look, I'm tired of people arguing just for the pleasure of contradicting others and pretending "what I mean".
This guy in this thread just asked "information can be entered in English or French in my case. What
do I need to do so that accents and whatnot are stored and displayed correctly?"
And my answer was "Nothing special."
Since 1995 I've been developing pages in French using Access 97 database and CF 1.1, none of them supported Unicode; like everybody else I was using the ISO standard (8859-1) which is the standard default character set used by all browsers anyway and I never had any problem. Just for your information ISO is ALSO an international standard, and it existed far before Unicode.
Unicode (or UTF-8 or UTF-64!) is a very powerful tool, if one wants to use it for French or even for English, he is free to do so, but to the question "what do I need", I'm sorry, I do not answer "You need to go Unicode".
If the guy asked "what do I need for Chinese" I would definitely have said "you should go Unicode*", but it was not the case.
* I know there are other codes for Chinese, so gimme a break!
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
