User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; es; rv:18.104.22.168) Gecko/20070809 Camino/1.5.1 (MultiLang)
I want to localize Mozilla Firefox
Contributor: Emilio Sepúlveda
Contact e-mail: firstname.lastname@example.org / email@example.com
ISO 639 Code: es-CL
I need CVS access for work in the es-CL localization project.
We've recently developed new documentation about how to become an official l10n team for Firefox or Thunderbird:
Could you please follow the procedure there, including creating yourself an L10n wiki page? That will make you the official localisation team for Chilean Spanish. You may want to coordinate with the other Spanish teams to make it easy for you to reuse their work. You probably don't want to start from scratch! If you can get yourself to the stage where you are able to distribute a working language pack for the latest version of Firefox, we can discuss checking the localisation into CVS.
I notice you've also opened a bug on registering to do SeaMonkey (bug 287638).
If you find the documentation isn't detailed enough, please let us know so we can fix it.
I have CCed folks from the Spanish localization teams here, this bug is as good as any other.
I'd like the spanish localizations to be a team effort. Could each of you do a review of the existing localizations, i.e., es-ES and es-AR, and give us an estimate on how big you think the changes should be between either and es-CL and es-MX? Feel free to point out places where you just think you found bugs in the two.
I have opened a thread on mozilla.dev.l10n, which you can join on both google groups and news.mozilla.org, google groups thread is http://groups.google.com/group/mozilla.dev.l10n/browse_frm/thread/3a8a0299c38b3fae/2f16fe7858ae3c18#2f16fe7858ae3c18
Thanks for your support
(In reply to comment #2)
> I have CCed folks from the Spanish localization teams here, this bug is as
> good as any other.
> I'd like the spanish localizations to be a team effort. Could each of you do a
> review of the existing localizations, i.e., es-ES and es-AR, and give us an
> estimate on how big you think the changes should be between either and es-CL
> and es-MX?
I'm afraid I can't do that. Neither I have enough time to do it, nor I have precise knowledge about what a chilean or mexican would find weird in a es-ES translation, much less in es-AR.
I really think the process should be taken on es-CL and es-MX side, and I don't really think I need to do it (heck, I'm not even sure if I *can* do it), but of course I bless anyone to take es-ES localization as starting point for another es-* localization, as long as they respect licenses.
Emilio just talked to me, and most of the es-AR localization will be used to get es-CL ready as soon as posible.
Chile is right next to Argentina and our localization is almost perfect.
Espero no incomodar a nadie por hablar castellano.
Estoy de acuerdo con Ricardo Palomares con respecto a su comentario en el que cree que los procesos deben ser realizados por separado, cada país de habla hispana tiene sus características muy particulares, pero creo que a todos nos caería bien tener alguna referencia, guía, mejores prácticas, etc. del proceso.
Ya que Gervase Markham ha sugerido la creación de la "wiki page" a cada uno de los que estamos interesados en contribuir en este aspecto, yo sugiero, si así lo desean:
* Crear una wiki page para las "Localization" de habla hispana siendo un punto de encuentro que además sirva para oficializar los equipos de trabajo.
* Que exista una sección individual para los integrantes de cada país.
* Crear una sección de consulta común que incluya referencias, guías, tips, mejores prácticas, fuentes, FAQ's y demás contenidos que faciliten el proceso y permitan reusar el trabajo (si los amigos de Argentina o España lo desean, al inicio nos podrían dar una gran ayuda incluyendo sus valiosas experiencias).
* Contribuir en las secciones antes mencionadas con las nuevas experiencias que los recién llegados tengamos.
Yo puedo contribuir con la creación de la wiki page de inicio apoyado, por supuesto, de sus valiosas sugerencias.
Estoy consciente que es mucho trabajo, pero sería bueno hacerlo.
Ricardo Palomares, that's totally fine, I mostly CCed you to get you into the loop on the discussion.
Marco, Emilio, I'd be interested to have some details on the "most", either a patch en-AR vs en-CL, or some overall description of the changes.
Ricardo Meza, sadly, I don't speak any Spanish, so I cannot comment on your input.
(In reply to comment #3)
> I really think the process should be taken on es-CL and es-MX side,
I've just noticed that I should clarify on this:
> and I don't really think I need to do it (heck, I'm not even sure if I *can*
> do it),
Just in case, I didn't mean that I don't need to or can check translation similarities. I meant that I don't know if I need or can grant permission to use es-ES as starting point for another es-* localization:
> ...but of
> course I bless anyone to take es-ES localization as starting point for another
> es-* localization, as long as they respect licenses.
(In reply to comment #5)
> Espero no incomodar a nadie por hablar castellano.
Let's stick to english so all participants can understand and reply to comments. :-)
> Estoy de acuerdo con Ricardo Palomares con respecto a su comentario en el que
> cree que los procesos deben ser realizados por separado, cada país de habla
> hispana tiene sus características muy particulares, pero creo que a todos nos
> caería bien tener alguna referencia, guía, mejores prácticas, etc. del
[Ricardo Meza suggests putting in common references, guides, best practices about the L10n process]
English-spanish localization style guides are sometimes published by commercial companies. I think Microsoft did it, and I was aware recently of Sun's:
I like most of what I've read in Sun's guide, but still there are points in which I don't agree. I think the best move will be for each es-* localization to write their own style guide, based on previous guides. For instance, translating "computer" by "computadora" sounds unusual in Spain, and translating it by "ordenador" sounds unusual in most latin-american countries.
Regarding localization processes themselves, I strongly believe that documents and tips about them should be in english, as they shouldn't depend on the target language.
> Ya que Gervase Markham ha sugerido la creación de la "wiki page" a cada uno de
> los que estamos interesados en contribuir en este aspecto, yo sugiero, si así
> lo desean:
> * Crear una wiki page para las "Localization" de habla hispana siendo un punto
> de encuentro que además sirva para oficializar los equipos de trabajo.
[Ricardo Meza talks about creating a wiki page for es-* localizations as a meeting point to oficialize teams]
Actually, is the registration bug along with the wiki page which oficializes each localization team, AFAIK. Having a common page could be interesting, though, if we really find common material to put in it.
> * Que exista una sección individual para los integrantes de cada país.
[Invididual sections in the es-* wiki page for each country member]
Individual wiki pages already exist for each localization (not country), so pointers to them should be used instead.
> * Crear una sección de consulta común que incluya referencias, guías, tips,
> mejores prácticas, fuentes, FAQ's y demás contenidos que faciliten el proceso
> y permitan reusar el trabajo (si los amigos de Argentina o España lo desean,
> al inicio nos podrían dar una gran ayuda incluyendo sus valiosas
[Ricardo Meza advocates creating a common reference section including guides, tips, best practices, sources and references, FAQs and other contents easing L10n process and reusing]
Except for english-spanish style guides, about which I've commented previously, I think most of those contents should be useful for any localization and, therefore, should be in english for everybody to be able to use it.
Notwithstanding this, we actually have a "welcoming" document for new localization efforts at Proyecto NAVE in spanish:
> * Contribuir en las secciones antes mencionadas con las nuevas experiencias
> que los recién llegados tengamos.
[Ricardo Meza suggests to promote contributions from newcomers in the proposed wiki references page]
Again, I think that is important not just for spanish members, but for all L10n members. I'd say even more, feedback from new localization teams about existing L10n documentation is encouraged and well received.
I think this conversation should take place in newsgroup mozilla.dev.l10n (or mirrored mailing list, whose address I don't remember right now). We could be charged of bugspamming if we stay here, I think.
Thank's a lot for all your comments, I'm reading all that links. If I have any questions, do I make it in this place or otherwise?
The best place for questions is the newsgroup:
Ok Gervase, thanks a lot.
Created attachment 298378 [details]
Fx2 es-CL locale / File for Review request
I wonder if one of the Spanish folks could/should do a review on this before me.
(In reply to comment #13)
> I wonder if one of the Spanish folks could/should do a review on this before
> Any volunteers?
I'm taking a look at it.
Created attachment 311435 [details]
Firefox es-CL review
This is not an in-deep review. Per the results, I'd say that es-CL team needs to do a thorough review, probably creating and installing a langpack XPI and testing the program interface by using it for a couple of weeks.
- create a glossary of terms (something like ) and try to fix strings to get a consistent translation for those terms.
- use a reference dictionary for es-CL. I'd say that RAE dictionary  is the normative one for all Spanish variants, but YMMV.
- english messages should be the exception in a fully translated Firefox. Every time you find one while surfing the Net, find out if the message comes from the web site or a non-translated string in Firefox.
BTW, there are a LOT of strings that would sound weird to a Spaniard, and probably the opposite will be true for es-ES vs. an Argentinian or Chilean, so I guess there is really a point in having several es-* translations. :-)
Hi es-CL team:
How are you doing with your localization? I see a recommendation in Comment #15 from Ricardo about making a language XPI.
It also appears that there were some Fx2 requests of the Mozilla team. If possible, could you provide an update? I would love to hear where you are in the process and where we can help
One question I had: Have you decided to work on localizing Firefox 3?
If you have started, thank you for all of your work at localizing. We're at the unique point of determining if you should localize for Firefox 3 or move onto localizing for Firefox 3.1, depending on your availability and interest.
If you are interested in working on *something* that is stable, you can continue to focus on localizing Firefox 3. We can get stable builds going for you. However, we will eventually ship your work in Firefox 3.1 and you will need to update the effort you are putting into Firefox 3 right now. The good news is that the string changes from Fx 3 --> Fx 3.1 are presently small in number (~30), so the update should not be too much too handle.
However, if you are interested in moving your effort toward localizing Firefox 3.1, then you can read the following documentation on working with Mercurial and getting a local environment set up on your machine.
or learn the basics about Mercurial here:
Thanks so much for your hard work. As always, ping us with any questions, we are ready to help.
We have translated this pages to Spanish (thanks to Ricardo) :
and interesting article: http://developer.mozilla.org/es/FAQ_de_Mercurial
You can also send me an email if you need more help because our translation (es-ES) has begun to use hg to the next Firefox 3.1. I don't know if es-AR has begun to work with hg...
Sethb: Hmmm. We are using Narro for translate Firefox 3.x to our locale.
I have a question about Mercurial: The requirements for get a committer account are the same as the requirements for a CVS account or not?
Glad you are using Narro. Hope that has worked well and I know Alexandru has been very helpful if you run into trouble...but you probably know that.
Regarding the committer process, Gerv is still the keeper of that process. Current CVS committers just need to sign a new Committers Agreement. People who want new access have to go through the same process of getting people to vouch for them, etc.
Just keep pinging me in this bug and when we get closer to a finished translation and registration time, we will coordinate it together. Does that seem clear and fair?
One more thought...
Everybody who wants access to Mozilla repositories needs the following:
- an ssh key
- a signed contributor form
The voucher piece is handled a bit ad-hoc for l10n compared to contributors to the main repositories.
Hope that helps even more.
(In reply to comment #20)
> Hi Emilio:
I'm Pablo and recently with Emilio and Eduardo (who hasn't post here) have launched ChileMoz. The last months we've working very hard to make real our project. The idea is to localize Mozilla products to our beloved country :D. He's a little out of time so I'm taking his place for now :).
> Glad you are using Narro. Hope that has worked well and I know Alexandru has
> been very helpful if you run into trouble...but you probably know that.
Alexandru has been very nice and a lot of help when I'd troubles.
> Regarding the committer process, Gerv is still the keeper of that process.
> Current CVS committers just need to sign a new Committers Agreement. People
> who want new access have to go through the same process of getting people to
> vouch for them, etc.
I don't understand very well this point. It's necessary for us to become committers? The process looks oriented to developers.
> Just keep pinging me in this bug and when we get closer to a finished
> translation and registration time, we will coordinate it together. Does that
> seem clear and fair?
We are very close to finish the localization, I think in one or at most two weeks es-CL will be 100% translated (right now is 89%).
(In reply to comment #21)
> Hi Emelio:
> One more thought...
> Everybody who wants access to Mozilla repositories needs the following:
> - an ssh key
> - a signed contributor form
> - vouchers.
When you localize and don't code... How you can get vouchers?
> The voucher piece is handled a bit ad-hoc for l10n compared to contributors to
> the main repositories.
Sorry, I don't understand what you tried to tell u_u.
> Hope that helps even more.
Created attachment 354376 [details]
Fx3.1b3pre updated locale tarball
I'll make a quick review from the new tarball, I'm just finished downloading it.
(In reply to comment #22)
> (In reply to comment #20)
> I don't understand very well this point. It's necessary for us to become
> committers? The process looks oriented to developers.
Yes, you must commit your translated files to Mozilla servers. When you do that, you get nightlies automatically generated on ftp.mozilla.org
I'm trying to keep the translation updated every day and it's easier to see if there are some errors.
> When you localize and don't code... How you can get vouchers?
> > The voucher piece is handled a bit ad-hoc for l10n compared to contributors to
> > the main repositories.
> Sorry, I don't understand what you tried to tell u_u.
They are telling you that if the translation is ok, you'll get the voucher. That means, you'll get the authorization to upload files.
Created attachment 360338 [details]
language pack for b3pre, b3 for testing
This is a language pack for testing, generated from the source in attachment 354376 [details]. I had to do a bit of l10n-merge and hand-editing, but this should install in both current 1.9.1 nightlies as well as the upcoming Firefox 3.1 Beta 3.
Technically, there are a few missing strings by now, which is totally fine. The stats from compare-locales look good,
90% of entries changed
What I'd like to see is another pass on an actual review of the Spanish here, thus the attached language pack.
Quick review. I'm writing this with es-CL langpack enabled.
The langpack install ok. Everything is working.
There are some accesskeys that need to match a letter in the label. e.g.: Marcadores (B)
Some strings still appear in english, but Axel just said that.
Maybe there are some minor typos.
I can say that this revision is almost ready and it could be used as a beta. With a little effort they can make it work to release RC1.
Emilio, Pablo, please send me an email if you need more details.
Axel & Marcelo: Thanks.
I started the process for get a Mercurial (Hg) account (Please see bug 475267)
Created attachment 360622 [details]
b3pre-b3 updated tarball
Updated b3pre-b3 tarball with certain strings fixed.
A couple of things I noticed:
- in the cookies dialog you explain in the text that the use can click on 'Permitir Para la Sesión' but the button is labelled 'Permitir por esta sesión'
- in the color picker dialog the category is called 'colores de link' but the dialog uses 'enlace' (link) everywhere
- in the language dialog picker, you use 'idioma' everywhere, but the selector says 'Seleccione un lenguaje...'
- in the security pane, maybe it's a Chileanism but the sentence 'Bloquear sitios informados de falsificación' sounds like the sites have been informed of their behaviour, I think 'sospechados' or 'conocidos' would make more sense for reported
- '...stored on your computer' is sometimes translated as '... almacenados en su computador' and sometimes as '... almacenados en su equipo' (personnally I prefer equipo)
- in the security setting dialog, you use formal You and subjonctive for all options 'Vaya...' except for 'Dejo una página...' which is in indicative first person.
- the string 'start private browsing' is not translated
- the about box is not translated
Created attachment 366232 [details]
Firefox 3.1b4 locale tarball - updated version
Emilio, does your latest tarball take into account the comments I made in #29 ? thanks
(In reply to comment #31)
> Emilio, does your latest tarball take into account the comments I made in #29 ?
Created attachment 368957 [details]
Firefox 3.5b4 updated tarball with new strings translated
Comment on attachment 368957 [details]
Firefox 3.5b4 updated tarball with new strings translated
intl.menuitems.insertseparatorbeforeaccesskeys in toolkit/chrome/global/intl.properties is translated, it should be either true or false. I have reset that to true, as in en-US. I removed the en-US search plugins, too, the files get picked up from the en-US dirs by the build anyway. Please don't do any changes to either search or region.properties without bugs and reviewed patches, we'll file bugs to get the initial revision done in a moment.
Congratulations, the shipping bugs are filed.
Marking FIXED, I'll head over to your account bug and do the vouching.