| To: | Glen Seeds <Glen.Seeds@xxxxxxxxxx> |
|---|---|
| Subject: | Re: multibyte C locale |
| From: | wollman+austin-group@xxxxxxxxxxx |
| Date: | Fri, 30 Oct 2009 18:03:38 -0400 |
| Cc: | austin-group-l@xxxxxxxxxxxxx |
| References: | <4AE83F49.1090805@byu.net><8CC273626A167C9-708C-A347@webmail-m008.sysops.aol.com><4AEAA953.7070605@jacaranda.org><20091030093610.GA31100@squonk.masqnet><20091030131925.GH28296@prunille.vinc17.org><20091030140706.GA12871@squonk.masqnet><20091030181139.GI28296@prunille.vinc17.org><8CC27A9B7A337AB-1BD0-9799@webmail-d053.sysops.aol.com><4AEB5378.5070402@byu.net><19179.21604.450124.747123@khavrinen.csail.mit.edu><OF7977394B.18C83951-ON8525765F.0077969C-8525765F.0077A6A5@ca.ibm.com> |
[formatting fixed]
<<On Fri, 30 Oct 2009 17:46:54 -0400, Glen Seeds <Glen.Seeds@ca.ibm.com> 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
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: multibyte C locale, wollman+austin-group |
|---|---|
| Next by Date: | Re: multibyte C locale, wollman+austin-group |
| Previous by Thread: | Re: multibyte C locale, wollman+austin-group |
| Next by Thread: | Re: multibyte C locale, wollman+austin-group |
| Indexes: | [Date] [Thread] [All Lists] |