Re: path to as string
Re: path to as string
- Subject: Re: path to as string
- From: Paul Berkowitz <email@hidden>
- Date: Mon, 27 Jun 2005 11:46:24 -0700
- Thread-topic: path to as string
On 6/27/05 11:29 AM, "Christopher Nebel" <email@hidden> wrote:
> "Deprecated" in Apple documentation usually implies that the function/
> constant/whatever in question is going to completely disappear
> sometime soon-ish. This is not the case with typeText and friends,
> since there's way too much existing software that uses them. We
> merely recommend that people not use them, since they have problems
> working correctly world-wide.
Unfortunately, that's not true, Chris. According to the AppleScript Release
Notes for AppleScript 1.9.2, and specifically reiterated in the Release
Notes for AppleScript 1.10:
"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."
So: typeStyledText and typeIntlText are not deprecated, although not
recommended, but typeText IS deprecated (according to you "is going to
completely disappear sometime soon-ish") in spite of the fact that there are
still quite a lot of typeText still around.
Will this release note be changed?
--
Paul Berkowitz
_______________________________________________
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