Re: Contributing for a new locale: Spanish as used in Latin America and the Caribbean (es-419)

--0000000000000fe37c05f57afd67
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

 Happy Friday!

Thank you very much for your kind welcome and reply.

First of all, it would be much appreciated having fresh .po files. It will
allow me to avoid any mistakes or leave translations that don=E2=80=99t mat=
ch the
expected locale.

In regards to your suggestion about the branch to use, it has been noted.
Any translations provided will be based on the S3_0 branch!

On the other hand, the language code is a bit more complicated. You are
correct in stating that the language part of the code should be "es", but
the locale cannot be es_MX, since it refers only to one country, Mexico,
and its locale, Spanish (Mexico). As the translations to be provided will
be in international standardized Spanish but taking into account the Latin
American region (Central America, South America and the Caribbean), the
level 2 canonicalization should be es_419. For more information on this
locale, see:

   - ISO 639-1 - https://www.iso.org/standard/22109.html
   - https://www.wikidata.org/wiki/Q56649449
   - https://datahub.io/core/language-codes#resource-language-codes
   - https://www.localeplanet.com/icu/es-419/index.html

Let me know if that sounds good to you.

Hugo


On Thu, Feb 23, 2023 at 9:16 PM Marko Lindqvist <[email protected]> wrote:

> On Fri, 24 Feb 2023 at 03:45, Hugo Morales <[email protected]> wrote=
:
>
>> Dear all,
>>
>> First of all, thank you very much for the amazing work that you have bee=
n
>> doing during the last year to make Freeciv such an amazing experience.
>>
>> I have decided to help with the localization of Freeciv and I would like
>> to contribute with a new locale: Spanish as used in Latin America and th=
e
>> Caribbean (es-419).
>>
>> In that order of ideas, I am trying to get up-to-date with the latest
>> code and tools required for such a task, but any advice or guidance to
>> speed up the task will be much appreciated.
>>
>> Hoping to be of help on the journey.
>>
>
>  Welcome.
>
>  Adding a completely new localization is of course a bit more complicated
> than just updating existing one. But those tasks do not require knowledge
> of the target language, so if you want me to help, I should be able to
> arrange things so that you just get a fresh .po file with nothing
> translated in it.
>  Other than that, I would recommend starting translating the S3_0 branch,
> the branch where releases are currently coming from. So the translation
> (even if partial) would be available in coming releases. And most of the
> S3_0 translation will still be valid for later branches. S3_1 is in beta,
> and 3.1.0-beta1 release is coming out soon, so starting there is another
> option. In any case, starting with the main development branch would mean
> that it would take several years before users see your translation, for t=
he
> first time.
>
>  Have to figure out what language code this would be in the gettext
> system. I think ISO 639-1 part is "es" in any case, but as the "location"
> is always a single country (as far as I know), we might be looking for
> something like "es_MX"?
>
>
>  - ML
>
>

--0000000000000fe37c05f57afd67
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:verdana,=
sans-serif">
<div><div style=3D"font-family:verdana,sans-serif" class=3D"gmail_default">=
Happy Friday!</div><br></div><div></div><div>Thank you very much for your k=
ind welcome and reply.</div><div><br></div><div>First of all, <span class=
=3D"gmail_default" style=3D"font-family:verdana,sans-serif">it would be muc=
h </span>appreciate<span class=3D"gmail_default" style=3D"font-family:verda=
na,sans-serif">d having </span>fresh .po<span class=3D"gmail_default" style=
=3D"font-family:verdana,sans-serif"> files</span>. It will allow me to avoi=
d any mistakes or leave translations that don=E2=80=99t match the expected =
locale.</div><div style=3D"font-family:verdana,sans-serif" class=3D"gmail_d=
efault"><br></div><div style=3D"font-family:verdana,sans-serif" class=3D"gm=
ail_default">In
 regards to your suggestion about the branch to use, it has been noted.=20
Any translations provided will be based on the S3_0 branch!</div><div style=
=3D"font-family:verdana,sans-serif" class=3D"gmail_default"><br></div><div =
style=3D"font-family:verdana,sans-serif" class=3D"gmail_default">On the oth=
er hand, the language code is a bit more complicated. You are correct in st=
ating that the language part of the code should be &quot;es&quot;, but the =
locale cannot be es_MX, since it refers only to one country, Mexico, and it=
s locale, Spanish (Mexico). As the translations to be provided will be in i=
nternational standardized Spanish but taking into account the Latin America=
n region (Central America, South America and the Caribbean), the level 2 ca=
nonicalization should be es_419. For more information on this locale, see:<=
ul><li> ISO 639-1 - <a href=3D"https://www.iso.org/standard/22109.html">htt=
ps://www.iso.org/standard/22109.html</a></li><li><a href=3D"https://www.wik=
idata.org/wiki/Q56649449">https://www.wikidata.org/wiki/Q56649449</a></li><=
li><a href=3D"https://datahub.io/core/language-codes#resource-language-code=
s">https://datahub.io/core/language-codes#resource-language-codes</a></li><=
li><a href=3D"https://www.localeplanet.com/icu/es-419/index.html">https://w=
ww.localeplanet.com/icu/es-419/index.html</a></li></ul><div>
Let me know if that sounds good to you.

</div><div><br></div></div>

</div><div><div dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gma=
il_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div><span style=
=3D"font-family:verdana,sans-serif"><span class=3D"gmail_default" style=3D"=
font-family:verdana,sans-serif">Hugo</span></span></div></div></div></div><=
/div></div></div><br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" =
class=3D"gmail_attr">On Thu, Feb 23, 2023 at 9:16 PM Marko Lindqvist &lt;<a=
 href=3D"mailto:[email protected]">[email protected]</a>&gt; wrote:<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div d=
ir=3D"ltr">On Fri, 24 Feb 2023 at 03:45, Hugo Morales &lt;<a href=3D"mailto=
:[email protected]" target=3D"_blank">[email protected]</a>&gt; w=
rote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex"><div dir=3D"ltr"><div style=3D"font-family:verdana,sans-se=
rif">Dear all,</div><div style=3D"font-family:verdana,sans-serif"><br></div=
><div style=3D"font-family:verdana,sans-serif">First of all, thank you very=
 much for the amazing work that you have been doing during the last year to=
 make Freeciv such an amazing experience.</div><div style=3D"font-family:ve=
rdana,sans-serif"><br></div><div style=3D"font-family:verdana,sans-serif"><=
/div><div style=3D"font-family:verdana,sans-serif">
I have decided=C2=A0to=C2=A0help=C2=A0with=C2=A0the=C2=A0localization=C2=A0=
of=C2=A0Freeciv and I would like to contribute with a new locale: Spanish a=
s used in Latin America and the Caribbean (es-419).</div><div style=3D"font=
-family:verdana,sans-serif"><br></div><div style=3D"font-family:verdana,san=
s-serif">In that order of ideas, I am trying to get up-to-date with the lat=
est code and tools required for such a task, but any advice or guidance to =
speed up the task will be much appreciated.<br></div><div><br></div><div><d=
iv style=3D"font-family:verdana,sans-serif">Hoping to be of help on the jou=
rney.</div></div></div></blockquote><div><br></div><div>=C2=A0Welcome.<br><=
/div><div><br></div><div>=C2=A0Adding a completely new localization is of c=
ourse a bit more complicated than just updating existing one. But those tas=
ks do not require knowledge of the target language, so if you want me to he=
lp, I should be able to arrange things so that you just get a fresh .po fil=
e with nothing translated in it.</div><div>=C2=A0Other than that, I would r=
ecommend starting translating the S3_0 branch, the branch where releases ar=
e currently coming from. So the translation (even if partial) would be avai=
lable in coming releases. And most of the S3_0 translation will still be va=
lid for later branches. S3_1 is in beta, and 3.1.0-beta1 release is coming =
out soon, so starting there is another option. In any case, starting with t=
he main development branch would mean that it would take several years befo=
re users see your translation, for the first time.</div><div><br></div><div=
>=C2=A0Have to figure out what language code this would be in the gettext s=
ystem. I think ISO 639-1 part is &quot;es&quot; in any case, but as the &qu=
ot;location&quot; is always a single country (as far as I know), we might b=
e looking for something like &quot;es_MX&quot;?<br></div><div><br></div><di=
v><br></div><div>=C2=A0- ML</div><div><br></div></div></div>
</blockquote></div>

--0000000000000fe37c05f57afd67--