Re: Why ISO language codes shouldn't be trusted

Hi,

While standards are good, they are always a step behind the real world,
 and the story of internationalization is a prime example of that, where
often the initial standards are created with the best of intentions, but
require subsequent adjustments to get it right -- I am sure that
eventually the folk in the region will get this sorted out with ISO so
that it makes sense for them.

In the meantime, I think the technological limitations of today should
not get in the way of people using AbiWord in a sensible way -- I
personally would like to see these translations in before we release 2.6.

> So let me reiterate, my earlier suggestion to get
> around the ISO code problem:
>
> http://www.runasimipi.org/abiword/ayn-BO.po
> becomes "aym-BO.po" and is listed as "Aymara (La Paz)"
>
> http://www.runasimipi.org/abiword/ays-BO.po
> becomes "ayc-BO.po" and is listed as "Aymara (Oruro)"
>
> http://www.runasimipi.org/abiword/qu3-BO.po
> becomes "quh-BO.po" and is listed as "Quechua (3
> vowels)"
>
> http://www.runasimipi.org/abiword/qu5-BO.po
> becomes "qul-BO.po" and is listed as "Quechua (5
> vowels)"

This sounds pretty reasonable to me (and there is nothing stopping us
from revisiting this later to make if/when a better solution becomes
available).

I have opened a bug so we do not loose track of this,

http://bugzilla.abisource.com/show_bug.cgi?id=11238

Amos, could you please adjust those .po files along the lines you
suggested and then attach them to the bug ?

Tomas
Received on Fri Oct 19 09:23:00 2007