As a workaround for v5 where this bug can't be fixed, I just pushed a module to 
let the administrator copy all the translations from one language to English.
I'll probably push it to v6 sometime later too, I think it should work as-is in 
v6.

Anyone willing to review the module is weclome at 
https://code.launchpad.net/~numerigraphe/openobject-addons/extra-base-translation-copy/+merge/67418
 .
Lionel Sausin.

** Branch linked: lp:~numerigraphe/openobject-addons/extra-base-
translation-copy

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

Title:
  Default language for "model" values hardcoded as 'en_US' should be
  configurable

Status in OpenERP Server:
  Confirmed

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.

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

_______________________________________________
Mailing list: https://launchpad.net/~openerp-dev-gtk
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~openerp-dev-gtk
More help   : https://help.launchpad.net/ListHelp

Reply via email to