Roger Leigh dixit: >From my reading of the standards a UTF-8 C locale would be required >to behave identically to the existing ASCII C locale: > >• will consider all byte sequences valid
I think it wouldn’t (since UTF-8 mbrtowc/wcrtomb don’t work this way, and it can’t be done with “just” the POSIX API anyway because they aren’t allowed to not read any input byte when outputting (in MirBSD, I’ve added a sister func- tion to mbrtowc which can do that), so not everything can be accepted in all situations. bye, //mirabilos -- “Having a smoking section in a restaurant is like having a peeing section in a swimming pool.” -- Edward Burr -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pine.bsm.4.64l.1101092219210.17...@herc.mirbsd.org