c2c-oerpscenario team mailing list archive

[xrg <xrg@xxxxxxxxx>]

On Friday 15 October 2010, you wrote:
> Hello Guys,
> 
>      IMHO it would not be feasible to first load es.po and then the
> es_XX.po files because we can have the overhead of having the same
> procedure two times. 

The overhead of loading the translation 2 times is not important, IMHO, 
because that only happends during a DB upgrade, which is 5min every so many 
months that you would keep the db.
But it just doesn't yet work that way. Currently, you cannot load both es.po 
and es_XX.po for the same module.

What I said in the first place is to only have es_XX.po for those modules where 
terms are different (eg. account, stock, purchase - perhaps), but keep only an 
es.po for the modules that can share terms (eg. idea, lunch, wiki, event). 
See?

-- 
[Trunk] Languaje es_XX should be extended to countries in latinoamerica
https://bugs.launchpad.net/bugs/660933
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to OpenERP OpenObject.

Status in OpenObject Server: Confirmed

Bug description:
Hello.

IMHO, we should count with the lenguages availables around all countries where there are community working around openERP, Spanish is speaked in almost 22 countries, not only Spain and Argentina (the last one has not done almost anything in them translation around the last 2 years.) but Spain yes.

We are growing up quickly in LatinAmerica and we think as partners and community members that have available his own commercial lenguaje around OpenERP installes OutOfthebox should be very insteresting to incentivate several more instalations in LA.

I propose a patch with countries where I know there are people working hard with community, and there are partners.

Regards.