From f158c946aa2e28529312e8730f561e85a5e0e4a1 Mon Sep 17 00:00:00 2001 From: John MacFarlane Date: Mon, 28 Dec 2015 21:10:50 -0800 Subject: Clarified that spec does not dictate URL encoding/normalization policy. --- spec.txt | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) (limited to 'spec.txt') diff --git a/spec.txt b/spec.txt index eadd2ab..57e649f 100644 --- a/spec.txt +++ b/spec.txt @@ -6633,9 +6633,13 @@ just a backslash: . URL-escaping should be left alone inside the destination, as all -URL-escaped characters are also valid URL characters. Character -references in the destination will be parsed into the corresponding Unicode -code points, as usual, and optionally URL-escaped when written as HTML. +URL-escaped characters are also valid URL characters. Entity and +numerical character references in the destination will be parsed +into the corresponding Unicode code points, as usual. These may +be optionally URL-escaped when written as HTML, but this spec +does not enforce any particular policy for rendering URLs in +HTML or other formats. Renderers may make different decisions +about how to escape or normalize URLs in the output. . [link](foo%20bä) -- cgit v1.2.3