From: Fred Drake <fdrake@acm.org>
Date: Thu, 11 Nov 2004 05:04:55 +0000 (+0000)
Subject: Replace last two uses of the "list" environment with "description"
X-Git-Tag: v2.4c1~38
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=758f5ea4194a2aa6d7d01c47d1558b45ec3f5fc2;p=thirdparty%2FPython%2Fcpython.git

Replace last two uses of the "list" environment with "description"
environments.

Closes SF bug #692442: Konqueror can't render docs because of
malformed HTML.  While the generated HTML is still terrible, the cited
cases of <DL COMPACT> have been removed.  The general problem of XHTML
conformance has not been solved, but is endemic to LaTeX2HTML output.
---

diff --git a/Doc/lib/libre.tex b/Doc/lib/libre.tex
index e6cbc5584712..3940dd198b1b 100644
--- a/Doc/lib/libre.tex
+++ b/Doc/lib/libre.tex
@@ -78,8 +78,8 @@ Special characters either stand for classes of ordinary characters, or
 affect how the regular expressions around them are interpreted.
 
 The special characters are:
-
-\begin{list}{}{\leftmargin 0.7in \labelwidth 0.65in}
+%
+\begin{description}
 
 \item[\character{.}] (Dot.)  In the default mode, this matches any
 character except a newline.  If the \constant{DOTALL} flag has been
@@ -306,14 +306,14 @@ pattern, which will match with \code{'<user@host.com>'} as well as
 \code{'user@host.com'}, but not with \code{'<user@host.com'}.
 \versionadded{2.4}
 
-\end{list}
+\end{description}
 
 The special sequences consist of \character{\e} and a character from the
 list below.  If the ordinary character is not on the list, then the
 resulting RE will match the second character.  For example,
 \regexp{\e\$} matches the character \character{\$}.
-
-\begin{list}{}{\leftmargin 0.7in \labelwidth 0.65in}
+%
+\begin{description}
 
 \item[\code{\e \var{number}}] Matches the contents of the group of the
 same number.  Groups are numbered starting from 1.  For example,
@@ -374,7 +374,7 @@ character properties database.
 
 \item[\code{\e Z}]Matches only at the end of the string.
 
-\end{list}
+\end{description}
 
 Most of the standard escapes supported by Python string literals are
 also accepted by the regular expression parser: