language export must not set msgstr if it is missing

Bug #915538 reported by Ferdinand
0
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

Revision history for this message
Jignesh Rathod(OpenERP) (jir-openerp) wrote :

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.

Changed in openobject-server:
status: New → Invalid
Revision history for this message
Ferdinand (office-chricar) wrote :

To be honest I do not understand how your answer is related to my question/problem

If I export a module to be translate (not using launchpad) I would like to have an empty string in msgstr to allow to jump to the untranslated terms.

Currently one has to examine every term visually to decide if the "translated" term is English or really translated.

Changed in openobject-server:
status: Invalid → New
Revision history for this message
Olivier Dony (Odoo) (odo-openerp) wrote :

This looks like a simple duplicate of bug 823788

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.