Re: u32_normalize UNINORM_NFKC on 0xD800

2011-05-27 Thread Simon Josefsson
Bruno Haible writes: > Simon Josefsson wrote: >> I'm calculating this IDNA2008 property >> >>toNFKC(toCaseFold(toNFKC(cp))) != cp >> >> for all code points. > > It makes no sense to consider non-character code points here. Citing again > the Unicode standard, chapter 3 [1], section 3.8: > >

Re: u32_normalize UNINORM_NFKC on 0xD800

2011-05-27 Thread Bruno Haible
Simon Josefsson wrote: > I'm calculating this IDNA2008 property > >toNFKC(toCaseFold(toNFKC(cp))) != cp > > for all code points. It makes no sense to consider non-character code points here. Citing again the Unicode standard, chapter 3 [1], section 3.8: "High-surrogate and low-surrogate c

Re: u32_normalize UNINORM_NFKC on 0xD800

2011-05-27 Thread Simon Josefsson
FWIW, I came up with a better approach to handle this, and have asked for confirmation of the interpretation on the IDNABIS list. So I think u32_normalize is fine, as you explained. http://www.alvestrand.no/pipermail/idna-update/2011-May/007099.html /Simon

Re: u32_normalize UNINORM_NFKC on 0xD800

2011-05-27 Thread Simon Josefsson
Bruno Haible writes: > Simon Josefsson wrote: >> I'm doing some Unicode NFKC operations and noticing that u32_normalize >> fails for U+D800. > > This is a valid behaviour, because U+D800 is a "surrogate" point code > and therefore not a valid character code point. > > See the Unicode standard, ch

freebsd: abort usage in rpl_strerror_r

2011-05-27 Thread Matthias Bolte
Since e67e250d98e9dc0177a564f2cbfa99330902fe9e rpl_strerror_r contains an abort call in a section of code that is compiled on FreeBSD. But gcc complains about this strerror_r.c: In function 'rpl_strerror_r': strerror_r.c:503: warning: implicit declaration of function 'abort' strerror_r.c:503: warn