Home ›

2.x

Help us with Camino 2.0 in Portuguese

Submitted by Marcello on Wed, 08/19/2009 - 22:32

Unfortunately, the people working on the Portuguese Camino l10n can no longer work on it and the 2.0 release is getting quite close.
If anyone wants to see the Portuguese translation of the upcoming (and exciting) new version of Camino and see it right from the 2.0 release, this is the right moment, because soon Camino2beta4 will be released, marking a substantial milestone in the development and bringing us an almost string-complete Camino 2.

There are substantial additions of strings from Camino 1.x, but also a good amount of them that can be translated very quickly, taking advantage of localized Firefox 3 builds.

Please set up at least a team of 2 people (one translator, one reviewer), but I suggest that, given the timing, a bigger team can speed up things dramatically.

I'm waiting for responses from the PT people here!

PS - You might also look for contributors at your local Mozilla communities, if you know any.

A couple of hours with iLocalize and Camino 2.0alpha1

Submitted by Marcello on Sun, 11/16/2008 - 11:43
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:

Chrome strings almost ready for translation

Submitted by Marcello on Wed, 08/29/2007 - 22:31
in

The unavailability of so-called "chrome strings" to Cocoa (the framework Camino is built upon) for translation/localization has been bothering our teams and our international users for a long time.
https://bugzilla.mozilla.org/show_bug.cgi?id=248160

The solution for this problem isn't here, yet, but has taken a big step closer lately, thanks to a new patch. The mechanism that will allow to override those strings (that are basically located in Mozilla code inside .jar files, inaccessible to Cocoa's means of translating a package) is finally set up and the strings might show up in Localizable.strings soon.
However, the target for implementing this huge improvement has been set for Camino 2, so Camino 1.6, next major upgrade of the application wil still show untranslated portions.
Here's a brand new bug about this new situation: https://bugzilla.mozilla.org/show_bug.cgi?id=394105

Syndicate content