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

Marko Lindqvist <[email protected]> Sat, 25 Feb 2023 03:13:47 +0200
Newsgroups gmane.games.freeciv.internationalization
Message-ID <CAF6bG8eOrhmmkb4msDfQwF6hCn7ijRBWPuFjZt5cfotpzXTYYg@mail.gmail.com>
--000000000000f1976205f57bf569
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sat, 25 Feb 2023 at 02:04, Hugo Morales <[email protected]> wrote:

> 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 match
> the expected locale.
>

 Ok. I'll arrange that soon.


>
> 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 Lati=
n
> 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
>

The important thing here is what are the locale settings of, e.g. , typical
Mexican or Argentinian users. We want your translation to end in use too,
not to be just present somewhere on the hard drive ;-)
Do they have "es_419" listed, or is it typically along the lines of "es_AR"
as primary, "es_MX" as secondary, and "es" as final fallback?
Unfortunately this might be rather OS specific.

Maybe we should have es_419, but (as long as we don't have exact
country-specific translations) have links to it (or build-time made copies)
as es_MX, es_AR etc?

Sorry for being so ignorant about all this.

I'll check some systems to see what are the localization settings actually
available on those + try to see what other projects have done in this
respect (but we should do better, of course ;-)
Fortunately we don't need to know the final code to get you started with
translating.


 - ML

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Sat, 25 Feb 2023 at 02:04, Hugo Mo=
rales &lt;<a href=3D"mailto:[email protected]">[email protected]<=
/a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><=
div dir=3D"ltr"><div style=3D"font-family:verdana,sans-serif">
<div><div style=3D"font-family:verdana,sans-serif">Happy Friday!</div><br><=
/div><div></div><div>Thank you very much for your kind 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 much </span>appreciate<span=
 class=3D"gmail_default" style=3D"font-family:verdana,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 avoid any mistakes or leave =
translations that don=E2=80=99t match the expected locale.</div></div></div=
></blockquote><div><br></div><div>=C2=A0Ok. I&#39;ll arrange that soon.<br>=
</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><d=
iv dir=3D"ltr"><div style=3D"font-family:verdana,sans-serif"><div style=3D"=
font-family:verdana,sans-serif"><br></div><div style=3D"font-family:verdana=
,sans-serif">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"><br></div><div style=3D"font-family:ver=
dana,sans-serif">On the other hand, the language code is a bit more complic=
ated. You are correct in stating 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 its locale, Spanish (Mexico). As the translations =
to be provided will be in international standardized Spanish but taking int=
o account the Latin American region (Central America, South America and the=
 Caribbean), the level 2 canonicalization should be es_419. For more inform=
ation on this locale, see:<ul><li> ISO 639-1 - <a href=3D"https://www.iso.o=
rg/standard/22109.html" target=3D"_blank">https://www.iso.org/standard/2210=
9.html</a></li><li><a href=3D"https://www.wikidata.org/wiki/Q56649449" targ=
et=3D"_blank">https://www.wikidata.org/wiki/Q56649449</a></li><li><a href=
=3D"https://datahub.io/core/language-codes#resource-language-codes" target=
=3D"_blank">https://datahub.io/core/language-codes#resource-language-codes<=
/a></li><li><a href=3D"https://www.localeplanet.com/icu/es-419/index.html" =
target=3D"_blank">https://www.localeplanet.com/icu/es-419/index.html</a></l=
i></ul><div>
Let me know if that sounds good to you.

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

</div><div><div dir=3D"ltr"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><di=
v><span style=3D"font-family:verdana,sans-serif"><span class=3D"gmail_defau=
lt" style=3D"font-family:verdana,sans-serif">Hugo</span></span></div></div>=
</div></div></div></div></div></div></blockquote><div><br></div><div>The im=
portant thing here is what are the locale settings of, e.g. , typical Mexic=
an or Argentinian users. We want your translation to end in use too, not to=
 be just present somewhere on the hard drive ;-)</div><div>Do they have &qu=
ot;es_419&quot; listed, or is it typically along the lines of &quot;es_AR&q=
uot; as primary, &quot;es_MX&quot; as secondary, and &quot;es&quot; as fina=
l fallback? <br></div><div>Unfortunately this might be rather OS specific.<=
br></div><div><br></div><div>Maybe we should have es_419, but (as long as w=
e don&#39;t have exact country-specific translations) have links to it (or =
build-time made copies) as es_MX, es_AR etc?</div><div><br></div><div>Sorry=
 for being so ignorant about all this.<br></div><div><br></div><div>I&#39;l=
l check some systems to see what are the localization settings actually ava=
ilable on those + try to see what other projects have done in this respect =
(but we should do better, of course ;-)<br></div><div>Fortunately we don&#3=
9;t need to know the final code to get you started with translating.</div><=
div><br></div><div><br></div><div>=C2=A0- ML</div><div><br></div></div></di=
v>

--000000000000f1976205f57bf569--