From: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
To: libc-alpha@sourceware.org, fweimer@redhat.com
Subject: Re: [PATCH v4 3/4] Regenerate localedata files.
Date: Thu, 29 Apr 2021 17:03:41 -0400 [thread overview]
Message-ID: <2383a0d8-6f10-bfe8-8f45-98e228f8f219@redhat.com> (raw)
In-Reply-To: <20210428130033.3196848-4-carlos@redhat.com>
On 4/28/21 9:00 AM, Carlos O'Donell wrote:
> Regenerate the locale data files from the Unicode 13.0 data using
> the newly updated localedata/unicode-gen/utf8-gen.py script.
>
> The regeneration is done automatically via 'make install' from
> the localedata/unicode-gen directory.
>
> Only localedata/charmaps/UTF-8 has changed, but we commit the
> date changes to all other files to indicate that we have run
> 'make install' to automatically update everything.
>
> Tested on x86_64 and i686 without regression.
> ---
> localedata/charmaps/UTF-8 | 4396 ++++--------------------
> localedata/locales/i18n_ctype | 2 +-
> localedata/locales/tr_TR | 2 +-
> localedata/locales/translit_circle | 2 +-
> localedata/locales/translit_cjk_compat | 2 +-
> localedata/locales/translit_combining | 2 +-
> localedata/locales/translit_compat | 2 +-
> localedata/locales/translit_font | 2 +-
> localedata/locales/translit_fraction | 2 +-
> 9 files changed, 700 insertions(+), 3712 deletions(-)
With this patch applied:
https://sourceware.org/pipermail/libc-alpha/2021-April/125595.html
This patch reduces down to just the localedata/charmaps/UTF-8 update,
as expected.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2021-04-29 21:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 13:00 [PATCH v4 0/4] Add new C.UTF-8 locale (Bug 17318) Carlos O'Donell via Libc-alpha
2021-04-28 13:00 ` [PATCH v4 1/4] Add support for processing wide ellipsis ranges in UTF-8 Carlos O'Donell via Libc-alpha
2021-04-29 14:11 ` Florian Weimer via Libc-alpha
2021-04-28 13:00 ` [PATCH v4 2/4] Update UTF-8 charmap processing Carlos O'Donell via Libc-alpha
2021-04-29 14:07 ` Florian Weimer via Libc-alpha
2021-04-29 21:02 ` Carlos O'Donell via Libc-alpha
2021-04-30 4:18 ` Florian Weimer via Libc-alpha
2021-05-02 19:18 ` Carlos O'Donell via Libc-alpha
2021-04-28 13:00 ` [PATCH v4 3/4] Regenerate localedata files Carlos O'Donell via Libc-alpha
2021-04-29 21:03 ` Carlos O'Donell via Libc-alpha [this message]
2021-04-28 13:00 ` [PATCH v4 4/4] Add generic C.UTF-8 locale (Bug 17318) Carlos O'Donell via Libc-alpha
2021-04-29 14:13 ` Florian Weimer via Libc-alpha
2021-04-29 20:05 ` Carlos O'Donell via Libc-alpha
2021-04-30 17:59 ` Carlos O'Donell via Libc-alpha
2021-04-30 18:20 ` Florian Weimer via Libc-alpha
2021-05-02 19:18 ` Carlos O'Donell via Libc-alpha
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=2383a0d8-6f10-bfe8-8f45-98e228f8f219@redhat.com \
--to=libc-alpha@sourceware.org \
--cc=carlos@redhat.com \
--cc=fweimer@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).