[Python-checkins] CVS: python/dist/src/Doc/lib libmailcap.tex,1.13,1.14
Fred L. Drake
fdrake@users.sourceforge.net
Tue, 07 Aug 2001 22:39:31 -0700
Update of /cvsroot/python/python/dist/src/Doc/lib
In directory usw-pr-cvs1:/tmp/cvs-serv30393/lib
Modified Files:
libmailcap.tex
Log Message:
Clean up some of the markup here -- be more consistent in the use of
semantic labels instead of presentational markup.
Index: libmailcap.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libmailcap.tex,v
retrieving revision 1.13
retrieving revision 1.14
diff -C2 -d -r1.13 -r1.14
*** libmailcap.tex 1998/08/10 19:41:57 1.13
--- libmailcap.tex 2001/08/08 05:39:29 1.14
***************
*** 26,30 ****
Return a 2-tuple; the first element is a string containing the command
line to be executed
! (which can be passed to \code{os.system()}), and the second element is
the mailcap entry for a given MIME type. If no matching MIME
type can be found, \code{(None, None)} is returned.
--- 26,30 ----
Return a 2-tuple; the first element is a string containing the command
line to be executed
! (which can be passed to \function{os.system()}), and the second element is
the mailcap entry for a given MIME type. If no matching MIME
type can be found, \code{(None, None)} is returned.
***************
*** 45,50 ****
\var{plist} can be a list containing named parameters; the default
value is simply an empty list. Each entry in the list must be a
! string containing the parameter name, an equals sign (\code{=}), and the
! parameter's value. Mailcap entries can contain
named parameters like \code{\%\{foo\}}, which will be replaced by the
value of the parameter named 'foo'. For example, if the command line
--- 45,50 ----
\var{plist} can be a list containing named parameters; the default
value is simply an empty list. Each entry in the list must be a
! string containing the parameter name, an equals sign (\character{=}),
! and the parameter's value. Mailcap entries can contain
named parameters like \code{\%\{foo\}}, which will be replaced by the
value of the parameter named 'foo'. For example, if the command line
***************
*** 52,67 ****
was in a mailcap file, and \var{plist} was set to \code{['id=1',
'number=2', 'total=3']}, the resulting command line would be
! \code{"showpartial 1 2 3"}.
! In a mailcap file, the "test" field can optionally be specified to
! test some external condition (e.g., the machine architecture, or the
window system in use) to determine whether or not the mailcap line
! applies. \code{findmatch()} will automatically check such conditions
! and skip the entry if the check fails.
\end{funcdesc}
\begin{funcdesc}{getcaps}{}
Returns a dictionary mapping MIME types to a list of mailcap file
! entries. This dictionary must be passed to the \code{findmatch()}
function. An entry is stored as a list of dictionaries, but it
shouldn't be necessary to know the details of this representation.
--- 52,67 ----
was in a mailcap file, and \var{plist} was set to \code{['id=1',
'number=2', 'total=3']}, the resulting command line would be
! \code{'showpartial 1 2 3'}.
! In a mailcap file, the ``test'' field can optionally be specified to
! test some external condition (such as the machine architecture, or the
window system in use) to determine whether or not the mailcap line
! applies. \function{findmatch()} will automatically check such
! conditions and skip the entry if the check fails.
\end{funcdesc}
\begin{funcdesc}{getcaps}{}
Returns a dictionary mapping MIME types to a list of mailcap file
! entries. This dictionary must be passed to the \function{findmatch()}
function. An entry is stored as a list of dictionaries, but it
shouldn't be necessary to know the details of this representation.