openerp-india team mailing list archive

Thread
Date

[Bug 324852] Re: Field account.account.name field is no longer translatable

To: openerp-india@xxxxxxxxxxxxxxxxxxx
From: Lorenzo Battistini - Agile BG - Domsense <lorenzo.battistini@xxxxxxxxxxx>
Date: Fri, 24 Feb 2012 17:57:52 -0000
Reply-to: Bug 324852 <324852@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Hello,
I don't think this is illegal everywhere. At least it isn't in Switzerland. It's important to keep the same account code, but the name can be translated.
A typical example is when staff speaks a language different from the management's one. In this case, I would avoid duplicating journal entries just for translation, of course.

** Changed in: openobject-addons
       Status: Invalid => New

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/324852

Title:
  Field account.account.name field is no longer translatable

Status in OpenERP Addons (modules):
  New

Bug description:
  Same with fields :
  account.account.template.name
  account.tax.template.name
  account.tax.code.name

  Is this intentional ?

  I have attached patch anyhow in case this was not intentional.

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