diff options
author | John MacFarlane <jgm@berkeley.edu> | 2014-10-24 20:09:53 -0700 |
---|---|---|
committer | John MacFarlane <jgm@berkeley.edu> | 2014-10-24 20:09:53 -0700 |
commit | c818df9888d452f0ae54b3a504eefdd970fd73d8 (patch) | |
tree | a863ec0a195bcf53259d2873d4f83146a47fe6d5 | |
parent | 48f0df56d24de06343bd6a52167f3f210c6c101d (diff) |
Spec: say explicitly that a character is a unicode code point.
-rw-r--r-- | spec.txt | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -192,10 +192,10 @@ In the examples, the `→` character is used to represent tabs. # Preprocessing A [line](#line) <a id="line"></a> -is a sequence of zero or more characters followed by a line -ending (CR, LF, or CRLF) or by the end of -file. +is a sequence of zero or more [characters](#character) followed by a +line ending (CR, LF, or CRLF) or by the end of file. +A [character](#character)<a id="character"></a> is a unicode code point. This spec does not specify an encoding; it thinks of lines as composed of characters rather than bytes. A conforming parser may be limited to a certain encoding. |