Clarified that spec does not dictate URL encoding/normalization policy.

1 files changed, 7 insertions, 3 deletions

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ä)