This is the mail archive of the
libc-locales@sourceware.org
mailing list for the GNU libc locales project.
Re: locale encodings
- From: Steven Abner <pheonix at zoomtown dot com>
- To: libc-locales at sourceware dot org
- Cc: Carlos O'Donell <carlos at redhat dot com>, Keld Simonsen <keld at keldix dot com>, Steven Abner <pheonix at zoomtown dot com>
- Date: Tue, 12 Nov 2013 10:37:05 -0500
- Subject: Re: locale encodings
- Authentication-results: sourceware.org; auth=none
- Authentication-results: smtp02.cincibell.synacor.com smtp dot mail=pheonix at zoomtown dot com; spf=unknown; sender-id=unknown
- Authentication-results: smtp02.cincibell.synacor.com header dot from=pheonix at zoomtown dot com; sender-id=unknown
- Authentication-results: smtp02.cincibell.synacor.com smtp dot user=pheonix at zoomtown dot com; auth=pass (LOGIN)
- References: <31AACAB8-A716-47CC-B755-F33DD77BA51E at zoomtown dot com> <1384174607 dot 4028 dot 8 dot camel at uno11 dot loco> <20131112012257 dot GA31828 at rap dot rap dot dk> <5281BEB1 dot 2010909 at redhat dot com> <20131112133642 dot GA22738 at rap dot rap dot dk> <98244D14-49A6-4953-8F6B-9D393E435324 at zoomtown dot com>
- X_cmae_category: 0,0 Undefined,Undefined
On 12 Nov 2013, at 9:34 AM, Steven Abner wrote:
> all data that is important, save one, is in POSIX's 7-bit ASCII
I wish to add, the quoted strings however are UTF8 instead of the default set. Off the top of my
head, the JP file has quoted ("") strings for correct display of months, hours, etc. in UTF8.
As far as embedded, a Japanese microwave doesn't need UTF8 for display, but the designer
who butchers the code for the microwave, even a Japanese one, can readily use UTF8 to set up
JIS0201 or even their own proprietary 128 or less byte display code, and internal communications.
That same designer could use UTF8, and default character information from glibc locales to
create an embedded version of a code set for microwaves in China.
Not saying this is standard, but my point was, I guess, is default character set for the locale could
or should go into the ASCII section of "LC" data. Comments in any encoding get gobbled, quoted
strings either in default character set or UTF8.
I am no expert, just food for thought.
Steve