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?
OK, that clears things up. So my conclusion is correct: the Viewer currently only handles 8-bit encodings and ignores character set records in the metadata section. The character encoding in the document must match the encoding set on the device in order for the text to display correctly.
What is multibyte support about then? I found a reference to this in the archives, but it seems this is available in the I18N branch only. Unfortunately I still can't reach www.plkr.org or cvs.plkr.org to check this out.
Regards -Laurens
_______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
