User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:126.96.36.199) Gecko/2008072820 Firefox/3.0.1 Build Identifier: Hi, I would like to start a new localization projet for the Mozilla Application suite, for the language kabyle (code kab). My contact details: agrakal, firstname.lastname@example.org, aselkim.free.fr Regards, agrakal Reproducible: Always Steps to Reproduce: 1. 2. 3.
Hi all, In addition, I have created a wiki page https://wiki.mozilla.org/L10n:Teams:kab for the kabyle language. Rgds, agrakal
Hi Agrakal: 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. http://developer.mozilla.org/en/L10n_on_Mercurial or learn the basics about Mercurial here: http://developer.mozilla.org/en/Mercurial Thanks so much for your hard work. As always, ping us with any questions, we are ready to help. Kind regards, Sethb
Hi, all I'm joining Kabyle Mozilla Localisation :)
marking as new as we have 2 volunteers now :)
Status: UNCONFIRMED → NEW
Ever confirmed: true
There hasn't been any visible activity in this project for a while now, I'm resolving this as INCOMPLETE. If there is activity again, please feel free to reopen or file a new bug. Thanks.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.