Character entities fail in UTF-8

[samalone@mac.com]

I started having a problem when I upgraded to iSiloX 4.0, and the problem seems to still be present in iSiloX 4.01b3.

I was converting a set of web pages that were in UTF-8 and contained character entities for things like the copyright symbol, trademark symbol, and left and right double-quotes. The character entities are corrupted during conversion if the web page is encoded using UTF-8. If I change the web page to use ISO-8859-1, then the character entities are converted correctly.

--Stuart

[iSilo]

How do you mean corrupted? Can you provide a specific webpage as an example?

Note that most Palm OS devices do not support display of Unicode encoded content, so did you try setting the output encoding to Western European (Windows-1252), which is equivalent to ISO8859-1, and which essentially all Western European languages Palm OS devices support?

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 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 is pretty much the same for "iSiloX for Mac OS" except for the right-click part.

[emceephd]

Hi,

I am not sure what the previous user (samalone@mac.com) is finding as corrupted but I am having the same issue.

My verison of "corrupted" is whenever there is a special character such as:

'
"
@

I get a:

?

Any ideas on why I might be getting this question mark instead of the correct symbol?

Again, I am getting this issue now that I have upgraded to version 4.0 and now 4.01b3.

Thanks!
Mike

[emceephd]

... I was able to make this work. I had not set both options to Western European (Windows - 1252). Thanks for the reply!!!

Mike