Japanese translations not updated in nightly builds

Bug #1015411 reported by Vincent Prouillet
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Server (MOVED TO GITHUB)
Won't Fix
Undecided
OpenERP Publisher's Warranty Team

Bug Description

Hi,

After installing the latest 6.1 nightly build (wget http://nightly.openerp.com/6.1/nightly/src/openerp-6.1-latest.tar.gz , which gives the build from the 19/06 at the time of the bug report), I realized that the translations made in Launchpad were not pulled into it.

For example : the module purchase https://translations.launchpad.net/openobject-addons/6.1/+pots/purchase/ja/+translate is almost completely translated and yet the .po file in the purchase module is mostly untranslate.
If I download the .po from launchpad, everything is correctly translated, as you can see in the attachment.

Could you make it so the translations are really pulled in the next nightly builds ?
Thanks.

Tags: maintenance
Revision history for this message
Vincent Prouillet (vincent-prouillet-deactivatedaccount) wrote :
Changed in openobject-server:
assignee: nobody → OpenERP Publisher's Warranty Team (openerp-opw)
tags: added: maintenance
Revision history for this message
Vincent Prouillet (vincent-prouillet-deactivatedaccount) wrote :

Any news on that ?

Revision history for this message
Olivier Dony (Odoo) (odo-openerp) wrote :

Hi,

Apparently this is caused by bug 987199 in Launchpad itself. The translations are shared between series, i.e. newer translations on trunk are automatically be copied in 6.1, and the other way around. However there seems to be a missing link, something that would tell Launchpad that the new translations should be exported in other series. Only the series where the terms were originally changed is automatically marked for export.

It seems that the Japanese translation team has been recently working in the trunk series when translating, so as a result of this bug, the .po files are only updated in the source code for the trunk series, not the 6.1 series.

There is unfortunately not much we can do to fix this properly ourselves, we have to wait for Launchpad to fix it.

In the mean time we have two simple workarounds (albeit tedious):

1) To force an export of the updated 6.1 po files, the translation team can simply "touch" any of the 6.1 translations, like translate one of the missing terms, or perform a dummy change on an existing translations. They must be sure to work in the 6.1 series here[1]

2) From now on and until the bug is fixed, it would be better to update translations always via the 6.1 series rather than the trunk series, to make sure that the 6.1 .po files are always up to date. The trunk files will be updated in the future anyway because we will update the translation template for 7.0, and that will certainly force a new export.

Sorry for the inconvenience. I will update the translation documentation to mention this. I'll also close the bug as 'Won't Fix' to indicate that we cannot fix it ourselves. I'd rather not make it a duplicate of bug 987199 because it is an indirect result of that bug, but not exactly a duplicate.

[1] https://translations.launchpad.net/openobject-addons/6.1/+lang/ja

Changed in openobject-server:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.