Director uses bitmap fonts in its own Text editor window, and some of the
characters you're having problems with cannot be displayed there. In
non-antialiased text members, the situation is the same. In antialiased
text members, Director uses outline fonts, and in my experience, all
characters that display as boxes in the Text editor do display correctly in
antialiased text members. Is this what you're seeing?
As for embedded fonts crashing the movie when they are antialiased, I have
not seen that problem. I've only used a dozen different embedded fonts
(under all versions of 32-bit Windows and Mac), and they do use all
characters above decimal 127, including those slots that used to be called
"control" characters (those are the problematic ones)
You talk about poor support for non-1252 code pages in Director, but you
only cite the font display issue. Are there other issues that make your
work difficult? For example, the input process seems to be fine. I am able
to translate all keystrokes to above-127-decimal characters and display and
store them in casts. One character (decimal 194) cannot be used as a
character in string assignments in scripts: you have to use the numerical
value, like this:
strTest = strTest1 & NumToChar(194) & strTest2
Do you have other related problems?
Slava
At 09:56 AM 7/2/2001 +0200, you wrote:
>Im not see diacritics signs in Text Edit window. An biggest problem is sign
>ž ( its z with ˇ upper) . Im getting an box sign .. Not a correct
>character..
>Pytkin
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
