- From: Ian Hickson <ian@hixie.ch>
- Date: Sun, 1 Feb 2009 07:41:47 +0000 (UTC)
On Sun, 28 Dec 2008, Geoffrey Sneddon wrote: > > Step 3 is (currently) "If encoding is UTF-16, then change it to UTF-8.". > Does this mean we literally change just "encoding" to UTF-16, and leave > "url" verbatim, or are we meant to change "url" to UTF-8 too? This is > currently ambiguous. Not changing "url" will cause issues later in a > UTF-16 document. I don't understand what it would mean for "url" to change to UTF-16. "url" is a sequence of characters at this point, it has no encoding. > Step 12 replaces \ with /. IIRC WebKit does this for all URLs, not just > those with a "server-based naming authority" (what's that anyway?). My testing suggests it doesn't: data:,/ See the URI specs for details. > Also, earlier in the "Resolving URLs" section, there should probably be > a ref. to XMLBASE. Ok. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Saturday, 31 January 2009 23:41:47 UTC