Le 16 mars 2009 à 06:31:17, Jon Pugh a écrit :
At 9:03 AM +1100 3/16/09, Shane Stanley wrote: As it happens, I've been doing some stuff in InDesign lately, including some in _javascript_. One of the things that struck me again is just how clear and readable a compound whose clause is can be in AppleScript. You can look at old code and see in an instant what was happening, without having to dig through multiple loops of iteration. But then I looked at sections of code doing string manipulation with TIDs rather than basic commands like split and so on, and was struck by exactly the reverse.
This is precisely why I wrote and use my SmartString class. It results in easy to read string code and by using code that is "known to work", there's a lot less screwing around.
(The file is MacOS Roman encoding.)
Hi John.
You posted an exemple of what I call an English-centric code.
It may be useful for English writers but is useless for others.
English is not the unique language in the world and, even in MacOS Roman there are some characterss which you didn't take care of:
œ,Œ,æ,Æ, á, Á, à, À, â, Â, ä, Ä, ã, Ã, å, Å, é, É, è, È, ê, Ê, ë, Ë, ó, Ó, ò, Ò, ô, Ô, ö, Ö, õ, Õ, ú, Ú, ù, Ù, û, Û, ü, Ü, í, Í, ì, Ì, î, Î, ï, Ï, ñ, Ñ,ç, Ç, ø, Ø, ÿ, Ÿ, π, ∏
Yvan KOENIG (from FRANCE lundi 16 mars 2009 11:23:11)
|