- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Thu, 30 Jan 2014 15:08:06 -0800
- To: Jungshik Shin (신정식, 申政湜) <jungshik@google.com>
- Cc: Gervase Markham <gerv@mozilla.org>, John C Klensin <klensin@jck.com>, yaojk <yaojk@cnnic.cn>, Paul Hoffman <paul.hoffman@vpnc.org>, "PUBLIC-IRI@W3.ORG" <public-iri@w3.org>, "uri@w3.org" <uri@w3.org>, IDNA update work <idna-update@alvestrand.no>, "www-tag.w3.org" <www-tag@w3.org>
On Thu, Jan 30, 2014 at 3:01 PM, Jungshik Shin (신정식, 申政湜) <jungshik@google.com> wrote: > ICU's IDNA 2003 implementation just does that. Before Chrome switched to UTS > 46 a few milestones ago, that's what's used by Chrome. > > And, Safari is likely to still use that (well, it depends on Mac OS X's > network API so that its behavior may differ on different OS X/iOS's). Earlier in this thread I provided a test case that shows Safari handles code points added after Unicode 3.2 just fine. Pretty sure the same was true for Chrome when I tested it. Hard to verify now. -- http://annevankesteren.nl/
Received on Thursday, 30 January 2014 23:08:34 UTC