From: Albert ARIBAUD <albert.aribaud@3adev.fr>
To: Mike FABIAN <mfabian@redhat.com>
Cc: GLIBC Devel <libc-alpha@sourceware.org>,
Pravin Satpute <psatpute@redhat.com>,
Jens Petersen <petersen@redhat.com>
Subject: Re: [PATCH] Update the i18n, UTF-8 and translit_* files to Unicode 9.0.0
Date: Wed, 29 Jun 2016 15:24:00 -0000 [thread overview]
Message-ID: <20160629172338.06d1613b.albert.aribaud@3adev.fr> (raw)
In-Reply-To: <s9da8i4kpri.fsf@redhat.com>
Hi Mike,
On Wed, 29 Jun 2016 16:56:17 +0200, Mike FABIAN <mfabian@redhat.com>
wrote :
> Unicode 9.0.0 has been released recently (2016-06-21).
>
> Here is a patch to update the i18n, tr_TR, UTF-8, and the translit_*
> files to Unicode 9.0.0.
Typo, probably:
> diff --git a/NEWS b/NEWS
> index e2737d5..5960274 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -6,6 +6,11 @@ Please send GNU C library bug reports via
> <http://sourceware.org/bugzilla/> using `glibc' in the "product"
> field.
> Version 2.24
> +* Unicode 8.0.0 Support: Character encoding, character type info, and
~~~~~
This should be 9.0.0, should it not?
> + transliteration tables are all updated to Unicode 9.0.0, using
> + generator scripts contributed by Mike FABIAN (Red Hat).
> + These updates cause user visible changes, such as the fix for bug
> + 20313.
Cordialement,
Albert ARIBAUD
3ADEV
next prev parent reply other threads:[~2016-06-29 15:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 14:57 Mike FABIAN
2016-06-29 15:24 ` Albert ARIBAUD [this message]
2016-06-29 15:41 ` [PATCH v2] " Mike FABIAN
2016-06-29 16:18 ` Mike Frysinger
2016-06-29 17:25 ` Joseph Myers
2016-06-30 7:09 ` [PATCH v3] Update the i18n, UTF-8 and translit_* files to Unicode 9.0.0 [BZ #20313] Mike FABIAN
2016-11-02 13:58 ` [PATCH v4] " Mike FABIAN
2017-02-21 13:32 ` Carlos O'Donell
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=20160629172338.06d1613b.albert.aribaud@3adev.fr \
--to=albert.aribaud@3adev.fr \
--cc=libc-alpha@sourceware.org \
--cc=mfabian@redhat.com \
--cc=petersen@redhat.com \
--cc=psatpute@redhat.com \
/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).