[prev in list] [next in list] [prev in thread] [next in thread] 

List:       glibc-locales
Subject:    [Bug localedata/16061] New: Review / update transliteration data
From:       sourceware-bugzilla () sourceware ! org (myllynen at redhat dot com)
Date:       2013-10-18 8:06:00
Message-ID: bug-16061-716 () http ! sourceware ! org/bugzilla/
[Download RAW message or body]

https://sourceware.org/bugzilla/show_bug.cgi?id=16061

            Bug ID: 16061
           Summary: Review / update transliteration data
           Product: glibc
           Version: 2.18
            Status: NEW
          Severity: normal
          Priority: P2
         Component: localedata
          Assignee: unassigned at sourceware dot org
          Reporter: myllynen at redhat dot com
                CC: libc-locales at sourceware dot org

The localedata/locales/translit_* files are probably, based on comments in
them, at least partially generated from some version of UnicodeData.txt (based
on 93a568 it looks like the last major update has been for Unicode 3.2 and
17b16e suggests them originally coming from an external contributor). However,
there are some characters missing even from the Latin-1 Supplement block and in
general it doesn't seem possible to update the files just by using
UnicodeData.txt. Some of the rules live in locale/C-translit.h /
locale/C-translit.h.in which also contain local changes (like 61d5a6 / 2a81ea).

It requires likely a lot of work to understand how the files have been
generated in the first place, how to identify relevant local changes, and how
to automate the process to update them in the future.

Some individual examples of currently missing characters are U+00D8 (?) and
U+0110 (?) whereas other characters like U+00C6 (?) and U+0141 (?) from their
blocks (Latin-1 Supplement and Latin Extended-A, respectively) are present.
Some characters (like U+2033, ?) have decomposition defined as is in Unicode
but some characters (like U+00D6, ?) have decomposition defined in Unicode but
not in glibc.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[prev in list] [next in list] [prev in thread] [next in thread]