User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.60 Safari/534.30 Build Identifier: I'd like to request a new Firefox localization in Luxembourgish, ISO-code: "lb". I have assembled a team of three to four people and we have started translating in a private Subversion repository. We are already done with the immediately visible UI as well as with most of the dialog windows. A current build of the langpack is available here: http://michel.weimerskirch.net/firefox-lb/ What's the procedure to import our source code into an official repository. Reproducible: Always
*** This bug has been confirmed by popular vote. ***
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: New localization: Luxembourgish (lb) → [lb] New localization: Luxembourgish
Summary: [lb] New localization: Luxembourgish → [lb] [Fx] New localization: Luxembourgish
Created attachment 743550 [details] [lb] translations updated to Aurora 22 I've migrated the translations in that XPI to Aurora 22. This is the same files updated to Aurora 22.
The translations are available here http://mozilla.locamotion.org/lb/firefox/ For testing you can use the updated Aurora 22 XPI from http://downloads.locamotion.org/aurora/22/firefox-22.0a2.lb.langpack.xpi
The translations mentioned in comment 2 are at 37% so I didn't ask for a review.
This locale registration bug is being resolved as INCOMPLETE because it has not been updated since before the final Firefox 17esr release on 2013-11-15. It is assumed that there has not been any progress in developing the desired localization since that time. If you feel this bug has been closed in error, please reopen it and provide a status update for your locale. In addition, please be sure to follow the guidelines listed on the wiki for creating a new localization: https://wiki.mozilla.org/L10n:Starting_a_localization [Mass change filter: l10n-new-incomplete-fx17esr]
Severity: enhancement → normal
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.