Re: Scripting Additions: Embracing the Horror of Unix
Re: Scripting Additions: Embracing the Horror of Unix
- Subject: Re: Scripting Additions: Embracing the Horror of Unix
- From: Christopher Nebel <email@hidden>
- Date: Thu, 31 Jan 2002 18:20:10 -0800
On Thursday, January 31, 2002, at 05:44 PM, Shane Stanley wrote:
On 1/2/02 12:40 PM +1000, Christopher Nebel, email@hidden, wrote:
There are still issues with non-ASCII characters vs. "do shell script",
but that's a different problem.
And that is? Do I still need to check for other characters? Would it not
make sense for the one command to do it all?
As a few people on the list have noticed, "do shell script" doesn't
behave well when you give it a path that contains non-ASCII characters
(e.g., an accented e) no matter how you quote it -- you usually get an
error about the file not existing. The problem is a fundamental
disagreement between "do shell script" and the shell itself about what
text encoding to use. It's possible to code around the problem in your
script, but it's *really* nasty.
The goal is that you should be able to say, if f is a file or alias
object,
quoted form of POSIX path of f
...and that gets you a string suitable for use with "do shell script" no
matter what screwy characters you like to use in your file names. We
hope to have it all straightened out in AppleScript 1.8.2.
--Chris Nebel
AppleScript Engineering