Re: lib/57064: Import OpenBSD's script to autogen Unicode ctype definition?

To: Joerg Sonnenberger <joerg%bec.de@localhost>, gnats-bugs%netbsd.org@localhost
Subject: Re: lib/57064: Import OpenBSD's script to autogen Unicode ctype definition?
From: Rin Okuyama <rokuyama.rk%gmail.com@localhost>
Date: Fri, 21 Oct 2022 14:52:53 +0900

On 2022/10/19 3:15, Joerg Sonnenberger wrote:

Also note that switch to OpenBSD's ctype definition of UTF-8 does
*not* completely resolve our problems related to UTF-8. Our Citrus
locale does not recognize combining characters (incl. variation
selectors). Such characters may confuse applications.


That's not really surprising. Combining characters don't fit the classic
model of ISO C very well. They confuse a lot of software that makes poor
assumptions like every glyph corresponds 1:1 with a unicode code point
etc. But that's beyond the scope.


Well. Actually, recent versions of macOS and glibc also cannot
handle combining characters...

Thanks,
rin

References:
- lib/57064: Import OpenBSD's script to autogen Unicode ctype definition?
  - From: rokuyama . rk
- Re: lib/57064: Import OpenBSD's script to autogen Unicode ctype definition?
  - From: Joerg Sonnenberger

Prev by Date: Re: kern/57067 (QEMU arm and aarch64 panics on -current in vioif or hangs if vioif is disabled)
Next by Date: Re: lib/57064: Import OpenBSD's script to autogen Unicode ctype definition?
Previous by Thread: Re: lib/57064: Import OpenBSD's script to autogen Unicode ctype definition?
Next by Thread: Re: lib/57064: Import OpenBSD's script to autogen Unicode ctype definition?
Indexes:

Home | Main Index | Thread Index | Old Index