Font/Punctuation Display

[JBJohnson]

I have several documents that I have created from html web sites using iSiloX that are not displaying the way I think they should on my device (Tungsten E). The text looks fine, but the punctuation (dashes, apostrophes) doesn't look right. It's almost like the characters aren't recongnized, so they display as question marks. I've double-checked the web sites, and everything looks OK there.

[iSilo]

By default, the converted document gets the same text encoding as the first source file.

If the first source file does not specify it's encoding, then it will be unknown and probably interpreted as plain 7-bit ASCII, with character values outside that range being unrecognized. In this case, you will need to specify the encoding explicitly. To change the default source encoding for an entry you created in iSiloX for conversion of a document, do this:

Right-click the entry to get the context menu.
In the context menu, click Properties. This gives you the Properties dialog for the entry.
In the Properties dialog, click the Document tab.
On the Document tab, click Text Encoding Options. This gives you the Text Encoding dialog.
In the Text Encoding dialog, set the For source files that do not specify their encoding, assume the following encoding field to Western European (Windows-1252) or whatever the source encoding is.
Click OK to accept the changes in the Text Encoding dialog.
Click OK to accept the changes in the Properties dialog.
After doing the above, reconvert.

If the above does not help, you may need to set the output encoding to what your device supports. For Western European language Palm OS devices, you should set the output encoding to Western European (Windows-1252). To change the output encoding for an entry you created in iSiloX for conversion of a document, do this:

Right-click the entry to get the context menu.
In the context menu, click Properties. This gives you the Properties dialog for the entry.
In the Properties dialog, click the Document tab.
On the Document tab, click Text Encoding Options. This gives you the Text Encoding dialog.
In the Text Encoding dialog, set the Output document text encoding field to Western European (Windows-1252) or whatever your device supports.
Click OK to accept the changes in the Text Encoding dialog.
Click OK to accept the changes in the Properties dialog.
After doing the above, reconvert.

The above instructions are for "iSiloX for Windows", but are pretty much the same for "iSiloX for Mac OS" except for the right-click part.

If the above suggestions do not help, please provide the URLs of the sites at issue.

[croberts@alum.mit.edu]

Here are some pages that have been giving me a problem:

http://library.lds.org/nxt/gateway.dll/Curriculum/music.htm/childrens%20songbook.htm?f=templates$fn=document-frame.htm$3.0$q=$x=

http://library.lds.org/nxt/gateway.dll/Magazines/Ensign/2005.htm/ensign%20august%202005.htm?f=templates$fn=document-frame.htm$3.0$q=$x=$nc=4021

They are all from the LDS.org website. I go 1 link deep. Any help you can provide would be appreciated.

Thanks,
Chris Roberts

[iSilo]

The encoding of the content appears to be "Windows-1252", however, there are at least three problems:

1. The web server that serves the content says it is UTF-8 encoded.
2. In the head portion of the HTML file, there is a meta content-type tag that says the content is UTF-8 encoded (e.g., <meta http-equiv="content-type" content="text/html;charset=utf-8">).
3. In the body portion of the HTML file, there is a meta content-type tag that says the content is ISO-8859-1 encoded (e.g., <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">).

All of the above are incorrect.

The lds webmaster or whoever is responsible for the content needs to correct the encoding description to be Windows-1252.