From: "ip at ipshel dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/27781] Please add the new rif_MA locale
Date: Wed, 06 Apr 2022 16:47:32 +0000 [thread overview]
Message-ID: <bug-27781-716-vO4GC9u4fK@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27781-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27781
--- Comment #12 from Ilyahoo Proshel <ip at ipshel dot com> ---
(In reply to Mike FABIAN from comment #11)
> (In reply to Mike FABIAN from comment #9)
> > https://en.wikipedia.org/wiki/Tarifit
> >
> > The wikipedia article said that the endonym (The name of the language in
> > itself) is Tmaziɣt or Tarifiyt or Tarifect and I did just choose the first
> > one.
> >
> > According to Wikipedia, “Tarifit” is the name of the language in English.
> >
> > lang_name should contain the endonym whereas
> >
> > language "Tarifit"
> >
> > should contain the English name.
>
> Wikipedia> Its own speakers simply call it "Tamazight", a term also often
> applied Wikipedia> in a broader sense to the Berber language across North
> Africa in Wikipedia> general.
Tamazight is the mother language where multiple other languages inherited from
it. Including Tarifit.
And what’s apply for Tarifit does mean that can apply for another sub-tamazight
languages, and vice versa. So we believe that lang_name should be “Tarifit”.
Should we resend the patch by email with your improvements?
Thank you very much for your time.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-04-06 16:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-27781-716@http.sourceware.org/bugzilla/>
2021-04-27 15:44 ` ip at ipshel dot com
2021-08-11 16:31 ` gunnarhj at ubuntu dot com
2021-08-17 17:11 ` ip at ipshel dot com
2021-08-17 17:12 ` ip at ipshel dot com
2021-11-12 21:28 ` carlos at redhat dot com
2022-01-22 18:35 ` ip at ipshel dot com
2022-01-22 18:35 ` ip at ipshel dot com
2022-01-22 18:36 ` ip at ipshel dot com
2022-01-24 11:33 ` adhemerval.zanella at linaro dot org
2022-04-05 6:46 ` maiku.fabian at gmail dot com
2022-04-06 6:10 ` maiku.fabian at gmail dot com
2022-04-06 11:09 ` ip at ipshel dot com
2022-04-06 15:54 ` maiku.fabian at gmail dot com
2022-04-06 15:56 ` maiku.fabian at gmail dot com
2022-04-06 16:03 ` maiku.fabian at gmail dot com
2022-04-06 16:47 ` ip at ipshel dot com [this message]
2022-04-07 8:31 ` maiku.fabian at gmail dot com
2022-04-07 13:29 ` cvs-commit at gcc dot gnu.org
2022-04-07 13:39 ` maiku.fabian at gmail dot com
2022-04-07 13:43 ` ip at ipshel dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-27781-716-vO4GC9u4fK@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libc-locales@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).