Re: multibyte C locale

[Glen Seeds <Glen.Seeds@xxxxxxxxxx>]

If I have this assurance, then I can
write a portable utilities that do things such as parse out components
of a pathname and do case-insensitive searches for portable file names.
I need the POSIX locale to do this. These utilities will still work as
intended in UTF-8, and will still be useful there. That seems like a lot
of value to me.
  /glen

From:	wollman+austin-group@xxxxxx
To:	Glen Seeds/Ottawa/IBM@IBMCA
Cc:	austin-group-l@xxxxxx
Date:	2009-10-30 06:03 PM
Subject:	Re: multibyte C locale

---

[formatting fixed]

<<On Fri, 30 Oct 2009 17:46:54 -0400, Glen Seeds <Glen.Seeds@xxxxxx>
said:

>> [I wrote:]
>> Turn it around: of what value is the POSIX locale without such
a
>> requirement?

> The value is considerable, if we can find a way to accommodate UTF-8.

I don't see it.  What's the use case?  I can see a value to
applications in being able to configure a locale that acts like
pre-locale Unix and C did; I don't see a value in configuring a locale
that doesn't behave like traditional Unix, but isn't usefully
localized either.  ("Traditional Unix" behavior is normally
what I
want pretty much all the time.)

-GAWollman