[Caminol10n] Using iLocalize

[Igor Pryadkin]

07.03.2008, в 11:59, Markus Amalthea Magnuson написал(а):

> I've had problems with iLocalize, someone with more experience from
> the application might be able to help me.

Hi guys,
I want to share my experience with you of using iLocalize.


1. Create a new project from the last Camino ML (select also 'Create  
non-existing localized file(s) from base language' and 'Leopard and  
previous version' compatibility)
2. Select English (en) and your language (setting English (en) as base  
language)
If you find ISO (ru in my case) and legacy (Russian in my case)  
designation for your language, select both.

The problem is that the last iLocalize version doesn't make difference  
between ISO and Legacy names and creates by default a Legacy  
('Russian' in my case) lproj folder when exporting even if you set an  
ISO ('ru' in my case) designation for your language in project.

  3. Open iLocalize preferences
in 'General' pane:
- select all the items in 'Automatic actions', and Display', if not  
selected;
in 'Localization' pane:
- select ' Validate string on user input' and 'Flag updated files  
after update operation', if not selected,
- uncheck 'Propagate to similar items' if checked (my suggestion for  
'beginning' period, then, if you find it useful you can also select  
this item);
- check 'Select next string after translating', if not checked,
- check 'Translate only if different from base string', if not checked,
- uncheck 'Fill translation with base language', if checked,
- check 'Read-only' for Base language
- Select 'No' for 'Translation propagation' (my suggestion for  
'beginning' period, then, if you find it useful you can set to 'All  
files' or Selected files');
- select 'Translate only if string is not translated' for 'Automatic  
translation' (my suggestion for 'beginning' period, then, if you find  
it useful you can set to 'Always translate');
- select 'Update base language' or 'None" for 'Default Update Selection'
As for other preferences, set them as you want.

4. Now you can check your project for incompatibilities, issues, etc.  
Menu 'Project'> 'Check' item. In our case you'll find 2 (o 1, I don't  
remember for sure) issues in 'Talkback' strings, that we can ignore  
for a moment, I think.

If you have unlocalized strings for your language (0% ... 99%  
indicates the percentage of translated string, if there's no % sign,  
your language is fully translated or (important!!!) filled with base  
language. To avoid it, I suggest  not to check 'Fill translation with  
base language' box, if checked in 'Preferences' and to review your  
language.

6. Create your language Glossary: menu 'Glossary' > New Glossary
- Path >  (Personally, I prefer  'Global' . You can find it in ~/ 
Library/Application Support/iLocalize/Glossaries)
-select 'Language' for 'Scope'
- select 'English' or 'en' for 'Source'
- select your language for 'Translation'
- check box for 'Translated' and leave other unchecked.
-save your new glossary.

You can also import Apple's glossaries from Mac OS X (see JJ.'s  
message) for your language and place them in ~/Library/Application  
Support/iLocalize/Glossaries. Then, open Glossary>Manage Glossaries.  
You'll see all the .ad glossaries, and you can leave them or merge ad.  
glossaries in one ilg. glossary.

After that, you can save and close you project.

When you want to update your project, download the latest Camino  
build, mount dmg, start iLocalize, open Camino project, select 'Update  
from bundle' in 'Project' menu.
1.
- select 'Update the project from a new version of the bundle' and  
path to mounted dmg
- DON'T check the box 'Reset the layout of each localized nib file  
from its base-language layout'. Otherwise, all changes, you made  
previously, will be lost.
- don't check the box 'Update the localized languages of the project  
from bundle'
2.
After update all the updated files have 'updated' label, and you'll  
see a strings percentage to be translated, when you switch to your  
language.
3.
Open 'New glossary inspector' in Window menu.
If there's a string that was previously translated, you'll see it in  
glossary window and use it. If you are sure that the same translation  
is used for similar strings (not in my case), you can propagate it  
(ctrl+click  >Propagate translation to identical strings in all files  
or Option key +F4)

4.
Go to 'To translate' filter. Translate strings to be translate. Go to  
'To check' filter and check automatically filled pairs (select and  
press F1 to approve o ctrl+click to open contextual menu)

5.
IMPORTANT!!! You should rebuild from English all the updated nib files  
(marked with updated label). Select a nib. file, ctrl+click to open  
contextual menu, select 'Rebuild from "en" o "English", DON'T check  
the box 'Keep existing nib layouts', because, normally, updated  
English nib. have also an updated layout and you should copy this  
layout and completely rebuild after that a layout for this nib  
manually once again.

6.
To open this nib file in Interface Builder after rebuilding, just  
double click on it.
7.
If your modified strings file have another encoding than English ones,  
ctrl+click on it, and select Encoding of English file and save.

8. After work is done, clear updated file symbols (ctrl+click  clear  
updated file symbols or F6) in both English and your language.

9. Close Glossary window, than create a new glossary, save it to save  
changes.

10. Go to Application menu and generate your app.
In opened window check 'en', 'your language' and 'Optimize' boxes.

IMPORTANT!!! DON'T check the 'Compact nib files' box, otherwise they  
become unmodified and can be used for further work.

11. Save project and quit iLocalize. You can run your Camino. Remark.  
If you open Camino package now, you find that your language lproj  
folder (Russian in my case) has a legacy designation, even if you  
worked with ISO designation (ru in my case). So, you can leave a  
legacy or manually rename all 'Legacy'.lproj to 'ISO'.lproj.

Hope, I was clear.
I think, that's all, that I could share with you.
Ciao
Igor