All~ > > Does ICU handle Unix, Windows, VMS and Palm OS? If not, we can't use > > it. (I figure if it handles those four, it's up to anything. :^) ) > > Well, we don't handle PalmOS right now anyway, so that's a moot point. > It handles the other three, and as I pointed out in my last post > defending ICU's use, it's even got build scripts for OS/400, so right > now it's more portable than Parrot. That's good enough for me.
Actually the Palm OS does not use Unicode. It has a strange mixture of single byte and two byte characters in a single stream that is in a different format. >From http://oasis.palm.com/dev/kb/manuals/1747.cfm : A given Palm OS device supports one language and one character encoding to represent the characters required by that language. Although the Palm OS supports multiple character encodings, a given device uses only one of those encodings. For example, a French device would probably use a character encoding similar to the Microsoft Windows code page 1252 character encoding (an extension of ISO Latin 1), while a Japanese device would use a character encoding similar to Microsoft Windows code page 932 (an extension of Shift JIS). Code page 932 is not supported on the French device, and code page 1252 is not supported on the Japanese device even though they both use the same version of Palm OS. No matter what the encoding is on a device, Palm guarantees that the low ASCII characters (0 to 0x7F) are the same. The exception to this rule is 0x5C, which is a yen symbol on Japanese devices and a backslash on all others. Matt
