To do

Camino 1.6.11 l10n status

Release notes can be found at Bug 549370; there are also small edits in the software update descriptions, since this will be the last Camino 1.6.x release (Bug 549374). See the full article for the usual status matrix.

Please note that there will be one and only one release of any localized version of Camino. Therefore, it's very important that release notes translations are produced and sent as soon as possible.

The translations are expected to be sent by Tue, Mar 9

Camino 2.0.2 l10n status

Release notes can be found at Bug 545347. See the full article for the usual status matrix.

Please note that there will be one and only one release of any localized version of Camino. Therefore, it's very important that release notes translations are produced and sent as soon as possible.

The translations are expected to be sent by Sun, Feb 21

Camino 2.0.1 l10n status

Release notes can be found at Bug 530177 (not finalized, but can be worked on). See the full article for the usual status matrix. There is an additional string to translate in Frameworks/Breakpad.framework/Versions/A/Resources/crash_report_sender.app/Contents/Resources/[lang].lproj/Localizable.strings: Bug 529989 comment #3.

Please note that there will be one and only one release of any localized version of Camino. Therefore, it's very important that release notes translations are produced and sent as soon as possible.

Camino 2.0 l10n-related bug list

This list should help the Camino ML maintainer keeping potential issues on the radar.

2.0
Bug 519140 - [l10n] Ensure "Edit Security Exceptions" button properly aligned in prefs
Bug 522783 - Two spaces instead of one between sentences in Safe Browsing hint text
Bug 521613 - Update Description for Camino 2.0

2.0.1
Bug 530177 - Release Notes for Camino 2.0.1
Bug 529989 - Collect email addresses and send them to Socorro with reports (see comment #3)

Camino 1.6.10 l10n status

Release notes can be found at Bug 515800. See the full article for the usual status matrix. There is an additional string to translate in PreferencePanes/WebFeatures.prefPane/Contents/Resources/[lang].lproj/Localizable.strings: Bug 513804.

Please note that there will be one and only one release of any localized version of Camino. Therefore, it's very important that release notes translations are produced and sent as soon as possible.

Analysis of current CL10n docs

in

[Here's a tentative outlook upon our documentation. Comments and writing help are warmly welcome!]

Camino 1.6.8 l10n status

Release notes can be found at Bug 495738. See the full article for the usual status matrix.

Please note that there will be one and only one release of any localized version of Camino. Therefore, it's very important that release notes translations are produced and sent as soon as possible.

The final multilingual package is expected to be complete by Sat, June 20

CaminoL10n website users: please update your profile

in

Hello, fellow CaminoL10n users and contributors!
You are invited to update your profile on our website, by adding information that is valuable for the Camino development team.
Specifically, the developers wish to know which OS X versions you are using when you work on Camino's localization.

Camino 1.6.7 l10n status

Release notes can be found at Bug 481575. See the full article for the usual status matrix.

Please note that there will be one and only one release of this localized version of Camino. Therefore, it's very important that release notes translations are produced and sent as soon as possible.

As of Mon. March 30th, I have received all the needed files from the l10n teams.

A couple of hours with iLocalize and Camino 2.0alpha1

in

After spending a little time on the building routine of Camino 1.6.5, I downloaded Camino 2.0alpha1 and looked at what's going to be done for the localization teams.

In the meantime, I had upgraded iLocalize to version 3.8 through its software update system: at the moment, it looks like a seamless upgrade with near to zero impact on the Camino l10n process.
One of the little things that make iLocalize useful is the ability to detect changes when you upgrade the base package (I can't say if this feature was present in previous versions); here is what was listed, when I upgraded my Camino 1.6 iLocalize document importing the Camino 2.0alpha1 package:

Syndicate content