From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <corinna@sourceware.org>
Received: by sourceware.org (Postfix, from userid 2155)
	id 6A2BB3858CDA; Wed,  2 Aug 2023 07:56:28 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6A2BB3858CDA
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1690962988;
	bh=uZ3xV2sPcgWrhmSRm6kvrmO7IPPFNhh3WPtuHKkvP+o=;
	h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To:From;
	b=njCsJtzGCbjW9WwGs2mNREQ+/uACg+e3BIfhOJTyaxHzXDLb8ktY60GDKSAnIQVwW
	 f6vY4RrrXhx9bkX8svHPwwcF+sje9JCWMks9QLuA/mjW0ElWcPI9JqiTZiBCse1+hy
	 fKyMp42KUp8dxuCUaqZX1oNCm58p+80FUAVDoY5M=
Received: by calimero.vinschen.de (Postfix, from userid 500)
	id 1D9B5A80C36; Wed,  2 Aug 2023 09:56:26 +0200 (CEST)
Date: Wed, 2 Aug 2023 09:56:26 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Cc: Brian Inglis <Brian.Inglis@shaw.ca>, Bruno Haible <bruno@clisp.org>
Subject: Re: character class "alpha"
Message-ID: <ZMoMKj9DHrf1LDnc@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com, Brian Inglis <Brian.Inglis@shaw.ca>,
	Bruno Haible <bruno@clisp.org>
References: <3884636.3uDm00564X@nimes>
 <ZMfzbOOJth8Mk+rJ@calimero.vinschen.de>
 <ZMf7aqxU8awRQM4v@calimero.vinschen.de>
 <4474610.kIfH5X4irW@nimes>
 <ZMgjuHZjuKbnGpR6@calimero.vinschen.de>
 <078cd0e8-0db9-cb3c-e1e4-227b2f55a4ae@Shaw.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <078cd0e8-0db9-cb3c-e1e4-227b2f55a4ae@Shaw.ca>
List-Id: <cygwin.cygwin.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