openerp-india team mailing list archive

[Yves Hoyos <1125280@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Hi,

The self.pool.get('ir.translation')._get_source() not always choose the right translation term when type is code.
The source module isn't used to differenciate the terms.

Example: 
Module "Fruit"
  en_US: Apple --> fr_FR: Pomme
Module "Macintosh"
  en_US: Apple --> fr_FR: Apple

So if I write de following code in file Fruit/test.py:
  raise(_('Message'), _('Apple'))
I wiil have, in fr_FR:
  Message: Pomme

For the same code in file Macintosh/test.py, I wiil have, in fr_FR:
  Message: Pomme
But I should have
  Message: Apple

You should take care of the source module, from where the _() function
is called. Or at least add an optionnal parameter the help select the
good translation term.

** Affects: openobject-server
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Server.
https://bugs.launchpad.net/bugs/1125280

Title:
  [7.0] Wrong translation term for type code

Status in OpenERP Server:
  New

Bug description:
  Hi,

  The self.pool.get('ir.translation')._get_source() not always choose the right translation term when type is code.
  The source module isn't used to differenciate the terms.

  Example: 
  Module "Fruit"
    en_US: Apple --> fr_FR: Pomme
  Module "Macintosh"
    en_US: Apple --> fr_FR: Apple

  So if I write de following code in file Fruit/test.py:
    raise(_('Message'), _('Apple'))
  I wiil have, in fr_FR:
    Message: Pomme

  For the same code in file Macintosh/test.py, I wiil have, in fr_FR:
    Message: Pomme
  But I should have
    Message: Apple

  You should take care of the source module, from where the _() function
  is called. Or at least add an optionnal parameter the help select the
  good translation term.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-server/+bug/1125280/+subscriptions