summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorH. Peter Anvin <hpa@zytor.com>2008-06-01 23:00:23 -0700
committerH. Peter Anvin <hpa@zytor.com>2008-06-01 23:00:23 -0700
commite8a092976eefc0a29071d52f671c43aec90160cb (patch)
tree1be334b607b22eb9a5d469d3f8c86488ca9bc356
parent677befc4614e75eb6f8c35c29254d3eebb3d149d (diff)
downloadnasm-e8a092976eefc0a29071d52f671c43aec90160cb.tar.gz
Document UTF-8 conversion better, use "byte" instead of "ASCII"
ASCII specifically refers to characters <= 127, so to use "ASCII" for literal bytes is really confusing in a multibyte environment. Give an example of using Unicode escapes.
-rw-r--r--doc/nasmdoc.src13
1 files changed, 9 insertions, 4 deletions
diff --git a/doc/nasmdoc.src b/doc/nasmdoc.src
index 07a60053..81de0693 100644
--- a/doc/nasmdoc.src
+++ b/doc/nasmdoc.src
@@ -1482,16 +1482,21 @@ The following escape sequences are recognized by backquoted strings:
\c \f FF (ASCII 12)
\c \r CR (ASCII 13)
\c \e ESC (ASCII 27)
-\c \377 Up to 3 octal digits - ASCII literal
-\c \xFF Up to 2 hexadecimal digits - ASCII literal
+\c \377 Up to 3 octal digits - literal byte
+\c \xFF Up to 2 hexadecimal digits - literal byte
\c \u1234 4 hexadecimal digits - Unicode character
\c \U12345678 8 hexadecimal digits - Unicode character
All other escape sequences are reserved. Note that \c{\\0}, meaning a
-\c{NUL} character, is a special case of the octal escape sequence.
+\c{NUL} character (ASCII 0), is a special case of the octal escape
+sequence.
Unicode characters specified with \c{\\u} or \c{\\U} are converted to
-UTF-8.
+UTF-8. For example, the following lines are all equivalent:
+
+\c db `\u263a` ; UTF-8 smiley face
+\c db `\xe2\x98\xba` ; UTF-8 smiley face
+\c db 0E2h, 098h, 0BAh ; UTF-8 smiley face
\S{strconst} String Constants