Comment 18 for bug 434266

A workaround for this issue was implemented in 6.0 [1] and 6.1 [2], and will be ported to trunk along with the next batch of corrections. It is similar to the patch suggested by Jay in comment #13, and works by translating in the language of the user performing the action, when no specific context can be found.
There is a limitation to this workaround: some operations are performed using temporarily elevated privileges (i.e. sudo mode), and in that case the language of the admin user will be used instead. This might be suitable for most companies where all employees speak the same language, but large international companies should make sure the admin language is set to a common language that everyone can understand (e.g. english).

Note: The workflow engine will still not propagate the context, because that requires a big refactoring and carries major risks, and it would be deprecated very soon anyway, when the new OpenERP API is implemented [3]. There is also no reason to propagate context except for translations, because the workflow itself should not depend on the context: it should operate exclusively based on the state of the documents - and should always fulfill the same 'contract'. So if translations work, there is no need to propagate the context anymore. This is why we can consider the bug fixed.

Thanks for your patience!

[1] server revno 3627 revision-id: <email address hidden>
[2] server revno 4226 revision-id: <email address hidden>
[3] the new ORM API that was introduced during OpenERP Open Days 2012 in Brussels