Tutorial

iLocalize is a localization tool (http://www.ilocalize.com/ilocalize/). Like AppleGlot, it's basically an interface for nibtool/ibtool, but it has several advantages, compared to AppleGlot, not requiring an external strings editor and having a nice UI for trivial tasks like importing a localized package or updating the source package.
If you localize open-source software (like Camino), you can use it without paying, by acquiring a free license: http://www.ilocalize.com/ilocalize/download.html
iLocalize requires Mac OS X 10.4 and, of course, XCode installed.

In this page, we look at the initial set-up and at the basics to get started. Detailed instructions provided by Igor Pryadkin.

1. Create a new project:

- Use the latest Camino MultiLanguage distribution as the package to be imported
- Check "Create non-existing localized file(s) from base language" option
- Check "Leopard and previous version" compatibility option
- In the following screen, 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.

2. Preferences

In "General" pane:
- Check all the items in "Automatic actions", and "Display", if not checked
In "Localization" pane:
- Check "Validate string on user input" and "Flag updated files after update operation", if not checked

Goals of this document
- To provide easy to use instructions for the people involved in localizing Camino, who need to distribute autonomously their work or need to send it to who builds the multilanguage package
- To create standard rules to be followed when localizators build their packages
- To allow circulation of smaller packages among localizators, so that broadband shouldn't be a requirement in order to participate to the project

Pre-requisites
- This document assumes that you have Apple's Developer Tools installed; if you don't have them, you wouldn't be able to work on the localization, anyway. Please see our AppleGlot How-To for more information about getting started in the localization workflow
- You need to be comfortable with the terminal: no particular skills are needed, you just have to be able to type in easy commands and change your working directory with the cd command

Introduction

Localizing a Cocoa application is not a difficult task, given the proper tools. It's easy to get the job done with Interface Builder and a little bit of patience. But, when you have to do recurrent translations of the same application, especially when this application is in an early development stage, it could become time consuming. This tutorial covers how to optimize efforts in localizing Camino, using tools mainly provided by Apple.

Download the tools

Everything starts at this URL:
http://developer.apple.com/intl/localization/tools.html
which points to links to everything we need:

We aim at delivering good and reliable translations. In order to do that, we ask that every localization is produced by a team and not by individuals. The reason is quite simple: as in the editorial world, authors are likely to miss their own errors, even if they thoroughly check their work. So, a team should be composed of at least 2 people: 1 doing actual translation using iLocalize and Interface Builder; 1 that checks the other's work. This checklist is a little help for the ones who check if everything is right. Comments are welcome through caminol10n mailing-list.

Introduction

When you're alone working on something like translating Camino, you tend to look over some mistakes. So in order to catch these mistakes, you have to help us. These mistakes includes:

• misspelled words
• user interface glitches (i.e. a window title not completely visible)
• untranslated sentences.

In order to fix these, the Caminol10n team needs to know that the problems are present. We need to be able to track those bugs, to do that, we will use the Mozilla Project's bugzilla.

Create a bugzilla account

Open your browser to https://bugzilla.mozilla.org/createaccount.cgi. Enter a valid email address; on this you will receive your bugzilla e-mail messages. Shortly after registration, you'll receive an e-mail message containing your bugzilla password. After completing registration with this password, you'll be able to report bugs and post comments.

If you already have a bugzilla account there is no need to create a new one.
Bugzilla related mail is often called bugmail.

Report the bug

Connect to https://bugzilla.mozilla.org/enter_bug.cgi?product=Camino. You'll be granted with a page that looks like :

To report the bug correctly we need the Component field (on the upper right) to be set to Translations.