X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org A94233858423
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1690963021;
	bh=1XDVD/DgDodlFHoPxE5KrbAVKQuhbuZOoTsnIzbzjfs=;
	h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	From;
	b=Q0V7ztzGgtsuSgCVRXjJnGSriqobwuUixXUYsgpx2L7Iaf85yIjC8kt+ghkcDMLs/
	cFMea6+dJ3tys7Je9hSK4fE7Sx+YYc6tC5/1f8aTdpKTMnkUW56KBExjoX1WVRQR5Y
	nHsB0oksE8w+YeY2KLwx5CZes+qdb8MnGQIKk210=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 6A2BB3858CDA
Date:	Wed, 2 Aug 2023 09:56:26 +0200
To:	cygwin AT cygwin DOT com
Subject:	Re: character class "alpha"
Message-ID:	<ZMoMKj9DHrf1LDnc@calimero.vinschen.de>
Mail-Followup-To:	cygwin AT cygwin DOT com, Brian Inglis <Brian DOT Inglis AT shaw DOT ca>,
	Bruno Haible <bruno AT clisp DOT org>
References:	<3884636 DOT 3uDm00564X AT nimes> <ZMfzbOOJth8Mk+rJ AT calimero DOT vinschen DOT de>
	<ZMf7aqxU8awRQM4v AT calimero DOT vinschen DOT de> <4474610 DOT kIfH5X4irW AT nimes>
	<ZMgjuHZjuKbnGpR6 AT calimero DOT vinschen DOT de>
	<078cd0e8-0db9-cb3c-e1e4-227b2f55a4ae AT Shaw DOT ca>
MIME-Version:	1.0
In-Reply-To:	<078cd0e8-0db9-cb3c-e1e4-227b2f55a4ae@Shaw.ca>
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Corinna Vinschen via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	cygwin AT cygwin DOT com
Cc:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>,
	Brian Inglis <Brian DOT Inglis AT shaw DOT ca>, Bruno Haible <bruno AT clisp DOT org>
Errors-To:	cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

On Aug  1 10:29, Brian Inglis via Cygwin wrote:
> On 2023-07-31 15:12, Corinna Vinschen via Cygwin wrote:
> > Hi Bruno,
> > 
> > On Jul 31 20:43, Bruno Haible via Cygwin wrote:
> > > Corinna Vinschen wrote:
> > > > there are more of those expressions which are disabled on glibc and
> > > > fail on Cygwin, for instance in test-c32iscntrl.c.  Maybe it's actually
> > > > the better idea to disable them on Cygwin, too, rather than to change
> > > > a working system...
> > > 
> > > Sure. There is no standard how to map the Unicode properties to POSIX
> > > character classes. Other than the mentioned ISO C constraints for
> > > 'digit' and 'xdigit' and a few POSIX constraints, you are free to
> > > map them as you like. For glibc and gnulib, I mapped them in a way
> > > that seemed to make most sense for applications. But different
> > > people might come to different meanings of "make sense".
> > 
> > Ok, so I just pushed a patchset to Cygwin git, which should make GB18030
> > support actually work.
> > 
> > Also, the C11 functions c16rtomb, c32rtomb, mbrtoc16, mbrtoc32 are now
> > implemented in Cygwin and a uchar.h header exists now, too.
> > 
> > Assuming all gnulib tests disabled for GLibc in
> > 
> >    test-c32isalpha.c
> >    test-c32iscntrl.c
> >    test-c32isprint.c
> >    test-c32isgraph.c
> >    test-c32ispunct.c
> >    test-c32islower.c
> > 
> > will be disabled for Cygwin as well, all gb18030 and c32 tests in gnulib
> > work as desired now.
> 
> 	https://www.iso.org/standard/86539.html		[ISO/IEC/IEEE 9945 CD]
> 
> Draft POSIX 2023 SUS V5 Issue 8 D3 CB2.1 proposes the following POSIX
> Subprofiling Option Group: POSIX_C_LANG_UCHAR: ISO C Unicode Utilities.
> 
> 	https://www.iso.org/standard/82075.html		[ISO/IEC 9899 DIS]
> 
> Draft Standard C 2023 is being voted on as of 2023-07-14, and if no
> technical issues arise requiring tweaks, will become the new standard, in
> which Unicode utilities <uchar.h> has some additions which you may wish to
> add; from:

Maybe at one point, but nobody keeps you from sending patches :)


Corinna

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -