openerp-india team mailing list archive
-
openerp-india team
-
Mailing list archive
-
Message #05187
[Bug 918086] Re: translation terms conflict: address state should be "federal state" (vs. document status)
Dear Olivier,
When contextualized translations become available, please make sure the localization experts and the translation teams are made aware of it.
Thanks in advance.
Lionel.
--
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/918086
Title:
translation terms conflict: address state should be "federal state"
(vs. document status)
Status in OpenERP Server:
Confirmed
Bug description:
I noted that "state" on the company settings in German was translated
as "Status", not as "Bundesland" (federal state).
When I tried to correct it on https://translations.launchpad.net
/openobject-
server/trunk/+pots/base/de/+translate?search=state&show=all&memo=20&start=20,
I found it originated from different sources:
Located in field:ir.actions.todo,state:0
field:ir.module.module,state:0
field:ir.module.module.dependency,state:0
field:publisher_warranty.contract,state:0 field:res.bank,state:0
field:res.company,state_id:0 view:res.country.state:0
field:res.partner.bank,state_id:0 view:res.request:0
field:res.request,state:0 field:workflow.instance,state:0
field:workflow.workitem,state:0
This is of course a problem.
On ir.actions.todo or ir.module.module, state would be certainly be "Status" (logical/programmatic state)
On res.band or res.company like here, state should be "Bundesland" (federal state)
Is there a way to split the translation origins in launchpad? Or do we
have to rename "state" to "federal state" first on the forms where it
applies?
To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-server/+bug/918086/+subscriptions
References