Note: This guide assumes that you are or will be using PO files.
this page needs to be rewriten now that Mozilla is using CSV. The steps are more or less the same. Look at creating mozilla POT files which talks about creating POT file from CVS. Then the process is mostly the same except swap any reference to XPI to be the translations in Mozilla CVS.
If you are not currently using PO files to do your translations then you can migrate an existing XPI to PO format.
Firstly make sure you have an XPI for your language then download a Mozilla English (US) XPI for the same release:
Change 1.7.3 to the release that you need. Note: Linux and Windows langenus.xpi are the same so no need to worry about that.
Now create the Mozilla PO files for your language using your existing XPI and the en-US XPI.
moz2po -t mozilla-1.7.3-langenus.xpi langXXYY.xpi xxYY-1.7.3
You need to create a set of Firefox PO Template files that you will use as templates when you migrate your Mozilla translations. Template files are simply blank PO files.
Rumour has it that the en-US XPI files for Firefox are different for Windows and Linux.
moz2po -P firefox-1.0-en-US.xpi templates-ff-1.0
We will now take the existing Mozilla PO files and migrate them to Firefox. Note that this tool only works on Linux (or an operating environment with bash and the gettext tools). If you need help ask at firstname.lastname@example.org.
pomigrate2 xxYY-1.7.3 xxYY-ff-1.0 templates-ff-1.0
Things that are fully automated scare most people and justifiably so! The migration will do the following:
The result is that all Firefox files are at least initialised. Many of them are populated with conflicting entries clearly highlighted and ready for you to fix.
Your PO files are ready. Begin translating with any of your usual PO editing tools.