Re: R?p: old AppleWorks script failing under 10.5
Re: R?p: old AppleWorks script failing under 10.5
- Subject: Re: R?p: old AppleWorks script failing under 10.5
- From: has <email@hidden>
- Date: Mon, 11 Aug 2008 18:40:17 +0100
Matt Neuburg wrote:
In my opinion, you should file a bug with Apple on AppleScript 10.5
for
making you do this. The backwards incompatibility that requires this
sort of
song-and-dance is unacceptable.
As a general FYI, appscript gives you more control over the way that
text is packed into Apple events, allowing you to deal with such
'awkward' applications much more easily. For example, Python appscript
packs values of type 'str' as typeChar (your system's primary
encoding, e.g. MacRoman) and values of type 'unicode' as
typeUnicodeText. Ruby and ObjC appscript provide methods for
specifying the AE type used (the default is typeUnicodeText). Plus
appscript is completely open and highly hackable, allowing its
behaviour to be customised even further if desired.
HTH
has
--
Control AppleScriptable applications from Python, Ruby and ObjC:
http://appscript.sourceforge.net
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden