[Sugar-devel] Fwd: [sugarlabs/terminal-activity] Albanian strings and delete aym.po (#21)

[Chris Leonard]

for anyone else wondering about aym.po deletions.

---------- Forwarded message ----------
From: Chris Leonard <cjlhomeaddress at gmail.com>
Date: Sun, Oct 30, 2016 at 8:23 PM
Subject: Re: [sugarlabs/terminal-activity] Albanian strings and delete
aym.po (#21)
To: sugarlabs/terminal-activity <
reply+004d55d493499968512606d795b2ececce3becb45a63a58592cf00000001142e3d6492a169ce0b1852c8 at reply.github.com
>
Cc: sugarlabs/terminal-activity <terminal-activity at noreply.github.com>,
Mention <mention at noreply.github.com>


Gonzalo,

tldr
Because it is the wrong code to use for Aymara.

aym was an early choice of isocode for Aymara, unfortunately it is a
macrolanguage code and thereby might tend to crowd out use of more specific
language codes for Aymara (there are distinct language codes ayc and ayr
that are more specific under the Aymara macrolanguage code aym).  All of
our Aymara work is captured under the ayc code and the aym files are
redundant.

Our variation of Aymara is ayc (as common in Peru, and distinct from ayc,
which is more Bolivian).  The upstream glibc locale for Linux is ayc_PE.

The aym files we have are redundant and less complete that those under ayc
in Pootle and our repos.  It makes sense to clean them out when the
opportunity presents itself to avoid confusion.

I'm writing up a policy that I'll be pushing on the glibc and CLDR locale
development communities that strongly discourages the use of macrolanguage
codes in locale development in favor of the more specific language codes
nested under the macrolanguage isocode, whereever possible.

This actually a wider problem with indigenous language families and our use
of quz for Quechua (Cusco-Collao) is intended to avoid similar issues of
confusion with the other 37 members of the qu macrolanguage.  It is in
keeping with the United Nations Declaration of the Rights of Indigenous
Peoples to respect their diverse cultural heritages by honoring
distinctions made as to language classification while still working within
the accepted ISO-639 standards family.  It is just the right thing to do.


cjl

On Sun, Oct 30, 2016 at 6:59 PM, Gonzalo Odiard <notifications at github.com>
wrote:

> @leonardcj <https://github.com/leonardcj> , just to know, why remove the
> aym translation?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/sugarlabs/terminal-activity/pull/21#issuecomment-257186466>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AE1V1MDj-i7CjbvViQ_uO2pRSxOEIYLAks5q5SFkgaJpZM4KkaE5>
> .
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20161030/7bf9d12b/attachment.html>