translation terms conflict: address state should be "federal state" (vs. document status)

Bug #918086 reported by Marco Dieckhoff
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Odoo Server (MOVED TO GITHUB)
Fix Released
Low
OpenERP's Framework R&D

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?

Related branches

Revision history for this message
Olivier Dony (Odoo) (odo-openerp) wrote :

Hi Marco,

You're right, our translation system does not yet support the concept of contextualized translations, so the only case where you can provide different translations for the same english source term is when they belong to different modules (1 module = 1 translation domains).

We should look into introducing contextualized translations, but we'd need to double-check if Launchpad translations support it, and then enhance the OpenERP API to support them as well.

In the mean time, your suggestion to rename the "State" field for addresses and companies to "Federal State" is a good workaround. Let's do that as a first step.

Thanks for reporting!

Changed in openobject-server:
importance: Undecided → Low
milestone: none → 6.1
status: New → Confirmed
assignee: nobody → OpenERP's Framework R&D (openerp-dev-framework)
summary: - Wrong combination of translation terms
+ translation terms conflict: address state should be "federal state" (vs.
+ document status)
Revision history for this message
Numérigraphe (numerigraphe) wrote :

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.

Revision history for this message
Olivier Dony (Odoo) (odo-openerp) wrote :

Update: the "State" field of the Company and Bank-related object was renamed to "Fed. State", in accordance with the existing convention for normal address objects. The translation template was updated, and should be available for translators on the Launchpad translation system approximately tomorrow morning at 8:00 AM UTC/GMT.

This was applied on trunk (server) at revision 3970 revid: <email address hidden>

Thanks for reporting!

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

Note: as the "Fed. State" term already existed and was translated in most languages, there should in fact be no action needed for most translation teams. A simple update of the server code to rev.3970 should provide correct translations upon the next restart.

@Numérigraphe: there is no specification or work-in-progress yet about context-sensitive translations. Of course translators would be notified if such a change was planned. In fact it would make sense to discuss the options with them, and that could be the next step, after some initial technical investigation to identify our options. There is no roadmap for this, so feel free to initiate the topic on the mailing-list. BTW, we always ask translation team leaders to join and subscribe to the localization expert list, so they should all follow it.

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.