public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
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 11:09:47 +0000	[thread overview]
Message-ID: <bug-27781-716-FQ28VYJHft@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 #8 from Ilyahoo Proshel <ip at ipshel dot com> ---
(In reply to Mike FABIAN from comment #7)
> Created attachment 14051 [details]
> Slighly improved rif_MA
> 
> I used ASCII characters directly instead of <U...>, for example:
> 
> abday           "L<U1E25>e";/
>                 "Let";/
>                 "Ttl";/
>                 "Lar";/
>                 "Lex";/
>                 "Jje";/
>                 "Sbt"
> 
> Only for non ASCII characters we are still using the <U....> code point
> notation, using the ASCII characters directly makes it a lot more readable.
> 
> I also added:
> 
> lang_name    "Tmazi<U0263>t"
> 
> Does that look OK to you?

Thank you for you help and your work on improving the locale.
everything seems to be ok. Just the name. it's a locale for "Tarifit", and not
"Tmazi<U0263>t". because the last one is another language.

And by the way. we did send the patch for the unmodified locale. and it pass
the build successfully, if you want to take a look here:
https://patchwork.sourceware.org/project/glibc/patch/20220125172555.2527278-1-ip@ipshel.com/

Thank you a lot.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-04-06 11:09 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 [this message]
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
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-FQ28VYJHft@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).