No all reports must be translatable

Some reports belong to a particular country, then is not required a translation for a report, or the reports with a huge quantity words (eg., contracts) designed for clients, so We could be add new attribute boolean to report model called "translatable", so in case to be "False" the report is ignored by synchronize and set translation, etc.

added type::feature + 1 deleted label

So just left the translations blank, and you will have it.

added 1 deleted label and removed 1 deleted label

The example doen't mean nothing for me.
Could you please provide an use case of such non-translatable report?

added 1 deleted label and removed 1 deleted label

msg17407 (view)
Yes, I leave in blank, but this cause slow performance in set translations, clean and synchronize, etc, creating/processing huge quantity of fields in ir.translation for this report that never will be used, this is not have sense.

msg17409
In human resources management the contract employee is like as:

http://csi.gsb.stanford.edu/sites/csi.gsb.stanford.edu/files/SampleEmploymentContract.pdf

This contract could be a tryton report inside no official module where the user prints employee's job contract, from company_employee for example, or in another case a module with contract service in sales, both reports can have very words in local language not english, so ¿why creates huge quantity records on ir.translation for a report which translation is no required?

Please see this module, is a real example:

https://bitbucket.org/presik/presik_staff_contracting

I saw that this affect the ir_translation model performance, because the model has read very much records useless (by local language report)

I see no reason to be able to translate such document.

Sorry, but I don't understand msg17419

Tryton isn't good with translation of paragraphs in reports, (ok not problem), why? because split each word in translation model, so in this case the translation is useless or bad idea.

The similar case is Issue3432, and take the same words
"It is quite logical because a (chart of account) report a linked to a
country" sometimes of course, so that's why hasn't sense reload ir.translation with records that will never be translated because already are in native language, plus register these reports will impact strongly performance of this model when are registered.

My proposal is just add new attribute called "translatable" to report model, and default for this field is "true", and if a developer/customer no need translation for your report set "false" this attribute.

I can try to create a patch

The reports included by #7484 (closed) are one example of non translatable reports because we are using the reporting engine to generate a text file that should be imported on another system.

Including a wrong translation may break the file format and thus making the file non readable by the other system.

I think in this case makes sense to not be able to translate the report.

added 1 deleted label and removed 1 deleted label

assigned to @pokoli

added accounting trytond + 1 deleted label and removed 1 deleted label

review56361002 updated at https://codereview.tryton.org/56361002/#ps1

I think that if the patch is ready before the last translation update, we should apply it to avoid useless translations.
Also is there only the account_es report that must not be translated?

+1

On 9/6/18 12:54 PM, Cédric Krier wrote:
> I think that if the patch is ready before the last translation update, we should apply it to avoid useless translations.

Ok, lets try to have it ready before the last translation update.

> Also is there only the account_es report that must not be translated?

I think so. account_payment_sepa templates are also a good candidate but they are not registered as reports but loaded directly from the template folder. So I do not think there is any other report that should be not translatable

review56361002 updated at https://codereview.tryton.org/56361002/#ps20001

review56361002 updated at https://codereview.tryton.org/56361002/#ps40001