This is the mail archive of the
mailing list for the glibc project.
Re: libc locale spec?
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Chris Leonard <cjlhomeaddress at gmail dot com>
- Cc: libc-alpha <libc-alpha at sourceware dot org>
- Date: Mon, 12 Aug 2013 15:30:34 -0400
- Subject: Re: libc locale spec?
- References: <CAHdAatZGCHVkRCyb7UP0WcLU_hNmuzW8GzKzpquOprgf3Wj2oQ at mail dot gmail dot com>
On 08/10/2013 03:31 PM, Chris Leonard wrote:
> Is there a current, complete and definitive specification of the
> fields that are required (and/or optional) in a glibc locale file?
There is no such document, but if you want to create a wiki page
for it I would be ecstatic. That is to say that we would call the
wiki document canonical (or perhaps decide we want a `docs' directory
in git like the kernel has and put all of our canonical design
> I ask because I see a number of fields that are collected
> inconsistently across existing locales, such as
> These appear deprecated , but they are still present in many
> locales, should they be removed from those locales?
Wouldn't it impact compatibility to remove them?
They are still used by programs and I think we should support
them completely and fill out the information correctly. That
is orthogonal from the point of view of deprecation of the entries
which will happen at some point in the future based on some plan
to phase them out.