Re: display dialog bug
Re: display dialog bug
- Subject: Re: display dialog bug
- From: "J. Stewart" <email@hidden>
- Date: Sun, 19 Jun 2005 07:41:44 -0400
On 06/18/05 at -0700 Paul Berkowitz said this
>Now I just have to figure out if it's better to coerce the original values
>to string when getting the results from display dialog, or when writing to
>file, or to let it go ahead as Unicode and then read back 'as Unicode text'.
>The main script is so long, with so many places where this could go wrong,
>that it might be simplest to control it by coercing these values to string
>just before writing to file. (I notice that the file does not even contain
>the tell-tale 'utxt' key for these values as it does for lists of Unicode
>values I also write to file. It doesn't seem to know.)
Paul,
Per the AppleScript v1.10 Release note:
<http://developer.apple.com/releasenotes/AppleScript/AppleScript.html>
The implicitly encoded text types, typeText, typeCString, and typePString, are all deprecated as of AppleScript 1.9.2, since they are incapable of representing international characters and may be reinterpreted in unpredictable ways. Additionally, typeCString and typePString do not support the full range of text coercions, and will be removed entirely in a future release. typeStyledText and typeIntlText, while they have explicit encodings, are not recommended, since they are incapable of representing Unicode-only characters like Hungarian, Arabic, or Thai. The recommended text type is typeUnicodeText.
Sounds like you might want to stick with Unicode.
JBS
--
The tree of liberty must be refreshed from time to time with the blood of patriots and tyrants. It is its natural manure. - Thomas Jefferson
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden