• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Unicode 'as string' = unicode?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unicode 'as string' = unicode?


  • Subject: Re: Unicode 'as string' = unicode?
  • From: John Delacour <email@hidden>
  • Date: Thu, 5 Sep 2002 09:58:51 +0100

At 6:08 pm -0700 4/9/02, Paul Berkowitz wrote:

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?

I don't see quite what you're getting at in your message, Paul, but the basic problem is that until we get proper cocoa applications both from Apple and from developers, everything is going to be a mess. At least Apple has given us WorldText, TextEdit, Mail and Address Book.

Suppose you create a new person in group family with first name

"pi-alpha-tau-eta.with.oxia-rho"

[ Unicode hex input: option-key 03c003b103c41f7503c1 ]

and then run this script,

tell application "Address Book"
set n to first name of last person of group "Family"
end tell
display dialog "" default answer n as international text
return n

You will find that the result window gives you what looks something like "pi-alpha-tau-?-rho" and that the dd dialog gives you an ascii mixture of Mac and non-Unicode Japanese encodings.

"...although it doesn't look perfect", you write. It doesn't look perfect because if you paste the result into TE+ or some other Uignorant editor, you will find that the pi is from the Mac character set in Geneva or monaco or something and the other non-accented "Greek" characters are robbed from the non-Unicode Osaka Japanese character set and the eta-with-oxia, which exists only in the Unicode set, is displayed as a question mark. There is no "passing back and forth" of such a heap of nonsense. Once this filtering has taken place there is no reversing the process.

JD
_______________________________________________
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.

References: 
 >Unicode 'as string' = unicode? (From: Paul Berkowitz <email@hidden>)

  • Prev by Date: Re: Unicode 'as string' = unicode?
  • Next by Date: Re: Unicode 'as string' = unicode?
  • Previous by thread: Unicode 'as string' = unicode?
  • Next by thread: Re: Unicode 'as string' = unicode?
  • Index(es):
    • Date
    • Thread