summaryrefslogtreecommitdiffstats
path: root/Doc/ref/ref3.tex
diff options
context:
space:
mode:
authorGuido van Rossum <guido@python.org>1995-03-15 11:25:32 (GMT)
committerGuido van Rossum <guido@python.org>1995-03-15 11:25:32 (GMT)
commit47b4c0fb35a5c0092fc82ece96fcb1a79dd2285d (patch)
treed9fec38185adbf8f70fda937f85610cd453e6295 /Doc/ref/ref3.tex
parent9b623b3d6329425daa4cb389546eb23a32354b52 (diff)
downloadcpython-47b4c0fb35a5c0092fc82ece96fcb1a79dd2285d.zip
cpython-47b4c0fb35a5c0092fc82ece96fcb1a79dd2285d.tar.gz
cpython-47b4c0fb35a5c0092fc82ece96fcb1a79dd2285d.tar.bz2
replace ASCII by macro call
Diffstat (limited to 'Doc/ref/ref3.tex')
-rw-r--r--Doc/ref/ref3.tex8
1 files changed, 4 insertions, 4 deletions
diff --git a/Doc/ref/ref3.tex b/Doc/ref/ref3.tex
index 0904849..152b1bf 100644
--- a/Doc/ref/ref3.tex
+++ b/Doc/ref/ref3.tex
@@ -211,7 +211,7 @@ character type; a character is represented by a string of one element.
Characters represent (at least) 8-bit bytes. The built-in
functions \verb@chr()@ and \verb@ord()@ convert between characters
and nonnegative integers representing the byte values.
-Bytes with the values 0-127 represent the corresponding ASCII values.
+Bytes with the values 0-127 represent the corresponding \ASCII{} values.
The string data type is also used to represent arrays of bytes, e.g.
to hold data read from a file.
\obindex{string}
@@ -221,10 +221,10 @@ to hold data read from a file.
\bifuncindex{chr}
\bifuncindex{ord}
-(On systems whose native character set is not ASCII, strings may use
+(On systems whose native character set is not \ASCII{}, strings may use
EBCDIC in their internal representation, provided the functions
-\verb@chr()@ and \verb@ord()@ implement a mapping between ASCII and
-EBCDIC, and string comparison preserves the ASCII order.
+\verb@chr()@ and \verb@ord()@ implement a mapping between \ASCII{} and
+EBCDIC, and string comparison preserves the \ASCII{} order.
Or perhaps someone can propose a better rule?)
\index{ASCII}
\index{EBCDIC}