Hedin
03-03-2005, 06:33 AM
Hello.
I was trying iSilo (Palm) + iSiloX (Windows) and found one very annoying bug.
If links inside HTML-files contains non-latin letters (or other forbidden characters), iSiloX convert them in UTF-8 (two bytes per symbol), and then convert (every byte, not symbol) in "quoted-printable".
This behaviour results in error "Unable open file".
Paths with "incorrect" symbols processed correctly if specified, e.g. in Source list.
I think it will be better to not use UTF-8 strictly, but use encoding specified in meta-tags (and/or in Document Properties).
Software configuration:
- Windows 2000 SP4 English w/ Russian locale.
- iSiloX 4.2.
- XHTML-files in windows-1251 encoding, with not-escaped non-latin charaters in links (it doesn't matter - escaped or not).
I was trying iSilo (Palm) + iSiloX (Windows) and found one very annoying bug.
If links inside HTML-files contains non-latin letters (or other forbidden characters), iSiloX convert them in UTF-8 (two bytes per symbol), and then convert (every byte, not symbol) in "quoted-printable".
This behaviour results in error "Unable open file".
Paths with "incorrect" symbols processed correctly if specified, e.g. in Source list.
I think it will be better to not use UTF-8 strictly, but use encoding specified in meta-tags (and/or in Document Properties).
Software configuration:
- Windows 2000 SP4 English w/ Russian locale.
- iSiloX 4.2.
- XHTML-files in windows-1251 encoding, with not-escaped non-latin charaters in links (it doesn't matter - escaped or not).