Evergreen translations that involve PO and POT files are currently hosted on Launchpad translations. (Translations for the Angular staff interface are managed using POEditor). This wiki page will document the basic steps for setting up a new series translation target.

In order to perform these steps, you must have the following privileges in Launchpad:

1. Be a member of the Evergreen Release Team team. This is needed in order to attach a bzr branch to the code series and designate branches to import from and export to for the strings.
2. Be a member of the Evergreen Bugs team. This is needed in order to create bzr branches owned by the evergreen-bugs team to follow the naming convention set up by this procedure.

1. Install Bazaar:

   sudo apt-get install bazaar

2. Setup your bzr account details:

   bzr whoami “FirstName LastName <email@address>”

3. Set launchpad login (replace "launchpadusr" with actual LP username):

   bzr launchpad-login launchpadusr

This procedure uses Evergreen 3.11 as an example. When implementing this procedure, replace rel_3_11 and 3.11 with values appropriate to the series that you are setting up.

1. View Bazaar branches: https://code.launchpad.net/evergreen/+branches
2. Import a branch
   1. Owner: evergreen-bugs
   2. Name: rel_3_11
   3. Git: git://git.evergreen-ils.org/Evergreen.git,branch=rel_3_11
   4. Target source control is bazaar
   5. then request the import and wait for to complete
3. After import done, go to overview for Evergreen in Launchpad, select the corresponding series, configure series branch, then point at the new branch you just created
4. Create a bzr checkout:
   1. bzr branch lp:evergreen/3.11
   2. cd 3.11
5. then push to a new translation-export branch
   1. bzr push lp:~evergreen-bugs/evergreen/translation-export-3.11
6. Now we have a place for LP to send translation exports
7. Go to translations https://translations.launchpad.net/evergreen
8. Choose to do an automatic export for the series
   1. by registering the branch for the series, it recognizes it, so we only need to set the settings
      1. import template and translation
      2. set the translations export branch created earlier
   2. Once the translation automatic sync is set up, you may need to wait for up to a day for the imports and exports to run for the first time.