[trunk/7.0]OE chatter's doesn't translate created objects in mail_thread widget

Hi Sandy Carter,

Thanks for your contribution.
The fix from your branch: lp:~savoirfairelinux-openerp/openobject-addons/7.0_mail_thread_translate_bug1262000 is working fine.
Soon our experts will review and merged this with stable 7.0 addons branch.

Regards,
Amit Dodiya

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?

@maddie
To export the description into the .po file I just put _() around it.

example:
from openerp.tools.translate import _

class simplenote_note(orm.Model):
    _name = 'simplenote.note'
    _description = _('A simple Note')

Hello Sandy Carter,

>> To export the description into the .po file I just put _() around it.
The above issue is already fixed with following branch:
branch: lp:~openerp-dev/openobject-addons/7.0-opw-601820-ado
revision-id: <email address hidden>
revision-no: 9707

Regards,
Amit Dodiya

Hi Sandy,

Thanks for your advice.

But some of the strings in the official addons don't get exported sometimes, is it also because of this?

@maddie, you could take a look on links attached, I don't have any translation export problem since using their fixes in production.

https://bugs.launchpad.net/openobject-server/+bug/906821
https://bugs.launchpad.net/openobject-server/+bug/1029344
https://code.launchpad.net/~openerp-dev/openobject-server/6.1-opw-581687-cbi

@Yann

Thanks a lot, I will take a look at the links.

Hello,

This may work for some models by some but _description is not translated by default. Fixing it this way in Sandy's merge prop will not be coherent. By luck you may have translation for res.groups but not others.
We should find a cleaner solution.
In Amit's commit, adding manually _description string is not a valid solution either. Quite overkill. Should be done globally.

In other models we use the subtypes (eg: project.task) which are translated.

Regards

@Martin
This was discussed in ocb, the proposed MP for openobject-server guarantees that _description is exported in the translation files