I've just browsed the server code a bit, and of course there are places where 'en_US' must be retained as the default language because (as Fabien stated) it's the base language for reports, field names, help texts etc.
However, it seems that we could easily tweak the server to make ir_translations having type='model' refer to another language but en_US.
That would allow users to store data in the company's language without the server dispatching strings to ir_translations at all, and so it would not impose them a fake translation process.
Lionel
I've just browsed the server code a bit, and of course there are places where 'en_US' must be retained as the default language because (as Fabien stated) it's the base language for reports, field names, help texts etc.
However, it seems that we could easily tweak the server to make ir_translations having type='model' refer to another language but en_US.
That would allow users to store data in the company's language without the server dispatching strings to ir_translations at all, and so it would not impose them a fake translation process.
Lionel