c2c-oerpscenario team mailing list archive

[xrg <xrg@xxxxxxxxx>]

On Monday 27 December 2010, you wrote:
> ** Project changed: openobject-addons => openobject-server

Sorry, are you suggesting that in  selection([('foo', 'Some foo'), ('bar', 
'Other bar')],... ) we let 'foo' and 'bar' be translated?

If so, I would definitely and absolutely disagree. It could bring havoc to the 
way the framework works.

The "internal names", the technical keywords of selection fields, are NOT 
supposed to vary. They are keywords for the database, should actually not be 
visible in the UIs or reports (but rather be replaced by their "display" 
names, eg 'Some foo' and 'Other bar').

If, on the other hand, you see the internal names being used for display 
purposes, eg. "foo" printed in a report, that's some other kind of bug we need 
to solve, agreed.

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/481130

Title:
  Internal name of State field is not translated.

Status in OpenObject Server:
  Confirmed

Bug description:
  PackingList
the label "Shipping Address" and the filed content of "state" is not translated to partners language