about summary refs log tree commit diff
path: root/locale/loadlocale.c
diff options
context:
space:
mode:
authorCarlos O'Donell <carlos@systemhalted.org>2017-10-13 14:36:23 -0700
committerCarlos O'Donell <carlos@systemhalted.org>2017-10-13 22:30:19 -0700
commitbc3821bb3b19646311d36c82a13b4ce5afea3508 (patch)
tree3599dd99abd375870c51ccbbe663913dd571d04a /locale/loadlocale.c
parenta3e23a2c1d9e871545c6f438a41fcb8ad429cf70 (diff)
downloadglibc-bc3821bb3b19646311d36c82a13b4ce5afea3508.tar.gz
glibc-bc3821bb3b19646311d36c82a13b4ce5afea3508.tar.xz
glibc-bc3821bb3b19646311d36c82a13b4ce5afea3508.zip
locale: No warning for non-symbolic character (bug 22295)
In "Is it OK to write ASCII strings directly into locale source files?"
https://sourceware.org/ml/libc-alpha/2017-07/msg00807.html there is
universal consensus that we do not have to keep writing <Uxxxx> symbolic
characters in locale files.

Ulrich Drepper's historical comment was that symbolic characters were
used for the eventuality of converting the source files to any encoding
system. Fast forward to today and UTF-8 is the standard. So the
requirement of <Uxxxx> is hard to justify.

Zack Weinberg's excellent scripts are coming along we can use these to
find instances of human errors in the scripts:
https://sourceware.org/ml/libc-alpha/2017-07/msg00860.html
https://sourceware.org/ml/libc-alpha/2017-08/msg00136.html

It still won't be easy to distinguish from i for í, but that's still the
case for <Uxxxx> characters which humans can't read either.

Since we all agreed that we should be able to use non-symbolic (<Uxxxx>)
characters in locale files, the following change removes the verbose
warning that is raised if you use non-symbolic characters in the locale
file.

Signed-off-by: Carlos O'Donell <carlos@redhat.com>
Diffstat (limited to 'locale/loadlocale.c')
0 files changed, 0 insertions, 0 deletions