Comment 3 for bug 1015411
Revision history for this message
| Olivier Dony (Odoo) (odo-openerp) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
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:/