Re: Automator bug in "run shell script" ?
Re: Automator bug in "run shell script" ?
- Subject: Re: Automator bug in "run shell script" ?
- From: Jean-Christophe Helary <email@hidden>
- Date: Wed, 15 Jun 2011 11:26:22 +0900
On 15 juin 2011, at 10:58, Ron Hunsinger wrote:
>> What matters is that if I want to process a string that uses a composed form and Automator gives me a decomposed form without warning I don't get the result I expect. And there is not setting anywhere in "run shell script" that lets me pass composed strings.
>
> If you process the string as Unicode, you'll still get the right results. If you process it as a sequence of bytes, for example by using a tool that doesn't understand Unicode, you won't. You have to use the right tools. "do shell script" does what it can, by encoding the codepoints in UTF8 before passing them to the shell, and converting the output back from UTF8 to Unicode text. The problem isn't "do shell script" itself, it's which Unix tools you ask the shell to use.
Sorry Ron, I must be really thick.
What I am seeing is that grep works fine with any sort of string I feed it when I run it in the Terminal and that Automator does something to that string before the command is passed to the shell so that grep is not grepping the same thing at all anymore when run in Automator.
If there is a way to have it work properly in Automator, I'd love it if you could explain it to me.
It may not be a bug, but it certainly is not expected behavior.
Jean-Christophe Helary
----------------------------------------
fun: http://mac4translators.blogspot.com
work: http://www.doublet.jp (ja/en > fr)
tweets: http://twitter.com/brandelune
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Automator-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden