716925 - How to import translation from existing Firefox 3.x language packs

Status: RESOLVED WONTFIX

(Mozilla Localizations Graveyard :: Documentation, defect)

Description

[arky [:arky]]

We can silme tools to import older translations. 

Thanks for @dietrich et al for providing this short tutorial. 

>> Subject: langpack xpi -> locale source for Myanmar
>>
>> I picked up things starting about the same place you are now for the
>> Khmer  locale. Here's the summary of the process I went through to
>> convert the  langpack to a new locale source for Firefox 4. I overcame
>> many hurdles with  help from Gandalf and Axel!
>>
>> (Gandalf, please correct any bits below that  are now out of date!)
>>
>> 1. Set up Silme. The tools are here:
>> https://wiki.mozilla.org/Silme:Tools. Clone the Silme hg repo  locally.
>> Put ./silme-apps and ./silme next to each other in a directory.  The
>> script to use is map_structure.py. Usage looks like:  map_structure.py
>> ./your-old-langpack  ./known-good-localization-source
>> ./your-new-localization-from-langpack
>>
>> 2.  Get your langpack ready: Unzip the xpi, and if there's a .jar
>> inside, unzip  that too.
>>
>> 3. Clone a known-good current localization for the target  release. For
>> example, the Poland locale for Mozilla-central (aka Firefox 4).  Do:
>> http://hg.mozilla.org/l10n-central/pl/
>>
>> 4. Run the script. I've  used paths that assume you did all of this in
>> your home directory.
>>
>> cd  ~/silme-apps
>> ./scripts/map_structure.py ~/firefox-3-6-km-KH ~/pl  ~/kh
>>
>> In the above, "firefox-3-6-km-KH" is the folder of the  unzipped
>> langpack xpi, "pl" is the folder of the cloned Polish locale  for
>> Firefox 4, and "kh" is the folder where the mappable bits inside  the
>> 3.6 langpack will have been converted to 4.0 localization  source,
>> ready for checking into a locale branch.
>>
>> During the script  execution, you'll see many things like  this:
>>
>> locale/km-KH/mozapps/downloads/settingsChange.dtd has multiple  matching
>>options:
>>     0)  toolkit/chrome/mozapps/downloads/settingsChange.dtd (matches: 100%)
>>      1) mail/chrome/overrides/settingsChange.dtd (matches: 100%)
>>      2) browser/chrome/overrides/settingsChange.dtd (matches: 100%)
>>      3) None of them
>> Which option is matching:
>>
>> Notice that in the  original question, there's a "mozapps" and in the
>> choices, only one has  "mozapps". Always choose the matching one.
>>
>