Dear MacScripters,
I have started to add the capacity to localize some of my AppleScripts following the example given here on MacScripters: http://macscripter.net/viewtopic.php?id=24805. However, my AppleScripts are already a little large and ponderous, and managing the Localizable.strings files with just TextEdit is tedious and error prone.
I was hoping to find a small program that would at least validate a Localizable.strings to catch the obvious typos; however, web searches dredge up nothing like this.
What is the “production” method for dealing with localized AppleScripts? Should any AppleScripts with this complexity “graduate” to Xcode projects? I’m not doing anything with user-interfaces yet on these scripts, so I haven’t needed anything beyond the AppleScript Editor. Has that just changed? 
Thanks for your advice on my “too big for their britches” AppleScripts . . .
Cheers, Edouard 
Both TextWrangler (free - App store) and BBEdit (not too expensive) have syntax colouring for string files. That should avoid most technical errors. (Your typos in the languages are another topic of course. But both support the standard Mac spell checking mechanism.)
Localization of AppleScript bundles and applications is not really different. There may be many reasons to use XCode, but I do not thing that localization is one of them.
Jürgen
Dear Jürgen and MacScripters,
Thanks for the suggestion. Indeed syntax highlighting should go a long way toward ferreting out errors. I’m trying to make the transition from UNIX programming to OS-X, so it might serve me well to upgrade to BBEdit.
I poked around in XCode once more and indeed it seems to offer nothing more than the same syntax highlighting. I had expected that someone would have tossed together a little drag’n’drop tool to catch Localizable.strings errors, if for not other reason than to double-check translatior’s submissions. But indeed this may be simply superfluous and unneeded.
Thanks again for the suggestion . . .
Cheers, Edouard