Fix up some more markup problems.

This commit is contained in:
Fred Drake 2002-08-07 13:24:09 +00:00
parent 95fa4ddf7b
commit f7aa164d7a
1 changed files with 9 additions and 8 deletions

View File

@ -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 backslash followed by a newline is interpreted as those two characters
as part of the string, \emph{not} as a line continuation. 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' When an \character{r} or \character{R} prefix is used in conjunction
prefix, then the \uXXXX escape sequence is processed while \emph{all other with a \character{u} or \character{U} prefix, then the \code{\e uXXXX}
backslashes are left in the string}. For example, the string literal escape sequence is processed while \emph{all other backslashes are
\code{ur"\u0062\n"} consists of three Unicode characters: left in the string}. For example, the string literal \code{ur"\e
`LATIN SMALL LETTER B', `REVERSE SOLIDUS', and `LATIN SMALL LETTER N'. u0062\e n"} consists of three Unicode characters: `LATIN SMALL LETTER
Backslashes can be escaped with a preceding backslash; however, both B', `REVERSE SOLIDUS', and `LATIN SMALL LETTER N'. Backslashes can be
remain in the string. As a result, \uXXXX escape sequences are escaped with a preceding backslash; however, both remain in the
only recognized when there are an odd number of backslashes. 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}} \subsection{String literal concatenation\label{string-catenation}}