This content has been marked as final. Show 3 replies
Solution found (at last!):
If you want to include texts in non-western language, don't stray too much with utf-8 encoding like I did. Just define ISO-8859-1 at the first line of the xml docuement ("<?xml encoding="ISO-8859-1" ?>") and save the document in the default encoding (ANSI). Oddly, it does the trick for other languages too. Strange5050 was right after all (see livedocs).
Director does not support UTF8 in the current version (MX2004 10.1.something)
In the next version (Dir 11) Adobe has promised that UTF8 will be fully supported.
There is still light in the end of the tunnel. The XML-parser supports UTF8 so you can read the UTF8 files but you cannot handle the strings after parsing.
After parsing director can only hande ISO-8859-1 (That is ASCII or as it is called in fonts the Western Latin)
Im not into hebrew that much but i guess they havent got more than 128 characters.
But this is the way to go if you cant wait for Dir11. I have been struggeling with this for a long time when i was making a multilanguage platform (Russian, Greek, Check, and so on)
First make a new ISO-8859-1 font with "ו" replaced with "A" and so on.
Now you have a conversionmap.
Search and replace all your hebrew xml externally in some software that
Replace all "ה" with "b" and so on.
Import your "abc-hebrew" into director and show it with your ISO-8859-1 font.
It's a bit of work but thats the easiest way to do it.
Remeber to save your "hebrew"-xml in ISO-8859-1 and not UTF8
Thank you the real POTMO. Apparently, we wrote a reply at the same time, so your answer is also the answer. You're right about the ISO-8859-1 (Latin 1) encoding & parsing, but I think I managed to import the texts without doing conversions. It just .... worked :)