View Single Post
Old 08-03-2003, 02:35 PM   #4
iSilo
Developer
iSilo knows what time it isiSilo knows what time it isiSilo knows what time it isiSilo knows what time it isiSilo knows what time it isiSilo knows what time it isiSilo knows what time it isiSilo knows what time it isiSilo knows what time it isiSilo knows what time it isiSilo knows what time it is
 
iSilo's Avatar
 
Posts: 33
Karma: 2314
Join Date: Oct 2002
Location: US
Font Silo™ supports only single-byte text encodings such as the windows-1252 Western European text encoding. If a document is specified to have any other encoding such as any of the UTF-8, Chinese, Japanese, or Korean text encodings, then the document displays with the device font even if you select installed fonts for the document.

Most Palm devices do not have UTF-8 support built-in, so if you see a bunch of question marks, then most likely your device either does not have UTF-8 support.

Recommendation is to set the output encoding to Windows-1252 when converting with iSiloX. If you are converting for Pocket PC or Windows, then UTF-8 will work across those platforms, but UTF-8 is very much not guaranteed to be compatible across all Palm OS verisons. When UTF-8 is encountered by iSilo and the OS does not provide support, iSilo can only display the values that are encoded within one byte. All other UTF-8 encoded characters come out as question marks. In general, if the source content was encoded using UTF-8 and contains only characters from the Windows-1252 character set, then setting the output encoding to Windows-1252 in iSiloX for conversion will give correct results. Characters in the Windows-1252 character set that have values greater than 128 are encoded using two or three bytes in UTF-8. To re-iterate iSiloX will correctly perform the transcoding from UTF-8 to Windows-1252.
iSilo is offline