From: Rafal Luzynski <digitalfreak@lingonborough.com>
To: Mike FABIAN <mfabian@redhat.com>, libc-alpha@sourceware.org
Cc: Siddhesh Poyarekar <siddhesh@gotplt.org>
Subject: Re: [PATCH 2/2] Add new locale: ckb_IQ (Kurdish/Sorani spoken in Iraq) [BZ #9809]
Date: Tue, 14 Jan 2020 23:09:40 +0100 (CET) [thread overview]
Message-ID: <92994978.1038459.1579039780291@poczta.nazwa.pl> (raw)
In-Reply-To: <s9dimleie1q.fsf@taka.site>
I am unable to verify most of the changes here but I believe they
are correct. Here are just few remarks:
14.01.2020 10:26 Mike FABIAN <mfabian@redhat.com> wrote:
>
>
>
> Add new locale: ckb_IQ (Kurdish/Sorani spoken in Iraq) [BZ #9809]
>
> Part 1 of the patch is what was submitted by the contributor.
> Part 2 are my fixes.
>
> From 63a4478070ccaf9eb96ab6bfea147ea52e22073c Mon Sep 17 00:00:00 2001
> From: Mike FABIAN <mfabian@redhat.com>
> Date: Mon, 13 Jan 2020 10:12:07 +0100
> Subject: [PATCH 2/2] Fix ckb_IQ; Add ckb_IQ to SUPPORTED file; Add
> ckb_IQ.UTF-8.in collation test file;
If this has to be the subject line of the git commit comment then please
consider shortening it. What about this:
---------------------------------------------------
Fix ckb_IQ [BZ #9809]
Add ckb_IQ to SUPPORTED file.
Add ckb_IQ.UTF-8.in collation test file.
---------------------------------------------------
Also please make sure there are no double spaces unless necessary.
I am not sure if they were in your original message or they were added
by my email client.
Also it's nice to mention the bug number in both commits.
>
> ---
> localedata/Makefile | 2 +
> localedata/SUPPORTED | 1 +
> localedata/ckb_IQ.UTF-8.in | 105 +++++++++++
> localedata/locales/ckb_IQ | 369 +++++++------------------------------
> 4 files changed, 178 insertions(+), 299 deletions(-)
> create mode 100644 localedata/ckb_IQ.UTF-8.in
>
> [...]
> LC_MONETARY
> -int_curr_symbol "<U0049><U0051><U0044><U0020>"
> +int_curr_symbol "IQD "
> currency_symbol "<U062F><U002E><U0639>"
> -mon_decimal_point "<U002E>"
> -mon_thousands_sep "<U002C>"
> +mon_decimal_point "."
> +mon_thousands_sep ","
OK
> mon_grouping 3
> -positive_sign ""
> -negative_sign "<U002D>"
> +positive_sign "+"
> +negative_sign "-"
This is not a simple change because it replaces an empty string
in the positive_sign field with "+". Are you sure this is correct?
> [...]
> -
> LC_MESSAGES
> -yesexpr "<U0628><U06D5><U06B5><U06CE>"
> -noexpr "<U0646><U06D5><U062E><U06CE><U0631>"
> +yesexpr "^[+1yY<U0628>]"
> +noexpr "^[-0nN<U0646>]"
Correct!
Otherwise this patch is either correct or I am unable to verify.
I don't give my "Reviewed-by" because this review is very incomplete.
But unless anyone else opposes feel free to push it.
Of course, we need a permission from Siddhesh (CC)
Regards,
Rafal
next prev parent reply other threads:[~2020-01-14 22:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 9:26 [PATCH 2/2] Add new locale: ckb_IQ (Kurdish/Sorani spoken in Iraq) [BZ #9809] Mike FABIAN
2020-01-14 22:09 ` Rafal Luzynski [this message]
2020-01-15 2:32 ` Siddhesh Poyarekar
2020-01-15 9:01 ` Mike FABIAN
2020-01-15 9:18 ` Siddhesh Poyarekar
2020-01-15 9:00 ` Mike FABIAN
-- strict thread matches above, loose matches on Subject: below --
2020-01-15 9:18 Mike FABIAN
2020-01-15 21:20 ` Rafal Luzynski
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=92994978.1038459.1579039780291@poczta.nazwa.pl \
--to=digitalfreak@lingonborough.com \
--cc=libc-alpha@sourceware.org \
--cc=mfabian@redhat.com \
--cc=siddhesh@gotplt.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).