c2c-oerpscenario team mailing list archive

["Jay \(OpenERP\)" <jvo@xxxxxxxxxxx>]

Borja,

I confirm this for Trunk.

It happens on stable as well, but as you said it is a regression; can
you please make sure that it wa working on 5.0.12?

If yes, we will consider this.

Thanks.

** Changed in: openobject-server/5.0
       Status: New => Won't Fix

** Changed in: openobject-server/trunk
   Importance: Undecided => Low

** Also affects: openobject-client
   Importance: Undecided
       Status: New

** Changed in: openobject-server/trunk
     Assignee: (unassigned) => OpenERP sa GTK client R&D (openerp-dev-gtk)

** Changed in: openobject-client
       Status: New => Confirmed

** Changed in: openobject-client
   Importance: Undecided => Low

** Changed in: openobject-client
     Assignee: (unassigned) => OpenERP sa GTK client R&D (openerp-dev-gtk)

** Summary changed:

- Regression: one2many widget title and fotter not getting translated on 5.0.13/5.0.14
+ Regression: one2many widget title and footer not getting translated

-- 
Regression: one2many widget title and footer not getting translated
https://bugs.launchpad.net/bugs/661281
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject GTK Client: Confirmed
Status in OpenObject Server: Confirmed
Status in OpenObject Server 5.0 series: Won't Fix
Status in OpenObject Server trunk series: Confirmed

Bug description:
With the lastest versions of the server (5.0.13/5.0.14) some one2many widgets don't get their title translated even when the translation is available.

HOW TO REPRODUCE:

  - Install the lastest version of OpenERP (server, addons, extra-addons).
  - Create a new database with any non-English language, "Services Profile" and Sales.
  - Go to the partners form: The "Partner Contacts" title is not translated.
  - Use the contextual menu (right-click) on a field caption, and select "Translate view".
  - Look for "Partner Contacts": a translation is available but not used!

VERSIONS AFFECTED:

We were able to reproduce the problem on versions 5.0.13 (revno 2107), 5.0.14 (revno 2109) and latest revno 2143. On 5.0.12 (revno 2085) the problem is not present.