X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C11E23858288 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1690837980; bh=DXitY7mFHg2N5UG0/ygQrIS1d6vAW+WsnE0tHzM5vT0=; 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=Nh1xTkx3E1h+HaXvVPgEl4n+jBGIpvWqEPod9Rp0wX13NVB4EA2WeBdNfsm3nPcPI 53f0Wn1QR0rjCg9ZqMl8ibS3TmW89yIs0ow+ZcGI4J7riZoBnsQMbDqj1Tb/JDZDkt DQVk/QEggt9IUQa7KuYmfpV9uTQK/2odY/rVW75I= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4307A3858D28 Date: Mon, 31 Jul 2023 23:12:24 +0200 To: Bruno Haible Subject: Re: character class "alpha" Message-ID: Mail-Followup-To: Bruno Haible , cygwin AT cygwin DOT com References: <3884636 DOT 3uDm00564X AT nimes> <4474610 DOT kIfH5X4irW AT nimes> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <4474610.kIfH5X4irW@nimes> X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Corinna Vinschen via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Corinna Vinschen , cygwin AT cygwin DOT com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" 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. Thanks for your input and help! 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