On Fri, Jun 24, 2022 at 3:26 PM Joseph Myers <jos...@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
