The comment added by Stephane above is a OPW request that was declined as feature request, not a bug.
I still think it is a bug, as the field translate is present in ir.model.fields, with a help text that indicates it's uses.
'translate': fields.boolean('Translate', help="Whether values for this field can be translated (enables the translation mechanism for that field)"),
There is also a checkbox on the Administration - Customization - Database Structure - Fields form.
But they don't work at all - the field is simply not filled when orm.py initializes the models.
In my book, that's a bug.
Therefore I propose the fix as developed by xrg in the link in the post above as merge request.
The comment added by Stephane above is a OPW request that was declined as feature request, not a bug.
I still think it is a bug, as the field translate is present in ir.model.fields, with a help text that indicates it's uses. boolean( 'Translate' , help="Whether values for this field can be translated (enables the translation mechanism for that field)"),
'translate': fields.
There is also a checkbox on the Administration - Customization - Database Structure - Fields form.
But they don't work at all - the field is simply not filled when orm.py initializes the models.
In my book, that's a bug.
Therefore I propose the fix as developed by xrg in the link in the post above as merge request.