[6.0RC1] translation - strange items

[Ferdinand]

in bin_addons_base_i18n_base-de.po
there are many entries like "terp-....."
IMHO these can't be translated and shouldn't be there

[OpenERP buildbot (openerp-buildbot)]

On Tuesday 26 October 2010, you wrote:
> Public bug reported:
>
> in bin_addons_base_i18n_base-de.po
> there are many entries like "terp-....."
> IMHO these can't be translated and shouldn't be there

There is a few items slipping in the translations, that might actually not
worth having, like:
 - names of icons, inside "string" xml elements
 - names of objects, like "ir.attachment", which may 50% worth translating
into "Documents" and 50% really make sense to leave the technical name so that
the admin knows it is "ir.attachment", not any other object.
 - strings of parent classes, like the "invalid xml for view architecture"
 (fill the list of others here)

But, after a closer inspection, the cost of hacking the translation engines to
recognize and exclude those strings may be rather high.

In the sake of keeping the translation engine simple and symmetric, I would
seriously consider ignoring these issues and just telling translators to act
as if those strings are not there.
That's my humble opinion/suggestion.

--
Say NO to spam and viruses. Stop using Microsoft Windows!

[Ferdinand (office-chricar)]

IMHO we should "translate" all this - even if the items shouldn't be there
otherwise no one will know if "untranslated" needs translation or not

[OpenERP buildbot (openerp-buildbot)]

On Tuesday 26 October 2010, you wrote:
> IMHO we should "translate" all this - even if the items shouldn't be there
> otherwise no one will know if "untranslated" needs translation or not

For one, this case proves that the translators (people) are more than a
machine that would match a string to another. They need to have a knowledge of
the context each string is used at; and then judge how to translate.

For the ORM name (eg. "ir.attachment") and the "invalid xml..." case,
translating the term in the local language seems to be the best thing to do.
But, for the first case, the "terp-open" icons, AFAIK a translation may
complicate things[1].

[1] I admit I don't know what will happen, but just express my fear.

--
Say NO to spam and viruses. Stop using Microsoft Windows!

[Ferdinand (office-chricar)]

On Mittwoch 27 Oktober 2010 01:29:28 P. Christeas wrote:
> On Tuesday 26 October 2010, you wrote:
> > IMHO we should "translate" all this - even if the items shouldn't be
> > there otherwise no one will know if "untranslated" needs translation or
> > not
>
> For one, this case proves that the translators (people) are more than a
> machine that would match a string to another. They need to have a knowledge
> of the context each string is used at; and then judge how to translate.
>
> For the ORM name (eg. "ir.attachment") and the "invalid xml..." case,
> translating the term in the local language seems to be the best thing to
> do. But, for the first case, the "terp-open" icons, AFAIK a translation
> may complicate things[1].
>
>
>
> [1] I admit I don't know what will happen, but just express my fear.
With "translate" I ment - just copy the string like "ir.attachment" to the
target language

Best Regards

ChriCar Beteiligungs- und Beratungs- GmbH
http://www.chricar.at/ChriCar/index.html
Dr. Ferdinand Gassauer
Official Tiny Partner

[Olivier Dony (Odoo) (odo-openerp)]

I agree that icon names etc. should not normally be exported as translatable terms.
I'm forwarding this for further investigation, to see if a simple technical solution can be found to avoid this minor issue.

Doing a "dummy" translation for these terms in Rosetta is a correct workaround indeed, for the time being.

Thanks for the report!

[Olivier Dony (Odoo) (odo-openerp)]

Many spurious terms, including icon names and source code things have been removed from pot files, and the code has been fixed to avoid exporting them (revision 3042 and some additional ones coming soon as well). Expect all these terms to disappear from the Rosetta web interface soon.