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 08:31:52 +0900
On 15 juin 2011, at 04:53, Ron Hunsinger wrote:
> What you're seeing is that Apple sometimes converts Unicode characters to their fully decomposed form. And to understand what "fully decomposed form" means, you have to understand the difference between characters and codepoints.
Thank you. I understand that very well even if I am not familiar with the exact terms.
What I do not understand is the reason for the "sometimes".
Besides, as far as I can tell, it is not a matter of what the characters _look_ like. They look exactly the same in the Automator output too.
It is a matter of being not the same.
I used "echo" to show that there was something happening (for ex, run the service in a TextWrangler window and you'll see what I mean right away), but if I run a grep process I won't find matches if the characters have been fully decomposed by Automator.
Which kind of defeats the point of having a "run shell script" action.
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.
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