summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGeorg Brandl <georg@python.org>2005-11-22 19:23:58 (GMT)
committerGeorg Brandl <georg@python.org>2005-11-22 19:23:58 (GMT)
commitf96f5f5bbec6de78183b87da431672b8f850d73f (patch)
treeea418593072b0e9c1ffea6fa6937dcd1bd2ffa6f
parent4a5a91838b7318cc89a2ff2018b26940a5960a29 (diff)
downloadcpython-f96f5f5bbec6de78183b87da431672b8f850d73f.zip
cpython-f96f5f5bbec6de78183b87da431672b8f850d73f.tar.gz
cpython-f96f5f5bbec6de78183b87da431672b8f850d73f.tar.bz2
Bug #1359053: Doc: \Uxxxxxxxx escapes _are_ interpreted in raw unicode strings
-rw-r--r--Doc/ref/ref2.tex5
1 files changed, 3 insertions, 2 deletions
diff --git a/Doc/ref/ref2.tex b/Doc/ref/ref2.tex
index 950a732..af79e4d 100644
--- a/Doc/ref/ref2.tex
+++ b/Doc/ref/ref2.tex
@@ -514,8 +514,9 @@ as part of the string, \emph{not} as a line continuation.
When an \character{r} or \character{R} prefix is used in conjunction
with a \character{u} or \character{U} prefix, then the \code{\e uXXXX}
-escape sequence is processed while \emph{all other backslashes are
-left in the string}. For example, the string literal
+and \code{\e UXXXXXXXX} escape sequences are processed while
+\emph{all other backslashes are left in the string}.
+For example, the string literal
\code{ur"\e{}u0062\e n"} consists of three Unicode characters: `LATIN
SMALL LETTER B', `REVERSE SOLIDUS', and `LATIN SMALL LETTER N'.
Backslashes can be escaped with a preceding backslash; however, both