v; last modified 2005-01-25 18:50:05 EST by krabat

Target Localizations

These are in no particular order. I have received offers to help with some of these locales already. If you are interested in helping, sign your name as I have below the appropriate section. You can send me an email to let me know how to communicate with you, since I doubt you will want to post a raw, spam-bot scrapable email address. (Note to self - make Wikir insulate any email address automatically.)

• English (development language)
• MikeSolomon
• German (released as part of Safari v0.7)
• Johannes Hoffmann
• French
• Jacky Bendayan
• Italian
• Spanish
• Norwegian
• Swedish
• Niclas Hedell
• Danish
• Kenneth Krabat
• Dutch
• Japanese
• Korean

How To Help

1. send me an email asking for the latest working glossary
2. sign your name on this page so no one else tries to translate the same file again
3. open it up in ADViewer http://developer.apple.com/intl/resources/ADViewer2.0b3.dmg.bin (you can use TextEdit, you may have to drag-n-drop it to force TextEdit to open it - also, make sure you are in UTF-8 encoding)
4. replace all of the tran tags with the translated text
5. send me a copy via email

Sample Work Glossary

<TextItem>

<Description> NSButton (Hide Blocked Content) : <title:Hide Blocked Content> (oid:94) </Description>

<Position>94.1</Position>

<TranslationSet>

<base loc="en" >Hide Blocked Content</base>

<tran loc="de" origin="">fill in translation here</tran>

</TranslationSet>

</TextItem>

AppleGlot

This is a pretty amazing tool for manipulating the internal strings for both the code and .nib files. It has some quirks, but it automates incremental string extraction/replacement in the .nib files, which is really cool. Plus, it generates translation glossaries that indicate just the strings that need localizing.

It does have a few quirks though - most notably its poor handling of .strings files. The only way I could get them to work was by encoding them in UTF-16.

Since AppleGlot really automates most of the difficult tasks, the new plan for localization is for me to generate the "work glossaries" for each language. This is a fairly simple XML file which can be editted with TextEdit. Once the translation is done, I can reinsert the strings and check any layout issues manually.