Comment 3 for bug 1262000

Hi,

We've found this problem a long time ago, and used the same technique to try solving this problem.

However, although this method works just fine, there is another problem:

This function looks into ir.translation model for the string, where 'type' equals [code].

So far it seems to work fine, but considering the origin string didn't exist before this patch, we will have to try adding the translation by exporting the PO file, adding the translation then import it back to OpenERP.

But just when you have exported the PO file and try to find the newly untranslated string, you'll discover that it wasn't being exported at all.

We found that there are also some other strings with type 'code' in ir.translation model won't get exported either.

Any way to solve this problem?