> Anyway, I tried writing out text using UTF-8 and UTF-16 and the > documents all came out wrong in the Viewer. Actually I don't understand > how the Viewer handles different character encodings(if it does at all). > It displays different 8-bit encodings (Big-5, ISO-8859-2, KOI8-R) fine, > as long as the font set on the Palm matches the character set. But > variable-length encodings like UTF-8 or 16-bit encodings such as UTF-16 > do not seem to be supported.
It doesn't. The distiller tries to detect and communicate the encodings of particular parts, but given the abysmal PalmOS support for charsets and the non-existent Python 1.5.2 support, we can't do much with it. If we move to Python 2.x, we can manage the charsets, but what to do about the poor PalmOS support for them? Bill _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
