@@ -94,7 +94,7 @@ \section{Standard Module \sectcode{xmllib}}
9494
9595\begin {funcdesc }{handle_charref}{ref}
9696This method is called to process a character reference of the form
97- `` \code {\&\# \var {ref};}'' . \var {ref} can either be a decimal number,
97+ \samp {\&\# \var {ref};}. \var {ref} can either be a decimal number,
9898or a hexadecimal number when preceded by \code {x}.
9999In the base implementation, \var {ref} must be a number in the
100100range 0-255. It translates the character to \ASCII {} and calls the
@@ -107,7 +107,7 @@ \section{Standard Module \sectcode{xmllib}}
107107
108108\begin {funcdesc }{handle_entityref}{ref}
109109This method is called to process a general entity reference of the form
110- `` \code {\& \var {ref};}'' where \var {ref} is an general entity
110+ \samp {\& \var {ref};} where \var {ref} is an general entity
111111reference. It looks for \var {ref} in the instance (or class)
112112variable \code {entitydefs} which should be a mapping from entity names
113113to corresponding translations.
@@ -121,17 +121,17 @@ \section{Standard Module \sectcode{xmllib}}
121121\begin {funcdesc }{handle_comment}{comment}
122122This method is called when a comment is encountered. The
123123\code {comment} argument is a string containing the text between the
124- `` \code {<!--}'' and `` \code {-->}'' delimiters, but not the delimiters
125- themselves. For example, the comment `` \code {<!--text-->}'' will
124+ \samp {<!--} and \samp {-->} delimiters, but not the delimiters
125+ themselves. For example, the comment \samp {<!--text-->} will
126126cause this method to be called with the argument \code {'text'}. The
127127default method does nothing.
128128\end {funcdesc }
129129
130130\begin {funcdesc }{handle_cdata}{data}
131131This method is called when a CDATA element is encountered. The
132132\code {data} argument is a string containing the text between the
133- `` \code {<![CDATA[}'' and `` \code {]]>}'' delimiters, but not the delimiters
134- themselves. For example, the entity `` \code {<![CDATA[text]]>}'' will
133+ \samp {<![CDATA[} and \samp {]]>} delimiters, but not the delimiters
134+ themselves. For example, the entity \samp {<![CDATA[text]]>} will
135135cause this method to be called with the argument \code {'text'}. The
136136default method does nothing.
137137\end {funcdesc }
@@ -141,7 +141,7 @@ \section{Standard Module \sectcode{xmllib}}
141141\code {name} is the PI target, and the \code {data} argument is a
142142string containing the text between the PI target and the closing delimiter,
143143but not the delimiter itself. For example, the instruction
144- `` \code {<?XML text?>}'' will cause this method to be called with the
144+ \samp {<?XML text?>} will cause this method to be called with the
145145arguments \code {'XML'} and \code {'text'}. The default method does
146146nothing. Note that if a document starts with a \code {<?xml ...?>}
147147tag, \code {handle_xml} is called to handle it.
@@ -150,8 +150,8 @@ \section{Standard Module \sectcode{xmllib}}
150150\begin {funcdesc }{handle_special}{data}
151151This method is called when a declaration is encountered. The
152152\code {data} argument is a string containing the text between the
153- `` \code {<!}'' and `` \code {>}'' delimiters, but not the delimiters
154- themselves. For example, the entity `` \code {<!ENTITY text>}'' will
153+ \samp {<!} and \samp {>} delimiters, but not the delimiters
154+ themselves. For example, the entity \samp {<!ENTITY text>} will
155155cause this method to be called with the argument \code {'ENTITY text'}. The
156156default method does nothing. Note that \code {<!DOCTYPE ...>} is
157157handled separately if it is located at the start of the document.
@@ -196,26 +196,26 @@ \section{Standard Module \sectcode{xmllib}}
196196case dependent; the \var {tag} occurring in method names must be in the
197197correct case:
198198
199- \begin {funcdesc }{start_\var {tag}}{attributes}
199+ \begin {funcdescni }{start_\var {tag}}{attributes}
200200This method is called to process an opening tag \var {tag}. The
201201\var {attributes} argument has the same meaning as described for
202202\code {handle_starttag()} above. In fact, the base implementation of
203- \code {handle_starttag} calls this method.
204- \end {funcdesc }
203+ \code {handle_starttag() } calls this method.
204+ \end {funcdescni }
205205
206- \begin {funcdesc }{end_\var {tag}}{}
206+ \begin {funcdescni }{end_\var {tag}}{}
207207This method is called to process a closing tag \var {tag}.
208- \end {funcdesc }
208+ \end {funcdescni }
209209
210- \begin {datadesc }{\var {tag}_attributes}
210+ \begin {datadescni }{\var {tag}_attributes}
211211If a class or instance variable \code {\var {tag}_attributes} exists, it
212212should be a list or a dictionary. If a list, the elements of the list
213213are the valid attributes for the element \var {tag}; if a dictionary,
214214the keys are the valid attributes for the element \var {tag}, and the
215215values the default values of the attributes, or \code {None} if there
216216is no default.
217217In addition to the attributes that were present in the tag, the
218- attribute dictionary that is passed to \code {handle_starttag} and
219- \code {unknown_starttag} contains values for all attributes that have a
218+ attribute dictionary that is passed to \code {handle_starttag() } and
219+ \code {unknown_starttag() } contains values for all attributes that have a
220220default value.
221- \end {datadesc }
221+ \end {datadescni }
0 commit comments