From f7aa164d7a84da3d2814abb8383c309603537c54 Mon Sep 17 00:00:00 2001 From: Fred Drake Date: Wed, 7 Aug 2002 13:24:09 +0000 Subject: Fix up some more markup problems. --- Doc/ref/ref2.tex | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) (limited to 'Doc') diff --git a/Doc/ref/ref2.tex b/Doc/ref/ref2.tex index e761c8d5ec..54706f33d8 100644 --- a/Doc/ref/ref2.tex +++ b/Doc/ref/ref2.tex @@ -457,14 +457,15 @@ 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. +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 \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 remain in the +string. As a result, \code{\e uXXXX} escape sequences are only +recognized when there are an odd number of backslashes. \subsection{String literal concatenation\label{string-catenation}} -- cgit v1.2.1