There are two important reasons why code pages are still needed:
1) Many applications do not yet support Unicode, and those applications
still need to work properly (imagine trying to sell an OS where your
favorite apps would not install and run?).
2) Many people with whom you may want to communicate may not yet be using
Unicode -- so you have to be able to convert to connect to these other
It is present as a LEGACY feature, though. AT the heart of it all is
Unicode, at this point.
Trigeminal Software, Inc. -- http://www.trigeminal.com/
----- Original Message -----
From: "Chris Kavanagh" <firstname.lastname@example.org>
Sent: Wednesday, May 29, 2002 10:24 AM
Subject: Unicode vs Code pages
Please pardon my ignorance on the subject ...
I was wondering if someone could direct me to some (highly) technical
documentation of how code pages work, in particular to Windows systems? I
want to research/understand, exactly why there is still a need for code
pages given the existence of Unicode.
I have just started a full time position, fresh out of university, that
requires me to research localization on windows ce platforms. If this
platform is Unicode based, why is there a need for code pages?
I understand that code pages provide mappings of user inputs, but if
everything is Unicode, why is this necessary - since all characters in
Unicode are unique!
Information pertaining to the complete process, from input to font display
would be greatly appreciated.
I have been researching this and still do not have a solid answer, only
This archive was generated by hypermail 2.1.2 : Wed May 29 2002 - 12:31:49 EDT