Email List: Xaustin-group-lX
[All Lists]

Re: multibyte C locale

To: shwaresyst@xxxxxxx
Subject: Re: multibyte C locale
From: Glen Seeds <Glen.Seeds@xxxxxxxxxx>
Date: Fri, 30 Oct 2009 15:38:14 -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>

I believe that would make a lot of working applications non-conformant. Could we say:

   In the POSIX locale, a character from the portable character set

    must not have a state-dependent encoding. For characters that have
    state-dependent encoding, the encoding of each part must be distinct
    from the coding of all portable characters.

  /glen


From: shwaresyst@aol.com
To: austin-group-l@opengroup.org
Date: 2009-10-30 02:57 PM
Subject: Re: multibyte C locale





Yes, that's more the type of fix I was intending to say, but it was 1AM
when I was composing it. I do think the further qualification of 'and
all code points shall fit in a variable of C type char.' is needed to
explicitly pin it down that wide char types are also excluded.

Mark
-----Original Message-----
From: Vincent Lefevre <vincent-opgr@vinc17.org>
To: austin-group-l@opengroup.org
Sent: Fri, Oct 30, 2009 2:11 pm
Subject: Re: multibyte C locale

8< --------------------------------------------

I wonder whether the text should be changed to be more rigorous and
say exactly what it intends to say. Something like:

   In the POSIX locale, a character must not have a state-dependent
   encoding.

--
Vincent Lefèvre <vincent@vinc17.net> - Web: <
http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <
http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)








<Prev in Thread] Current Thread [Next in Thread>