From d9fdb51df6dc5c9023bcf63996c48162c3770017 Mon Sep 17 00:00:00 2001 From: Raymond Hettinger Date: Tue, 6 Aug 2002 22:36:26 +0000 Subject: [PATCH] Document handling of raw-unicode-escapes. Closes SF bug 587087. --- Doc/ref/ref2.tex | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/Doc/ref/ref2.tex b/Doc/ref/ref2.tex index 56d5bb71cbf..e761c8d5ecc 100644 --- a/Doc/ref/ref2.tex +++ b/Doc/ref/ref2.tex @@ -457,6 +457,14 @@ escape the following quote character). Note also that a single backslash followed by a newline is interpreted as those two characters as part of the string, \emph{not} as a line continuation. +When an `r' or `R' prefix is used in conjunction with a `u' or `U' +prefix, then the \uXXXX escape sequence is processed while \emph{all other +backslashes are left in the string}. For example, the string literal +\code{ur"\u0062\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 +remain in the string. As a result, \uXXXX escape sequences are +only recognized when there are an odd number of backslashes. \subsection{String literal concatenation\label{string-catenation}}