c2c-oerpscenario team mailing list archive

["Albert Cervera i Areny - http://www.NaN-tic.com" <albert@xxxxxxxxxxx>]

A Diumenge, 27 de febrer de 2011 11:48:28, xrg va escriure:
> I'm talking about the same thing here. Changing the way the frameworks
> behaves  for a given set of input IS a change of API. Yes, sometimes the
> previous behavior was not the best one (kept you seeing English strings
> that no Spanish person understands, for example), but the rule is to
> improve things only "to behave as expected". Getting translated strings
> from an empty context is not what I would ever expect from the framework.
> (already gave you 2 examples where this is the designed behavior).

Well, its your decision after all. But just for the record of other users 
we've got this patch applied in v5 in several production systems for months 
now with no issues so far. We're going to use it in production systems for v6 
too.

-- 
Albert Cervera i Areny
http://www.NaN-tic.com
OpenERP Partners
Tel: +34 93 553 18 03
skype: nan-oficina

http://twitter.com/albertnan 
http://www.nan-tic.com/blog

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/724057

Title:
  translation needs context but it doesn't always exist

Status in OpenERP Server:
  Confirmed

Bug description:
  OpenERP v6:

  class GettextAlias in tools/translate.py requires a valid context
  available where _() was called. In some cases the context variable
  does not exsits or is not properly initialized. The attached patch
  provides a workarround by searching current user's language in order
  to find to which language it should translate.

  The patch is based on a Jay Vora patch provided in a v5 bug report:
  https://bugs.launchpad.net/openobject-addons/+bug/432504