Does this means that localizers decide the language code? I mean, if a team from Venezuela decides to start a new localization in Spanish and they say: "this is Venezuelan, code vz or qvz", should we accept that translation? Even knowing that this is Spanish from Venezuela?.
Valencian and Catalan are the same language and there is already a code for Valencian locale: ca_XV (or ca-valencia accepted by the IANA). The Valencian localizers have been using qcv_ES in their linux distribution (Liurex) for a while avoiding whatever related to the name "Catalan" and using the qcv_ES instead. It is very important for us (people who speak Catalan/Valencian) to be identified with the same code. It doesn't make sense to be identified as different languages. The Valencian localizers should change their original code qcv for the ca-valencia or ca_XV and not the other. If not, the name for this localization cannot be "Valencian". Pau Iranzo El dt 30 de 03 de 2010 a les 08:19 -0600, en/na Alexandro Colorado va escriure: > Unfortunately the localizers are not, since they do the work on this > locale, they want it to remain as original. After some talks with Eike > the best solution is the qcv_ES choice which already works on the > localizer internal build and could work for ours as long as they keep > it on the UI level and get it out of store documents. > > On 3/30/10, Jesús Corrius <jcorr...@gmail.com> wrote: > > Hi Alexandro, > > > >> Internally we suggested qcv_ES originally because that is the legacy > >> built works and is also a reserved locale in spain. > >> > >> Alternatively there could be a xv_ES which would be a good alternative > >> since it uses the user-asigned variables. > > > > I am perfectly fine with Eike's proposal of CA_XV for the moment until > > the BCP47/RFC5646 language tags are implemented. I think this is the > > way to go, taking into account that is a provisional solution. > > > > Regards, > > > > -- > > Jesús Corrius > > http://www.corrius.org > > > >
