c2c-oerpscenario team mailing list archive

[Numérigraphe <400256@xxxxxxxxxxxxxxxxxx>]

Thanks Olivier,
My users need this feature, so I'll commit to it. I'll trying hard to KISS, and make it merge-able too.

There are 2 parts in this work :
- some existing code has to be cleaned up, so "international usage" will actually improve
- then I can implement the feature cleanly.
Maybe I can propose a cleanup/refactoring branch for merging when v6 is released?
Then I can propose a feature branch for testing and review later on.

The re-factoring effort itself is not huge but a bit subtle. The main idea is to split translations of bundled strings (fields, help...) from user-entered strings.
I think I have a clear idea of what's needed. I can file a blueprint to explain my implementation plan if you are interested.

Lionel.

-- 
Default language for "model" values hardcoded as 'en_US' should be configurable
https://bugs.launchpad.net/bugs/400256
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject Server: In Progress

Bug description:
In the current v5.0, the default language for data strings in objects is hardcoded to be 'en_US' in the server code.

This complicates usage when the main language in the company is not English.
For example even in a company where all the business is done in French, you cannot change (and correct!) the value of a translatable field in the table, because the new value will be written to ir_translation instead when you don't use en_US.

This is particularly disturbing in companies where English is not used at all.

We should be able to change the default language from en_US to the locale of our choice, preferably at database creation time, or else in the server config file or command-line.

This is only for data strings input by users ("model" values in ir_translate), and the default language for field names, help texts and other stuff must remain en_US.