Unicode 'as string' = unicode?
Unicode 'as string' = unicode?
- Subject: Unicode 'as string' = unicode?
- From: Paul Berkowitz <email@hidden>
- Date: Wed, 04 Sep 2002 18:08:11 -0700
I'm aware that 'string' is now 'styled text', 'international string'.
Even so: when I use a Japanese and a Russian keyboard to input Japanese and
Russian into names of Address Book contacts (manually), then get the names
via AppleScript, the results are in Unicode. When I then
set stringName to theName as string
stringName = theName
--> true
What's going on? Even international string should not be able to do
double-byte Unicode, should it? If I open the result in a Script Debugger
result window, sure enough, it looks exactly the same (although it doesn't
look perfect). Also if I transpose it to Entourage, it looks perfect there.
I'm actually trying to test to see whether the Unicode text is nothing ASCII
will go anywhere, or whether it's something that really has to be Unicode.
So I'm testing now with the <<class ktxt>> business.
But why is AppleScript not doing anything when asked to get Japanese 'as
string'? Is the the result of the kindly coercions that allow MacRoman ASCII
strings (such as punctuation) to pass back and forth as Unicode. Is it
likely to remain like this indefinitely, or is this something that will
change again soon?
--
Paul Berkowitz
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.