language export must not set msgstr if it is missing
Bug #915538 reported by
Ferdinand
This bug report is a duplicate of:
Bug #823788: exported po files are buggy for gettext utils.
Edit
Remove
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Server (MOVED TO GITHUB) |
New
|
Undecided
|
Unassigned |
Bug Description
all terms seem to be translated in the po file - but are filled with the English terms which makes translation more cumbersom
IIRC in v5 untranslated terms were empty
To post a comment you must log in.
Hello Dr Ferdinand ,
First of all,I would like to remind you in v5 it is working same because
it is a behaviour of framework.
Let me explain the whole thing when we import string as a translation with
" " (Blank String) It will automatically take the English language for that
blank string,now when we export the same it will show us a English translation
on message string because when we exported something we have to know
that which thing we have exported.
For import ,we should know that which thing we are exporting so this is the
behaviour of Import/Export which working same as v5
so this is not a bug and I am closing this issue.
Hope this will help to you.
Thanks for reporting.