This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: About hex ranges in charmap files
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: oplnykis at vfemail dot net
- Cc: "libc-help at sourceware dot org" <libc-help at sourceware dot org>
- Date: Fri, 5 May 2017 10:28:48 -0400
- Subject: Re: About hex ranges in charmap files
- Authentication-results: sourceware.org; auth=none
- References: <20170505134754.Horde.jFeVhRIlvk3JM98yrg1HFth@www.vfemail.net>
On Fri, May 5, 2017 at 9:47 AM, <oplnykis@vfemail.net> wrote:
> Hello. I was looking at charmap files, and I found the use of hex
> ranges, which is not specified in POSIX. I asked about it here
> <https://unix.stackexchange.com/questions/362800/how-to-interpret-char>.
> The answer says that it's glibc's undocumented behavior. Is it right?
The charmap man page maintained by the linux man pages project is not
official documentation for glibc. And while the man page does document
the <Uxxx>..<Uyyy> range format it is not officially documented by
glibc. In fact the whole process of writing locales is absent from the
official glibc manual, instead relying on upstream POSIX documentation
to provide the basis for this behaviour. That does indeed mean that
there is a lot of undocumented dark corners here, and that's a
problem. We would be happy to have someone working on the manual to
help clarify and document the process of locale creation, and there is
an open bug for something similar:
https://sourceware.org/bugzilla/show_bug.cgi?id=18408
I hope that answers your question.
Cheers,
Carlos.