This content has been marked as final. Show 2 replies
The current version of Director does not support Unicode text. That is
one of the most requested features, and one that the good folks at Adobe
have stated will be a part of the next version of Director (which is
supposed to be released in the 2nd half of 2007.
Until that happens, there is no good way to make Director use extended
character sets natively. The standard work around is to put the text
into Flash and publish swf files that you can bring into Director.
Also, as you said, it is possible to use them if you turn the text into
bitmaps. Neither of those options are ideal, but until the next
Director version, that's about all we have.
Have a look at:
This includes both a new unicode rtf member, and a method to convert unicode
text to ansi text that director can display.
The text member can display any language and also supports embedding images.
The conversion will not work if the text includes multi-byte characters -
you'll be prompted if such characters exist.
So, try if it works for your docs, and then we'll see what we can do so that
> ..which means LOT of pain..
does not happen.
P.S. Hyperlink translation was not enabled in the Xtra version used by the
"Blade75" <email@example.com> wrote in message
> Hi everybody!
> I have some applications made with Director MX 2004, and I have to convert
> writings to polish language. I have the translations in a word .doc file,
> and I
> found out that when I paste the text into Director, the accented and
> polish letters don't display in Director correctly. It shows the empty
> or strange wrong characters, as it could not map the font correctly. I
> tried to
> embed the font, but it still does not work. At first I thought I messed up
> the font, as the font was manually edited to add the special letters (but
> font does work in every other application... photoshop, flash, word et
> But the problem remains even if I use/embed a "standard" window font like
> Times New Roman, Arial and so on. It seems that Director is refusing to
> correctly the font, even if I embed it entirely as full set.
> Now, is there a solution to this? Is it "normal"? Or have I to resign
> and convert all the text to images...which means LOT of pain :(
> Thank you in advance,