I was previously involved with the ca-XV and the Valencian government to push the valencian l10n code for it.
I remember this process was initially approved, but later decided not to go forward by the GVA. Althought there isn't really much I would like to add to the process at this time, just want to offer any help on the future. On 4/21/14, Pau Iranzo <[email protected]> wrote: > Hi, > > My name is Pau Iranzo and I've been the maintainer of the ca-XV translation > until the last version of OOO before it became AOO. I've been following the > discussion and I just wanted to mention that I agree on the proposed > solution: keeping ca-XV for AVL and find a different code for the RACV > version (ca-XR?). > > Regarding working in pootle please create a Pootle account for me. I state > that my contributions are under the Apache 2 license and I will work on > both ca and ca-XV translations. My preferred username is PauGNU. > > Thanks, > Pau > > > > > > 2014-04-21 0:05 GMT+02:00 Andrea Pescetti <[email protected]>: > >> On 20/04/2014 Software Valencià wrote: >> >>> we would like to be supported by OpenOffice so we could save a lot of >>> work. >>> >> >> No problem! Once we get the things set up (warning: this may take a >> while, >> we are about to release version 4.1 -end of April- and we won't do Pootle >> updates before release) you will only have to translate, and we'll >> happily >> do the rest. >> >> >> Valencian language have to rules (AVL and RACV) as other languages like >>> Norwegian, Galician, Serbian... To prevent misunderstandings by users we >>> suggest you to tag our translation as "Valencian (RACV)" so if other >>> team want to translate "Valencian (AVL)" they can do it. We will use >>> "ca-XV" code if it's free, or other like that. >>> >> >> Thanks for this information. I got some further details and indeed I was >> wrong (sorry, I didn't know about the two variants of Valencian). >> >> We have technical limitations that make it necessary to use a kludge >> since >> we can't support BCP-47 tags (so to use an example you mentioned: we use >> "sh" and "sr" for the two variant of Serbian, and they are both wrong, >> but >> we must live with it). >> >> The current ca-XV is the AVL variant. So, even though it is not >> maintained >> at the moment (but it may change soon), we must keep ca-XV for AVL. It's >> an >> unofficial code anyway. >> >> Can we settle on ca-XR for the "Valencian RACV" translation? I'm totally >> inventing it, so stop me if it's crazy. Basically, the logic is that due >> to >> technical constraints we have to use "ca-" to identify the main ISO >> language group, "X" to mean that it is our extension, "R" is randomly >> chosen by me to denote "RACV" and can be changed into anything else if >> you >> prefer. >> >> This way we keep ca-XV open for AVL and ca-XR (or whatever) for RACV and >> you can work in parallel. If this can help you, we can initialize ca-XR >> with the files we have now for ca-XV, even though I assume you will have >> to >> adapt a lot of strings (but it may still be useful as a reference). >> >> >> So, can we start to work to be part of next Apache OpenOffice's release? >>> >> >> Let's agree on these details while we finalize the 4.1 release. Then >> we'll >> update Pootle as soon as possible and all teams can start working again. >> >> >> Regards, >> Andrea. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > -- Alexandro Colorado Apache OpenOffice Contributor http://www.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
