public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Lewis Hyatt <lhyatt@gmail.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: David Malcolm <dmalcolm@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libcpp: Update cpp_wcwidth() to Unicode 14.0.0
Date: Sun, 26 Jun 2022 14:16:35 -0400	[thread overview]
Message-ID: <CAA_5UQ7sUkGp9PB71+4Lrf2ZLJevPv0mvdZUtzAmpm_Wgf3OXg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2206241921530.77392@digraph.polyomino.org.uk>

On Fri, Jun 24, 2022 at 3:26 PM Joseph Myers <joseph@codesourcery.com> wrote:
>
> On Fri, 24 Jun 2022, David Malcolm via Gcc-patches wrote:
>
> > > BTW, is this something simple enough I should just commit it without
> > > bugging
> > > the list for approval?
> >
> > The patch seems reasonable to me, but Joseph seems to be the expert on
> > i18n-related matters.
> >
> > Joseph, do we have a policy on this?
>
> I don't think we have a policy on Unicode updates specifically, but the
> general principle for updating files maintained outside GCC and copied
> verbatim into the GCC sources doesn't require prior approval.
>
> (Note that Unicode data is also used to generate ucnid.h - data for
> Unicode characters in identifiers - we should probably also include
> DerivedNormalizationProps.txt and DerivedCoreProperties.txt in the
> checked-in Unicode data for that purpose.)

Thank you both for the feedback. I have pushed the change for wcwidth,
and then I will follow up with a patch that adds these other two
Unicode data files and updates contrib/unicode/README so that the
procedure there will update both wcwidth and ucnid.h... and the patch
will follow that procedure to update ucnid.h from Unicode 13 to
Unicode 14.

-Lewis

      reply	other threads:[~2022-06-26 18:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 21:49 Lewis Hyatt
2022-06-24 18:25 ` David Malcolm
2022-06-24 19:26   ` Joseph Myers
2022-06-26 18:16     ` Lewis Hyatt [this message]

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=CAA_5UQ7sUkGp9PB71+4Lrf2ZLJevPv0mvdZUtzAmpm_Wgf3OXg@mail.gmail.com \
    --to=lhyatt@gmail.com \
    --cc=dmalcolm@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.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).