Which fields to translate ?

Registered by Ferdinand

openobject-server> find . -follow -name "*py"|xargs grep -i "name"|grep fields.char|grep -v translate|sort|less
this statement lists name fields which are not translated
 * and does not take into account split lines with translate on the second line

We should consider 2 cases
(1) main company is monolingual
(2) main company is multilingual (Switzerland, Netherlands, US, many multinationals have English as reporting language, but various local languages as working language)

ad(1) if we can assume that the system administrator has IT English working knowledge - only a restricted set of translated names is necessary mainly concerning external partner communication. else -> (2)

ad(2) most/all "names" must be translated.
Example 1: if the administrator of OpenERP has no or poor English knowledge, he/she will not be able to select and configure OpenERP, because much, but not all (=partly translated - IMHO this gives a very incomplete picture) is available in the language which was selected at startup
Example 2: for multinational accounting (consolidation) almost all must be in English and local language.

So I suggest to set most of the name and description fields to translatable.
See also
https://blueprints.launchpad.net/openobject-server/+spec/translation-update

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.