The problem is, a release is a moving target.
In an ideal world, that would be pretty easy. Another script copies the files into the corresponding places in our subversion repository, careful not to stomp on the. Using a shell script, I copy the resources into a new directory structure that parallels our subversion repositories (since the topology of an application package is not the same as our source code). When they are done, they export the resources (.strings files. They each open the application bundle with iLocalize, and it figures out what strings need to be translated, keeping track of the strings that have already been translated. The ideal workflow goes something like this: When we are getting near a release, we send a private build of Sandvox out to these localizers.
#Ilocalize mac license#
(We may have to drop a couple of supported localizations for our forthcoming 1.5 version we've lost a couple of our volunteers unfortunately.) The volunteers all use iLocalize, which is a great (but by no means the only) localization tool out there if they don't have the program we get them a license for them to use it. The localizations are done by some wonderful, amazing volunteers. Besides English, it's in Danish, French, German, Italian, Japanese, Traditional Chinese (Taiwan) and Simplified Chinese (China). The current version of Sandvox has eight localizations. It really could be a lot easier than it is now. Each time we have a new version coming out, I have to go through a lot of tedium and hassle to successfully get Sandvox updated and fully functional in several languages.
#Ilocalize mac update#
Get notified automatically of new updates thanks to the built-in update capability.I've been spending the last few days, on and off, dealing with localizations of the new Sandvox version we are trying to get ready. Encoding for text, html and strings files can be set on a file-by-file basis. Moreover, multiple selection is now supported in the file table meaning that multiple files can be edited at the same time.Įdit most files directly in the project window thanks to the integrated editors: strings, txt, rtf, html, plist and many more. The project window has been designed to efficiently use the screen space: smart filters and languages are immediately available. When finding for a particular string, the results will always be available in the filter table for immediate access. Smart filters are a convenient way to display immediately only files and strings having particular attributes, such a to translate. Glossary can be exported or imported to the TMX standard format. Thanks to the multi-threaded glossary engine, you don't have to wait for the entire glossary library to be searched before translating or moving to the next string. The glossary inspector provides a powerful way to immediately view suggested translation from one or more glossary at a time. iLocalize handles multiple languages in the same project, offers custom glossaries, smart filters and has powerful features to help incremental localization. ILocalize is a powerful and intuitive application designed to help developers localize their applications.
0 kommentar(er)
