ubuntu-bengali-manual team mailing list archive

[Sense Hofstede <u@xxxxxxxxxxxxxxxx>]

Public bug reported:

Launchpad Translations can automatically import templates and
translations from a branch, but it can also automatically export
translations from Launchpad to a branch. Possible outdated information
about this functionality can be found at
<https://help.launchpad.net/Translations/YourProject/Exports>.

At the moment the translations of the LoCo Directory are manually
exported from Launchpad and then imported into the LoCo Directory. It
would be a lot easier if Launchpad would automatically export all
translations to the branch.

Unfortunately, it does not work with the way Django structures its
locale directory. In order for automatic imports and exports to work,
Launchpad needs to have the translations in the same directory as the
templates, but Django puts them in "locale/XX/LC_MESSAGES/". This breaks
Launchpad.

A possible solution could be to create custom makemessages and
compilemessages commands that store the PO files in same directory as
the POT file, but keep the MO files in the default location, so Django
can find them.

** Affects: loco-directory
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bengali Manual, which is subscribed to loco-directory.
https://bugs.launchpad.net/bugs/748446

Title:
  Find a way to use Launchpad's automatic translations export

Status in LoCo Directory:
  New

Bug description:
  Launchpad Translations can automatically import templates and
  translations from a branch, but it can also automatically export
  translations from Launchpad to a branch. Possible outdated information
  about this functionality can be found at
  <https://help.launchpad.net/Translations/YourProject/Exports>.

  At the moment the translations of the LoCo Directory are manually
  exported from Launchpad and then imported into the LoCo Directory. It
  would be a lot easier if Launchpad would automatically export all
  translations to the branch.

  Unfortunately, it does not work with the way Django structures its
  locale directory. In order for automatic imports and exports to work,
  Launchpad needs to have the translations in the same directory as the
  templates, but Django puts them in "locale/XX/LC_MESSAGES/". This
  breaks Launchpad.

  A possible solution could be to create custom makemessages and
  compilemessages commands that store the PO files in same directory as
  the POT file, but keep the MO files in the default location, so Django
  can find them.