>>there's an odd director behavior that i've found about lingo and letters
>>with accents, that i'd like you to confirm. that's the case:
>>i'm changing, from a behavior parameter, the member of a sprite, no big
>>deal; all the members used are text sprites, and if the name of the member
>>contains and accented letter AND the name is all written in capitals, if i
>>don't write the accented word in capital in the parameter, i get an error
>>alert, telling me that the member is not found. the only way to corrrect
>>this is writing the accented letter exactly like the accented letter in
>>the member's name. that's funny, because this parameter is a string,
>>although it is held as a global. shouldn't lingo be not case sensitive?
>>i've had issues with accented words in markers before, so i may presume
>>that director does not handle very well stuff like that.
>
>But accented characters are special characters, and aren't considered
>normal letters (english bias). I'll bet that Director only considers A-Z
>and a-z as identical and no other characters outside of those 46.
>Lingo is case-insensitive for characters with the high bit reset--IOW,
>ASCII value <= 128 (and >= 65). It's an English bias, for sure--ASCII is a
>7-bit standard, and doesn't support any accented characters (officially).
There are other cases in which Lingo is case-sensitive, even when using English
letters.
Details on case-sensitivity and accents and other diactrical marks can be found in
Appendix C of Lingo in a Nutshell.
Bruce Epstein
Zeus Productions
[EMAIL PROTECTED]
732-940-2800
[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!]
