launchpad helpLaunchpad Help > Translations > Your Project > Importing translations
Importing your project's translations
Just as with translation templates, you can import translation files (.po) in two ways:
- from your series' default Bazaar branch
- or by uploading a tarball of templates and translation files through the web interface.
Imports from a Bazaar branch
There are two ways to import translation files (.po) from the series' default Bazaar branch:
On your project's translations settings page choose Import template and translation files to automatically import any .po that are in the branch, whenever Launchpad imports .pot files from the branch.
Or go to the Request Bazaar Import page to request a one-time import of all .pot and .po files in the branch.
One time upload through the web interface
Visit your project's translations overview page and click the link for the trunk series. Upload a tarball containing your translation files preserving directory structure.
Naming translation files
To ensure automatic approval and subsequent import of the translation files, you need to follow the translations import policy.
As a rough guide, you should observe these two rules:
- Place the files in the same directory as the template for which they are meant. Each template and its translation files must have its own directory. This rules out the first naming option for templates that was mentioned above.
Name the files according to the language code of the language they contain. So for Spanish translations use es.po.
In addition to that the normal instructions for uploading translation files apply.
Next steps
Launchpad can help you safeguard the quality of the translations you use in your project. Choose a review policy for your project's translations.
