aboutsummaryrefslogtreecommitdiff
path: root/spec.txt
diff options
context:
space:
mode:
authorJohn MacFarlane <jgm@berkeley.edu>2015-03-09 21:07:55 -0700
committerJohn MacFarlane <jgm@berkeley.edu>2015-03-09 21:07:55 -0700
commit4ab59a258b5d76abddd8ed66a119270223dca5a3 (patch)
tree37cb1fd0426c942a1da8576c198b35d5d7fc140f /spec.txt
parentf0b15b806279f6b9a3f4bfffc35f3ca49d2cf3ac (diff)
Replaced some references to UTF-8 that should be to unicode.
The spec does not mandate UTF-8.
Diffstat (limited to 'spec.txt')
-rw-r--r--spec.txt9
1 files changed, 5 insertions, 4 deletions
diff --git a/spec.txt b/spec.txt
index 2ebbd11..f1d1b17 100644
--- a/spec.txt
+++ b/spec.txt
@@ -4276,7 +4276,7 @@ corresponding codepoints.
[Decimal entities](@decimal-entities)
consist of `&#` + a string of 1--8 arabic digits + `;`. Again, these
entities need to be recognised and tranformed into their corresponding
-UTF8 codepoints. Invalid Unicode codepoints will be written as the
+unicode codepoints. Invalid unicode codepoints will be written as the
"unknown codepoint" character (`0xFFFD`)
.
@@ -4287,7 +4287,8 @@ UTF8 codepoints. Invalid Unicode codepoints will be written as the
[Hexadecimal entities](@hexadecimal-entities)
consist of `&#` + either `X` or `x` + a string of 1-8 hexadecimal digits
-+ `;`. They will also be parsed and turned into their corresponding UTF8 values in the AST.
++ `;`. They will also be parsed and turned into the corresponding
+unicode codepoints in the AST.
.
&#X22; &#XD06; &#xcab;
@@ -5839,8 +5840,8 @@ in Markdown:
URL-escaping should be left alone inside the destination, as all
URL-escaped characters are also valid URL characters. HTML entities in
-the destination will be parsed into their UTF-8 codepoints, as usual, and
-optionally URL-escaped when written as HTML.
+the destination will be parsed into the corresponding unicode
+codepoints, as usual, and optionally URL-escaped when written as HTML.
.
[link](foo%20b&auml;)