some more translatable fields

[Ferdinand]

translatable fields for modules base and product

thinking of arabic, cyrilic etc many more fields have to be declared as translatable
so I set also most "Name" fields (Product, Partner, Contact) to translatable.

Just let me know if this is OK for further modules ...

[Fabien (Open ERP) (fp-tinyerp)]

It has no sense to put such fields as translatable. Nobody will translate them. Translatable fields are more complex to manage (when you change a value, you must change in all language, otherwise you may have different values which is confusing).

[Ferdinand (office-chricar)]

I agree with "... complex"

But how to print a product list in French, English and German ?

and there are a some fields in the patch which should be translated nevertheless - pls have a look
* Partner Functions
* Titles
* Partner Categories
* Countries (Austria - Österreich)
* Partner Events (Channel, ....)

[Ferdinand (office-chricar)]

AND ...
I had already a lot of arguments showing the demo to German speaking people and a lot of terms are not translated ....

So if you think the terms mentioned above should not go into the "base" we should prepare modules
demo_data_german, demo_data_french etc which either replace the English terms or make the fields translatable.
IMHO much more work than settings the fields translatable in the base configuration.

[Fabien (Open ERP) (fp-tinyerp)]

Hello,

> and there are a some fields in the patch which should be translated nevertheless - pls have a look
> * Partner Functions
> * Titles

I don't think we should translate these 2. For examples, it has no sense
for titles to translate SPRL to Pvt. Ltd.. I think it's the same for
partner function. For some business, partner function are crititcal and
can be hard to translate: kings, doctors, lawyers. Putting the wrong
title on a letter can be an offense for some people. So I think it's
better to encode two titles: Mister, Monsieur if you manage 2 languages.

> * Partner Categories

Yes, this is already translatable.

> * Countries (Austria - Österreich)

Ok, I agree, I changed. (but I think this can generate more problems
than you can think of. I see bad users that changed the name of the
country instead of changing the country on the partner form, this was
unmanageable with translations because with some languages, you did not
noticed this inconsistency.)

> * Partner Events (Channel, ....)

Create a blueprint for this. I think ot's more complex than you think we
can not just put a translate=True.

Thanks for the feedback.

--
Fabien Pinckaers
CEO Tiny - OpenERP Editor
Chaussée de Namur 40
B-1367 Grand-Rosière
Belgium
Phone: [phone]
Fax: [phone]
Web: http://openerp.com

Great Achievements Start With Tiny Investments
   -- Marty, 2005

[Thorsten Vocks (OpenBig.org) (openbig.org)]

I would agree with Fabien but Ferdinand you are also right.

We have also a demand for demo_data_german. As is understand everything right, this would be a use case for base_module_recording? I still have problems with usage (bug?), but normally this will be the best.

In a first step we will have

->demo_data_german service companies

and later

-> demo_data_german manufacturing and so on...

This will fit maybe better for specific branches demo_data

e.g. healthcare for example
Partner functions:
- laboratory provider
- radiology
- nurses
- doctor
....

[Ferdinand (office-chricar)]

pls see blueprint/discussion here
https://blueprints.launchpad.net/openobject-server/+spec/translation-update