On Aug 2 09:56, Corinna Vinschen via Cygwin wrote: > 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 :)
Never mind, had a bit of time. I fixed the uchar.h header and implemented c8rtomb und mbrtoc8. Still needs testing. Does anybody know of an easily accessible testsuite testing these functions? However, I did not define __STDC_VERSION_UCHAR_H__ yet. I wasn't sure my uchar.h is compliant, and Glibc doesn't define that macro yet, either. 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
