exported po files are buggy for gettext utils

[Andriy Podanenko]

When we exporting po file
it contains untranslated strings with filled source and destination with english
But when I want to use some of the gettext utils (msgattrib FE) - I can't export untranslated strings from po file - all strings are translated (translation = source)
This is really bug, inapropriate usage po format

Can we export filled translated and empty untranslated from openerp?

Buggy

#. module: email_template
#: help:email_template.account,auto_delete:0
msgid "Permanently delete emails after sending"
msgstr "Permanently delete emails after sending"

Has to be exported

#. module: email_template
#: help:email_template.account,auto_delete:0
msgid "Permanently delete emails after sending"
msgstr ""

[Olivier Dony (Odoo) (odo-openerp)]

Hello Andriy,

That's a good point, thanks for reporting!

However let me add some more details:
- this behavior only affects the exports done manually using the Translation Terms Export wizard within OpenERP, not the actual PO files that contain the effective translations and are autonomously managed by Launchpad's translation system, based on the online translations.
- we do not routinely export any PO files with the Translation Terms Export wizard, we only export the templates (POT) to serve as reference for translators, and of course contain only empty translations
- the Web and GTK projects do not have any system for exporting PO files, they only have tools to export templates (POT), and thus they are not affected by this issue (thus I will invalidate the bug affectation for these 2 projects)

Based on the above, the priority of this issue should be Wishlist, as it only affects a small uncommon use-case, and has no visible consequence for users. But having good tools for translators is very important too (and the patch should be trivial), so let's raise the priority to "Low" :-)

Thanks!

[Andriy Podanenko (podarokua)]

I`d select clients, cause they have option for exporting po files BTW
And possibly we can handle it at the client side

[Andriy Podanenko (podarokua)]

However let me add some more details too:
[quote]- this behavior only affects the exports done manually using the Translation Terms Export wizard within OpenERP, not the actual PO files that contain the effective translations and are autonomously managed by Launchpad's translation system, based on the online translations.[/quote]
YUP!

[quote]- we do not routinely export any PO files with the Translation Terms Export wizard, we only export the templates (POT) to serve as reference for translators, and of course contain only empty translations[/quote]
Nope!
GTK+ and WEB clients already do export into semitranslated buggy PO format via Import/Export Translations WIzard

[quote]- the Web and GTK projects do not have any system for exporting PO files, they only have tools to export templates (POT), and thus they are not affected by this issue (thus I will invalidate the bug affectation for these 2 projects)[/quote]
As I posted above - they have wizard when user can select PO format for desktop translation

[quote]Based on the above, the priority of this issue should be Wishlist, as it only affects a small uncommon use-case, and has no visible consequence for users. But having good tools for translators is very important too (and the patch should be trivial), so let's raise the priority to "Low" :-)[/quote]
Don`t understand Wishlist priority - with current gettext behavior user can`t export translation into po file for importing it into another openerp database with merge feature for translations

[Olivier Dony (Odoo) (odo-openerp)]

On 08/11/2011 12:16 PM, Andriy Podanenko wrote:
> [quote]- we do not routinely export any PO files with the Translation
> Terms Export wizard, we only export the templates (POT) to serve as
> reference for translators, and of course contain only empty
> translations[/quote]
> Nope! GTK+ and WEB clients already do export into semitranslated
> buggy PO format via Import/Export Translations WIzard

Actually, this wizard is implemented in the 'base' module (i.e. part of
the openobject-server), the clients only "render" it, like any other
view or wizard coming for the OpenERP Addons.
Therefore the logic for exporting the PO files is only present in the
server code, and needs to be changed only there.
Sorry if that was not clear in my previous comment.

> Don`t understand Wishlist priority - with current gettext behavior
> user can`t export translation into po file for importing it into
> another openerp database with merge feature for translations

Mind you, OpenERP's import/export wizard does not really have any
"merge" feature, so I suppose you will need external gettext utils anyway.

But that's a good point, we'll also need to make sure that importing a
PO/CSV file with untranslated terms won't empty the existing
translations even if the "override" flag was checked.