On Wed, Jan 11, 2017 at 02:14:13AM -0800, Ngie Cooper (yaneurabeya) wrote:
> > On Aug 11, 2015, at 6:45 PM, Craig Rodrigues <rodr...@crodrigues.org> wrote:
> > On Tue, Aug 11, 2015 at 2:59 PM, Jilles Tjoelker <jil...@freebsd.org
> > <mailto:jil...@freebsd.org>> wrote:
> > Author: jilles
> > Date: Tue Aug 11 21:59:36 2015
> > New Revision: 286649
> > URL: https://svnweb.freebsd.org/changeset/base/286649
> > <https://svnweb.freebsd.org/changeset/base/286649>
> > Log:
> > Fix and re-enable UTF-8 tests.
> > Modified:
> > head/contrib/netbsd-tests/lib/libc/locale/t_mbrtowc.c
> > head/contrib/netbsd-tests/lib/libc/locale/t_mbstowcs.c
> > head/lib/libc/tests/locale/Makefile
> > Thanks for fixing this. What is the procedure that FreeBSD
> > developers need to follow to push this kind of change upstream to
> > NetBSD?
> I’m submitting PRs with NetBSD as needed. To be frank, I’m not
> sure that this change is needed upstream (I’m probably going to #ifdef
> the code — some things I found when trying to push things back).
I think the change is required upstream as well, since UTF-8 no longer
includes code points greater than 0x10ffff per RFC 3629 (this change
made the code point ranges of UTF-8 and UTF-16 the same). The sequences
that used to correspond to code points greater than 0x10ffff shall be
treated as invalid. See also SVN r286490, r286491, r287125.
I suppose I should have included this reasoning in the original commit
email@example.com mailing list
To unsubscribe, send any mail to "svn-src-head-unsubscr...@freebsd.org"