Comment 14 for bug 632760

I have uploaded a fix to lp:~arnegoetje/rosetta/po2xpi-arne which attempts to fix this. The following are the instructions to that person who is handling the language-packs now:

On the server where the language-packs are generated, the following needs to be done:
 * in langpack-o-matic is a subdirectory po2xpi, which should point to po2xpi-arne. in This subdirectory, please use bzr pull lp:~arnegoetje/rosetta/po2xpi-arne
 * to fix this bug in the current packages, do the following:
  1. in maverick/sources-base/language-pack-{bn|en|es|pt|ta|zh}-base/data/ is a mozilla.tar.gz . Untar it in a temporary directory.
  2. it will untar several subdirectories, one per language. In each subdirectory is a chrome.manifest and a firefox-3.6-$LANGCODE.jar file.
  3. in each chrome.manifest replace only the first ll_CC with ll-CC
  4. tar everything up again and replace the mozilla.tar.gz in the language-pack with the new one.
  5. cd ~/langpack-o-matic; for l in bn en es pt ta zh; do cd ../maverick/sources-base/language-pack-${l}-base; dch -v 1:10.10+20100930.1 -D maverick "Fix firefox translations (LP: #632760)"; cd ../; for p in gnome kde; do cd language-pack-${p}-base; dch -v 1:10.10+20100930.1 -D maverick "Version bump, no changes."; cd ../; done; cd ../sources-update/; for p in language-pack-${l} language-pack-gnome-${l} language-pack-kde-${l}; do cd ${p}; dch -v 1:10.10+20100930.1 -D maverick "Version bump, no changes."; cd ../; done; cd ~/langpack-o-matic; echo "../maverick/sources-base/language-pack-${l}-base\n../maverick/sources-base/language-pack-gnome-${l}-base\n../maverick/sources-base/language-pack-kde-${l}-base\n../maverick/sources-updates/language-pack-${l}\n../maverick/sources-updates/language-pack-gnome-${l}\n../maverick/sources-updates/language-pack-kde-${l}" >> updated-packages; done
 6. upload the packages like normal.

@dpm:
This bug seems only to happen when po2xpi runs in devmode, i.e. all exported .po files will be used and not just the officially published .xpi files. If you don't want this, edit the 'import' file in the langpack-o-matic source code and replace line 281 with the next higher ubuntu release number. Or, if you want to use 'devmode' for all releases in future, replace the code with something more appropriate. We ususally change the code in our local branch checkouts of langpack-o-matic, commit the changes and then pull the changes on the server, where we generate the langpacks.
You would need to re-run langpack-o-matic then and bump up the version in the launchpad translation tarball.
If you need my help, contact me on Skype.