W3C home > Mailing lists > Public > www-archive@w3.org > January 2017

Re: Unicode IDNA feedback

From: Anne van Kesteren <annevk@annevk.nl>
Date: Sat, 7 Jan 2017 12:04:02 +0100
Message-ID: <CADnb78iDRGHtSbWqitT9HzYipg-Oco4nLMs8Bps9C-OB0wWQ9g@mail.gmail.com>
To: Mark Davis ☕️ <mark@macchiato.com>
Cc: Sebastian Mayr <github@smayr.name>, www-archive <www-archive@w3.org>, Markus Scherer <mscherer@google.com>, Jungshik Shin (신정식, 申政湜) <jungshik@google.com>, Michel SUIGNARD <Michel@suignard.com>, Alex Christensen <achristensen@apple.com>, Domenic Denicola <d@domenic.me>
On Sat, Jan 7, 2017 at 11:32 AM, Mark Davis ☕️ <mark@macchiato.com> wrote:
> So it isn't missing anything that you know of?

While working on ASCII-only tests for the host parser Domenic and I
discovered the issue with "-" yesterday that he reported in the
document.


> Also, if you could help find the "shoulds" that should be parameters, and
> have any suggestions for naming, that would be great.

It seems Bidi, ContextJ, and ContextO could all be options that you
either enable or disable. As Alex mentioned in
https://github.com/whatwg/url/issues/110 it seems that nobody enables
ContextO at this point, but the others are checked.

Unfortunately I haven't gotten around to testing the algorithms more
thoroughly yet, but I hope to get to that soon. Domenic and I have a
plan for a host parsing test framework that will help us test ToASCII.
We might be able to repurpose it to stress ToUnicode as well come to
think of it, since URL's origin getter uses that (but that's always
after ToASCII has already been applied, there's no way to use
ToUnicode directly in browsers).


-- 
https://annevankesteren.nl/
Received on Saturday, 7 January 2017 11:04:46 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 7 January 2017 11:04:47 UTC