I suspect I see a similar problem with translation sharing between series, and the behavior seems to match Jeroen's description.
The Japanese translations for OpenERP Addons have been updated in the trunk series in the past few days, and are properly shared with the 6.1 series. You can see the changed dates of some terms are 20 june in the UI for the 6.1 series [1].
However if you look at the last update date of the PO file itself [2], it's still 12 june, and indeed the last export for the 6.1 series was on june 13 [3]. The PO files are exported correctly in the trunk series however [4].
This is quite a problem, because our workaround would be to "touch" the templates in the 6.1 series every time they are changed in the trunk series, in order to force an export.... possibly requiring hundreds of manual operations every day. Good luck explaining this to the translation teams ...
An offline process to detect this and patch the POFile.date_changed in the database directly would be great.
Is there any chance we can do it ourselves using launchpadlib? It does not seem to expose the actual PO database, only the import queue and translation groups.
Note: the dates I quoted may not be accurate for long as we will have to manually "touch" the templates in order to trigger the missing exports.
I suspect I see a similar problem with translation sharing between series, and the behavior seems to match Jeroen's description.
The Japanese translations for OpenERP Addons have been updated in the trunk series in the past few days, and are properly shared with the 6.1 series. You can see the changed dates of some terms are 20 june in the UI for the 6.1 series [1].
However if you look at the last update date of the PO file itself [2], it's still 12 june, and indeed the last export for the 6.1 series was on june 13 [3]. The PO files are exported correctly in the trunk series however [4].
This is quite a problem, because our workaround would be to "touch" the templates in the 6.1 series every time they are changed in the trunk series, in order to force an export.... possibly requiring hundreds of manual operations every day. Good luck explaining this to the translation teams ...
An offline process to detect this and patch the POFile.date_changed in the database directly would be great.
Is there any chance we can do it ourselves using launchpadlib? It does not seem to expose the actual PO database, only the import queue and translation groups.
Note: the dates I quoted may not be accurate for long as we will have to manually "touch" the templates in order to trigger the missing exports.
[1] https:/ /translations. launchpad. net/openobject- addons/ 6.1/+pots/ purchase/ ja/+translate /translations. launchpad. net/openobject- addons/ 6.1/+pots/ purchase bazaar. launchpad. net/~openerp/ openobject- addons/ 6.1/view/ head:/purchase/ i18n/ja. po#L17 bazaar. launchpad. net/~openerp/ openobject- addons/ trunk/view/ head:/purchase/ i18n/ja. po#L17
[2] https:/
[3] http://
[4] http://