Once you have a project in iLocalize, the next thing to do is to translate the project. This section focuses on the translation process for the strings and nib files only (other type of files can be translated using external tools).
To translate a string, type its translation in the desired language column. More than one file can be selected at one time.
Glossaries are very powerful to help suggesting a translation for a given string. Click on the lower-left button representing a glossary to open the glossary view. Each time a string is selected, iLocalize will display the list of translation candidates, with the best match at the top. Double-click on any match in the list to apply the translation.
iLocalize uses by default two places to look for glossaries:
It is possible to specify more path to look for glossaries by open the glossary manager using the command:
Next to the glossary view (at the bottom left of the project) is another list of translation: this list displays all the translations of identical string in the current project. This is useful to see if you already translated a term somewhere else.
It is possible to instruct iLocalize to propagate translations to similar items, when strings differ only by the following punctuation signs:
For example, the following strings can be automatically translated at once:
When the first string is translated, iLocalize can propagate the translation to the other similar strings, by keeping their specific end punctuation.
And the end result will be:
When translating the strings of a nib file, make sure to also adjust the interface if needed. To adjust the nib layout, double-click on the file to open Interface Builder. Once the layout is adjusted, save the file in Interface Builder and switch back to iLocalize. When iLocalize updates a project, it is possible to instruct iLocalize to keep the previous localized layout (more discussion about that in the Updating a project section).