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

Re: Unicode IDNA feedback

From: Anne van Kesteren <annevk@annevk.nl>
Date: Fri, 6 Jan 2017 10:07:12 +0100
Message-ID: <CADnb78jPGG5cU=Sizq4G3UjbuReHQDJ81w_jYC72joepPDys3A@mail.gmail.com>
To: Mark Davis ☕ <markdavis@google.com>
Cc: Sebastian Mayr <github@smayr.name>, www-archive <www-archive@w3.org>
On Mon, Nov 21, 2016 at 5:06 PM, Mark Davis ⚖ <markdavis@google.com> wrote:
> Traveling now so will be next week before I can look at this.

Hey Mark, belated happy holidays. Would you be able to look into this now?


> On Nov 21, 2016 01:39, "Anne van Kesteren" <annevk@annevk.nl> wrote:
>> Hi Mark,
>>
>> As you might recall we track IDNA issues that affect the URL Standard
>> through https://github.com/whatwg/url/issues/53. The last set of
>> feedback was recorded here http://www.unicode.org/review/pri317/ and
>> apparently closed without it being addressed. Could you perhaps shed
>> some light on that?
>>
>> Somewhat related, now both Firefox and Safari use
>> Nontransitional_Processing (i.e., IDNA2008), which for now is still
>> against the URL Standard as that requires Transitional_Processing, but
>> I think the time has come to change that.
>>
>> The commit message at https://trac.webkit.org/changeset/208902 is
>> pretty detailed on the specifics. It turns out that some of the
>> implemented processing steps are SHOULD-level requirements in UTS46. I
>> think these should be refactored to be options for the ToASCII and
>> ToUnicode algorithms, so the URL Standard can enforce them. It does
>> not seem great to allow variable processing.


-- 
https://annevankesteren.nl/
Received on Friday, 6 January 2017 09:07:43 UTC

This archive was generated by hypermail 2.3.1 : Friday, 6 January 2017 09:07:43 UTC