Update __STDC_ISO_10646__, and general Unicode character data issues

Carlos O'Donell carlos@systemhalted.org
Thu May 10 20:22:00 GMT 2012


On Thu, May 10, 2012 at 3:37 PM, Joseph S. Myers
<joseph@codesourcery.com> wrote:
> Do we have any locale experts interested in sorting out the various
> bits of Unicode and related data in glibc properly?  I think the tasks
> would include:
>
> * Ensure the character type data in localedata/charmaps/i18n can be
>  properly reproduced from Unicode 5.0 data using gen-unicode-ctype.c,
>  adapting gen-unicode-ctype.c as needed to replicate any changes that
>  may have been made not using that program.
>
> * Update the character type data to Unicode 6.1, removing any local
>  hacks from gen-unicode-ctype.c that are no longer needed.
>  (10646:2012, corresponding to Unicode 6.1, appears to be in
>  publication stage so should be out very soon.)
>
> * Ensure the character data in localedata/charmaps/UTF-8 can be
>  reproduced in some automated fashion from Unicode 6.0, locating any
>  previously used automation for this or creating some new automation
>  if any previous automation can't be found.
>
> * Update the character data to Unicode 6.1, removing any local hacks
>  in the automation from the previous step.
>
> * Document thoroughly on the wiki how the automation works and how to
>  do updates to new Unicode versions.
>
> * Figure out the origins of the localedata/locales/iso14651_t1_* files
>  and whether it's possible to update them usefully from Unicode data.
>
> ISO 10646 and 14651 are freely available from
> <http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html>.

This looks like a very useful breakdown of tasks.

Please make sure this data should go into the wiki as a project:
http://sourceware.org/glibc/wiki/HomePage#ProjectTODO

Either in generic or a locale specific section.

I have no comment on the patch.

Cheers,
Carlos



More information about the Libc-alpha mailing list