Mirror
/
cpython
mirror of https://github.com/python/cpython
4
1
Fork 0
Code Issues Releases Wiki Activity

Use the new RFC macros wherever RFCs are referenced by number. No other 

changes.
This commit is contained in:
Fred Drake 1998-02-09 19:16:20 +00:00
parent b16166e56f
commit c58912426e
24 changed files with 56 additions and 58 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Doc/lib/libbase64.tex
View File

@ -2,12 +2,12 @@
\label{module-base64} \label{module-base64}
\stmodindex{base64} \stmodindex{base64}
\indexii{base-64}{encoding} \indexii{base-64}{encoding}
\index{RFC!1421} \rfcindex{1421}
\index{MIME!base 64 encoding} \index{MIME!base 64 encoding}
This module perform base-64 encoding and decoding of arbitrary binary This module perform base-64 encoding and decoding of arbitrary binary
strings into text strings that can be safely emailed or posted. The strings into text strings that can be safely emailed or posted. The
encoding scheme is defined in RFC 1421 and is used for MIME email and encoding scheme is defined in \rfc{1421} and is used for MIME email and
various other Internet-related applications; it is not the same as the various other Internet-related applications; it is not the same as the
output produced by the \file{uuencode} program. For example, the output produced by the \file{uuencode} program. For example, the
string \code{'www.python.org'} is encoded as the string string \code{'www.python.org'} is encoded as the string

5
Doc/lib/libftplib.tex
View File

@ -2,7 +2,7 @@
\label{module-ftplib} \label{module-ftplib}
\stmodindex{ftplib} \stmodindex{ftplib}
\indexii{FTP}{protocol} \indexii{FTP}{protocol}
\index{RFC!959} \rfcindex{959}
\renewcommand{\indexsubitem}{(in module ftplib)} \renewcommand{\indexsubitem}{(in module ftplib)}
@ -11,8 +11,7 @@ This module defines the class \code{FTP} and a few related items. The
can use this to write Python programs that perform a variety of can use this to write Python programs that perform a variety of
automated FTP jobs, such as mirroring other ftp servers. It is also automated FTP jobs, such as mirroring other ftp servers. It is also
used by the module \code{urllib} to handle URLs that use FTP. For used by the module \code{urllib} to handle URLs that use FTP. For
more information on FTP (File Transfer Protocol), see Internet RFC more information on FTP (File Transfer Protocol), see Internet \rfc{959}.
959.
Here's a sample session using the \code{ftplib} module: Here's a sample session using the \code{ftplib} module:

3
Doc/lib/libhtmllib.tex
View File

@ -1,6 +1,7 @@
\section{Standard Module \sectcode{htmllib}} \section{Standard Module \sectcode{htmllib}}
\label{module-htmllib} \label{module-htmllib}
\stmodindex{htmllib} \stmodindex{htmllib}
\rfcindex{1866}
\index{HTML} \index{HTML}
\index{hypertext} \index{hypertext}
@ -63,7 +64,7 @@ The module defines a single class:
\begin{funcdesc}{HTMLParser}{formatter} \begin{funcdesc}{HTMLParser}{formatter}
This is the basic HTML parser class. It supports all entity names This is the basic HTML parser class. It supports all entity names
required by the HTML 2.0 specification (RFC 1866). It also defines required by the HTML 2.0 specification (\rfc{1866}). It also defines
handlers for all HTML 2.0 and many HTML 3.0 and 3.2 elements. handlers for all HTML 2.0 and many HTML 3.0 and 3.2 elements.
\end{funcdesc} \end{funcdesc}

2
Doc/lib/libhttplib.tex
View File

@ -79,7 +79,7 @@ been made. It sends a line to the server consisting of the
\end{funcdesc} \end{funcdesc}
\begin{funcdesc}{putheader}{header\, argument\optional{\, ...}} \begin{funcdesc}{putheader}{header\, argument\optional{\, ...}}
Send an RFC-822 style header to the server. It sends a line to the Send an \rfc{822} style header to the server. It sends a line to the
server consisting of the header, a colon and a space, and the first server consisting of the header, a colon and a space, and the first
argument. If more arguments are given, continuation lines are sent, argument. If more arguments are given, continuation lines are sent,
each consisting of a tab and an argument. each consisting of a tab and an argument.

10
Doc/lib/libmailcap.tex
View File

@ -1,5 +1,6 @@
\section{Standard Module \sectcode{mailcap}} \section{Standard Module \sectcode{mailcap}}
\label{module-mailcap} \label{module-mailcap}
\rfcindex{1524}
\stmodindex{mailcap} \stmodindex{mailcap}
\renewcommand{\indexsubitem}{(in module mailcap)} \renewcommand{\indexsubitem}{(in module mailcap)}
@ -12,7 +13,7 @@ message or Web document with the MIME type video/mpeg, \code{\%s} will be
replaced by a filename (usually one belonging to a temporary file) and replaced by a filename (usually one belonging to a temporary file) and
the xmpeg program can be automatically started to view the file. the xmpeg program can be automatically started to view the file.
The mailcap format is documented in RFC 1524, ``A User Agent The mailcap format is documented in \rfc{1524}, ``A User Agent
Configuration Mechanism For Multimedia Mail Format Information'', but Configuration Mechanism For Multimedia Mail Format Information'', but
is not an Internet standard. However, mailcap files are supported on is not an Internet standard. However, mailcap files are supported on
most \UNIX{} systems. most \UNIX{} systems.
@ -24,12 +25,13 @@ line to be executed
the mailcap entry for a given MIME type. If no matching MIME the mailcap entry for a given MIME type. If no matching MIME
type can be found, \code{(None, None)} is returned. type can be found, \code{(None, None)} is returned.
\var{key} is the name of the field desired, which represents the type of \var{key} is the name of the field desired, which represents the type
activity to be performed; the default value is 'view', since in the of activity to be performed; the default value is 'view', since in the
most common case you simply want to view the body of the MIME-typed most common case you simply want to view the body of the MIME-typed
data. Other possible values might be 'compose' and 'edit', if you data. Other possible values might be 'compose' and 'edit', if you
wanted to create a new body of the given MIME type or alter the wanted to create a new body of the given MIME type or alter the
existing body data. See RFC1524 for a complete list of these fields. existing body data. See \rfc{1524} for a complete list of these
fields.
\var{filename} is the filename to be substituted for \%s in the \var{filename} is the filename to be substituted for \%s in the
command line; the default value is command line; the default value is

3
Doc/lib/libmd5.tex
View File

@ -1,9 +1,10 @@
\section{Built-in Module \sectcode{md5}} \section{Built-in Module \sectcode{md5}}
\label{module-md5} \label{module-md5}
\rfcindex{1321}
\bimodindex{md5} \bimodindex{md5}
This module implements the interface to RSA's MD5 message digest This module implements the interface to RSA's MD5 message digest
algorithm (see also Internet RFC 1321). Its use is quite algorithm (see also Internet \rfc{1321}). Its use is quite
straightforward:\ use the \code{md5.new()} to create an md5 object. straightforward:\ use the \code{md5.new()} to create an md5 object.
You can now feed this object with arbitrary strings using the You can now feed this object with arbitrary strings using the
\code{update()} method, and at any point you can ask it for the \code{update()} method, and at any point you can ask it for the

4
Doc/lib/libnntplib.tex
View File

@ -2,14 +2,14 @@
\label{module-nntplib} \label{module-nntplib}
\stmodindex{nntplib} \stmodindex{nntplib}
\indexii{NNTP}{protocol} \indexii{NNTP}{protocol}
\index{RFC!977} \rfcindex{977}
\renewcommand{\indexsubitem}{(in module nntplib)} \renewcommand{\indexsubitem}{(in module nntplib)}
This module defines the class \code{NNTP} which implements the client This module defines the class \code{NNTP} which implements the client
side of the NNTP protocol. It can be used to implement a news reader side of the NNTP protocol. It can be used to implement a news reader
or poster, or automated news processors. For more information on NNTP or poster, or automated news processors. For more information on NNTP
(Network News Transfer Protocol), see Internet RFC 977. (Network News Transfer Protocol), see Internet \rfc{977}.
Here are two small examples of how it can be used. To list some Here are two small examples of how it can be used. To list some
statistics about a newsgroup and print the subjects of the last 10 statistics about a newsgroup and print the subjects of the last 10

3
Doc/lib/libquopri.tex
View File

@ -3,13 +3,12 @@
\stmodindex{quopri} \stmodindex{quopri}
This module performs quoted-printable transport encoding and decoding, This module performs quoted-printable transport encoding and decoding,
as defined in RFC 1521: ``MIME (Multipurpose Internet Mail Extensions) as defined in \rfc{1521}: ``MIME (Multipurpose Internet Mail Extensions)
Part One''. The quoted-printable encoding is designed for data where Part One''. The quoted-printable encoding is designed for data where
there are relatively few nonprintable characters; the base-64 encoding there are relatively few nonprintable characters; the base-64 encoding
scheme available via the \code{base64} module is more compact if there scheme available via the \code{base64} module is more compact if there
are many such characters, as when sending a graphics file. are many such characters, as when sending a graphics file.
\indexii{quoted printable}{encoding} \indexii{quoted printable}{encoding}
\indexii{RFC}{1521}
\index{MIME!quoted-printable encoding} \index{MIME!quoted-printable encoding}
\renewcommand{\indexsubitem}{(in module quopri)} \renewcommand{\indexsubitem}{(in module quopri)}

9
Doc/lib/librfc822.tex
View File

@ -6,9 +6,8 @@
This module defines a class, \code{Message}, which represents a This module defines a class, \code{Message}, which represents a
collection of ``email headers'' as defined by the Internet standard collection of ``email headers'' as defined by the Internet standard
RFC 822. It is used in various contexts, usually to read such headers \rfc{822}. It is used in various contexts, usually to read such
from a file. headers from a file.
\index{RFC!822}
Note that there's a separate module to read \UNIX{}, MH, and MMDF Note that there's a separate module to read \UNIX{}, MH, and MMDF
style mailbox files: \code{mailbox}. style mailbox files: \code{mailbox}.
@ -30,10 +29,10 @@ e.g. \code{m['From']}, \code{m['from']} and \code{m['FROM']} all yield
the same result. the same result.
\begin{funcdesc}{parsedate}{date} \begin{funcdesc}{parsedate}{date}
Attempts to parse a date according to the rules in RFC822. however, Attempts to parse a date according to the rules in \rfc{822}. however,
some mailers don't follow that format as specified, so some mailers don't follow that format as specified, so
\code{parsedate()} tries to guess correctly in such cases. \code{parsedate()} tries to guess correctly in such cases.
\var{date} is a string containing an RFC822 date, such as \var{date} is a string containing an \rfc{822} date, such as
\code{"Mon, 20 Nov 1995 19:12:08 -0500"}. If it succeeds in parsing \code{"Mon, 20 Nov 1995 19:12:08 -0500"}. If it succeeds in parsing
the date, \code{parsedate()} returns a 9-tuple that can be passed the date, \code{parsedate()} returns a 9-tuple that can be passed
directly to \code{time.mktime()}; otherwise \code{None} will be directly to \code{time.mktime()}; otherwise \code{None} will be

5
Doc/lib/liburlparse.tex
View File

@ -16,9 +16,8 @@ URL'' to an absolute URL given a ``base URL''.
The module has been designed to match the Internet RFC on Relative The module has been designed to match the Internet RFC on Relative
Uniform Resource Locators (and discovered a bug in an earlier Uniform Resource Locators (and discovered a bug in an earlier
draft!). Refer to RFC 1808\index{RFC!1808} for details on relative draft!). Refer to \rfc{1808} for details on relative
URLs and RFC 1738\index{RFC!1738} for information on basic URL URLs and \rfc{1738} for information on basic URL syntax.
syntax.
It defines the following functions: It defines the following functions:

6
Doc/lib/libwww.tex
View File

@ -49,7 +49,7 @@ location, path, parameters, query string, fragment identifier).
--- Generic output formatter and device interface. --- Generic output formatter and device interface.
\item[rfc822] \item[rfc822]
--- Parse RFC-822 style mail headers. --- Parse \rfc{822} style mail headers.
\item[mimetools] \item[mimetools]
--- Tools for parsing MIME style message bodies. --- Tools for parsing MIME style message bodies.
@ -65,11 +65,11 @@ location, path, parameters, query string, fragment identifier).
representation representation
\item[xdrlib] \item[xdrlib]
--- The External Data Representation Standard as described in RFC 1014, --- The External Data Representation Standard as described in \rfc{1014},
written by Sun Microsystems, Inc. June 1987. written by Sun Microsystems, Inc. June 1987.
\item[mailcap] \item[mailcap]
--- Mailcap file handling. See RFC 1524. --- Mailcap file handling. See \rfc{1524}.
\item[base64] \item[base64]
--- Encode/decode binary files using the MIME base64 encoding. --- Encode/decode binary files using the MIME base64 encoding.

3
Doc/lib/libxdrlib.tex
View File

@ -3,13 +3,12 @@
\stmodindex{xdrlib} \stmodindex{xdrlib}
\index{XDR} \index{XDR}
\index{External Data Representation} \index{External Data Representation}
\index{RFC!1014}
\renewcommand{\indexsubitem}{(in module xdrlib)} \renewcommand{\indexsubitem}{(in module xdrlib)}
The \code{xdrlib} module supports the External Data Representation The \code{xdrlib} module supports the External Data Representation
Standard as described in RFC 1014, written by Sun Microsystems, Standard as described in \rfc{1014}, written by Sun Microsystems,
Inc. June 1987. It supports most of the data types described in the Inc. June 1987. It supports most of the data types described in the
RFC. RFC.

4
Doc/libbase64.tex
View File

@ -2,12 +2,12 @@
\label{module-base64} \label{module-base64}
\stmodindex{base64} \stmodindex{base64}
\indexii{base-64}{encoding} \indexii{base-64}{encoding}
\index{RFC!1421} \rfcindex{1421}
\index{MIME!base 64 encoding} \index{MIME!base 64 encoding}
This module perform base-64 encoding and decoding of arbitrary binary This module perform base-64 encoding and decoding of arbitrary binary
strings into text strings that can be safely emailed or posted. The strings into text strings that can be safely emailed or posted. The
encoding scheme is defined in RFC 1421 and is used for MIME email and encoding scheme is defined in \rfc{1421} and is used for MIME email and
various other Internet-related applications; it is not the same as the various other Internet-related applications; it is not the same as the
output produced by the \file{uuencode} program. For example, the output produced by the \file{uuencode} program. For example, the
string \code{'www.python.org'} is encoded as the string string \code{'www.python.org'} is encoded as the string

5
Doc/libftplib.tex
View File

@ -2,7 +2,7 @@
\label{module-ftplib} \label{module-ftplib}
\stmodindex{ftplib} \stmodindex{ftplib}
\indexii{FTP}{protocol} \indexii{FTP}{protocol}
\index{RFC!959} \rfcindex{959}
\renewcommand{\indexsubitem}{(in module ftplib)} \renewcommand{\indexsubitem}{(in module ftplib)}
@ -11,8 +11,7 @@ This module defines the class \code{FTP} and a few related items. The
can use this to write Python programs that perform a variety of can use this to write Python programs that perform a variety of
automated FTP jobs, such as mirroring other ftp servers. It is also automated FTP jobs, such as mirroring other ftp servers. It is also
used by the module \code{urllib} to handle URLs that use FTP. For used by the module \code{urllib} to handle URLs that use FTP. For
more information on FTP (File Transfer Protocol), see Internet RFC more information on FTP (File Transfer Protocol), see Internet \rfc{959}.
959.
Here's a sample session using the \code{ftplib} module: Here's a sample session using the \code{ftplib} module:

3
Doc/libhtmllib.tex
View File

@ -1,6 +1,7 @@
\section{Standard Module \sectcode{htmllib}} \section{Standard Module \sectcode{htmllib}}
\label{module-htmllib} \label{module-htmllib}
\stmodindex{htmllib} \stmodindex{htmllib}
\rfcindex{1866}
\index{HTML} \index{HTML}
\index{hypertext} \index{hypertext}
@ -63,7 +64,7 @@ The module defines a single class:
\begin{funcdesc}{HTMLParser}{formatter} \begin{funcdesc}{HTMLParser}{formatter}
This is the basic HTML parser class. It supports all entity names This is the basic HTML parser class. It supports all entity names
required by the HTML 2.0 specification (RFC 1866). It also defines required by the HTML 2.0 specification (\rfc{1866}). It also defines
handlers for all HTML 2.0 and many HTML 3.0 and 3.2 elements. handlers for all HTML 2.0 and many HTML 3.0 and 3.2 elements.
\end{funcdesc} \end{funcdesc}

2
Doc/libhttplib.tex
View File

@ -79,7 +79,7 @@ been made. It sends a line to the server consisting of the
\end{funcdesc} \end{funcdesc}
\begin{funcdesc}{putheader}{header\, argument\optional{\, ...}} \begin{funcdesc}{putheader}{header\, argument\optional{\, ...}}
Send an RFC-822 style header to the server. It sends a line to the Send an \rfc{822} style header to the server. It sends a line to the
server consisting of the header, a colon and a space, and the first server consisting of the header, a colon and a space, and the first
argument. If more arguments are given, continuation lines are sent, argument. If more arguments are given, continuation lines are sent,
each consisting of a tab and an argument. each consisting of a tab and an argument.

10
Doc/libmailcap.tex
View File

@ -1,5 +1,6 @@
\section{Standard Module \sectcode{mailcap}} \section{Standard Module \sectcode{mailcap}}
\label{module-mailcap} \label{module-mailcap}
\rfcindex{1524}
\stmodindex{mailcap} \stmodindex{mailcap}
\renewcommand{\indexsubitem}{(in module mailcap)} \renewcommand{\indexsubitem}{(in module mailcap)}
@ -12,7 +13,7 @@ message or Web document with the MIME type video/mpeg, \code{\%s} will be
replaced by a filename (usually one belonging to a temporary file) and replaced by a filename (usually one belonging to a temporary file) and
the xmpeg program can be automatically started to view the file. the xmpeg program can be automatically started to view the file.
The mailcap format is documented in RFC 1524, ``A User Agent The mailcap format is documented in \rfc{1524}, ``A User Agent
Configuration Mechanism For Multimedia Mail Format Information'', but Configuration Mechanism For Multimedia Mail Format Information'', but
is not an Internet standard. However, mailcap files are supported on is not an Internet standard. However, mailcap files are supported on
most \UNIX{} systems. most \UNIX{} systems.
@ -24,12 +25,13 @@ line to be executed
the mailcap entry for a given MIME type. If no matching MIME the mailcap entry for a given MIME type. If no matching MIME
type can be found, \code{(None, None)} is returned. type can be found, \code{(None, None)} is returned.
\var{key} is the name of the field desired, which represents the type of \var{key} is the name of the field desired, which represents the type
activity to be performed; the default value is 'view', since in the of activity to be performed; the default value is 'view', since in the
most common case you simply want to view the body of the MIME-typed most common case you simply want to view the body of the MIME-typed
data. Other possible values might be 'compose' and 'edit', if you data. Other possible values might be 'compose' and 'edit', if you
wanted to create a new body of the given MIME type or alter the wanted to create a new body of the given MIME type or alter the
existing body data. See RFC1524 for a complete list of these fields. existing body data. See \rfc{1524} for a complete list of these
fields.
\var{filename} is the filename to be substituted for \%s in the \var{filename} is the filename to be substituted for \%s in the
command line; the default value is command line; the default value is

3
Doc/libmd5.tex
View File

@ -1,9 +1,10 @@
\section{Built-in Module \sectcode{md5}} \section{Built-in Module \sectcode{md5}}
\label{module-md5} \label{module-md5}
\rfcindex{1321}
\bimodindex{md5} \bimodindex{md5}
This module implements the interface to RSA's MD5 message digest This module implements the interface to RSA's MD5 message digest
algorithm (see also Internet RFC 1321). Its use is quite algorithm (see also Internet \rfc{1321}). Its use is quite
straightforward:\ use the \code{md5.new()} to create an md5 object. straightforward:\ use the \code{md5.new()} to create an md5 object.
You can now feed this object with arbitrary strings using the You can now feed this object with arbitrary strings using the
\code{update()} method, and at any point you can ask it for the \code{update()} method, and at any point you can ask it for the

4
Doc/libnntplib.tex
View File

@ -2,14 +2,14 @@
\label{module-nntplib} \label{module-nntplib}
\stmodindex{nntplib} \stmodindex{nntplib}
\indexii{NNTP}{protocol} \indexii{NNTP}{protocol}
\index{RFC!977} \rfcindex{977}
\renewcommand{\indexsubitem}{(in module nntplib)} \renewcommand{\indexsubitem}{(in module nntplib)}
This module defines the class \code{NNTP} which implements the client This module defines the class \code{NNTP} which implements the client
side of the NNTP protocol. It can be used to implement a news reader side of the NNTP protocol. It can be used to implement a news reader
or poster, or automated news processors. For more information on NNTP or poster, or automated news processors. For more information on NNTP
(Network News Transfer Protocol), see Internet RFC 977. (Network News Transfer Protocol), see Internet \rfc{977}.
Here are two small examples of how it can be used. To list some Here are two small examples of how it can be used. To list some
statistics about a newsgroup and print the subjects of the last 10 statistics about a newsgroup and print the subjects of the last 10

3
Doc/libquopri.tex
View File

@ -3,13 +3,12 @@
\stmodindex{quopri} \stmodindex{quopri}
This module performs quoted-printable transport encoding and decoding, This module performs quoted-printable transport encoding and decoding,
as defined in RFC 1521: ``MIME (Multipurpose Internet Mail Extensions) as defined in \rfc{1521}: ``MIME (Multipurpose Internet Mail Extensions)
Part One''. The quoted-printable encoding is designed for data where Part One''. The quoted-printable encoding is designed for data where
there are relatively few nonprintable characters; the base-64 encoding there are relatively few nonprintable characters; the base-64 encoding
scheme available via the \code{base64} module is more compact if there scheme available via the \code{base64} module is more compact if there
are many such characters, as when sending a graphics file. are many such characters, as when sending a graphics file.
\indexii{quoted printable}{encoding} \indexii{quoted printable}{encoding}
\indexii{RFC}{1521}
\index{MIME!quoted-printable encoding} \index{MIME!quoted-printable encoding}
\renewcommand{\indexsubitem}{(in module quopri)} \renewcommand{\indexsubitem}{(in module quopri)}

9
Doc/librfc822.tex
View File

@ -6,9 +6,8 @@
This module defines a class, \code{Message}, which represents a This module defines a class, \code{Message}, which represents a
collection of ``email headers'' as defined by the Internet standard collection of ``email headers'' as defined by the Internet standard
RFC 822. It is used in various contexts, usually to read such headers \rfc{822}. It is used in various contexts, usually to read such
from a file. headers from a file.
\index{RFC!822}
Note that there's a separate module to read \UNIX{}, MH, and MMDF Note that there's a separate module to read \UNIX{}, MH, and MMDF
style mailbox files: \code{mailbox}. style mailbox files: \code{mailbox}.
@ -30,10 +29,10 @@ e.g. \code{m['From']}, \code{m['from']} and \code{m['FROM']} all yield
the same result. the same result.
\begin{funcdesc}{parsedate}{date} \begin{funcdesc}{parsedate}{date}
Attempts to parse a date according to the rules in RFC822. however, Attempts to parse a date according to the rules in \rfc{822}. however,
some mailers don't follow that format as specified, so some mailers don't follow that format as specified, so
\code{parsedate()} tries to guess correctly in such cases. \code{parsedate()} tries to guess correctly in such cases.
\var{date} is a string containing an RFC822 date, such as \var{date} is a string containing an \rfc{822} date, such as
\code{"Mon, 20 Nov 1995 19:12:08 -0500"}. If it succeeds in parsing \code{"Mon, 20 Nov 1995 19:12:08 -0500"}. If it succeeds in parsing
the date, \code{parsedate()} returns a 9-tuple that can be passed the date, \code{parsedate()} returns a 9-tuple that can be passed
directly to \code{time.mktime()}; otherwise \code{None} will be directly to \code{time.mktime()}; otherwise \code{None} will be

5
Doc/liburlparse.tex
View File

@ -16,9 +16,8 @@ URL'' to an absolute URL given a ``base URL''.
The module has been designed to match the Internet RFC on Relative The module has been designed to match the Internet RFC on Relative
Uniform Resource Locators (and discovered a bug in an earlier Uniform Resource Locators (and discovered a bug in an earlier
draft!). Refer to RFC 1808\index{RFC!1808} for details on relative draft!). Refer to \rfc{1808} for details on relative
URLs and RFC 1738\index{RFC!1738} for information on basic URL URLs and \rfc{1738} for information on basic URL syntax.
syntax.
It defines the following functions: It defines the following functions:

6
Doc/libwww.tex
View File

@ -49,7 +49,7 @@ location, path, parameters, query string, fragment identifier).
--- Generic output formatter and device interface. --- Generic output formatter and device interface.
\item[rfc822] \item[rfc822]
--- Parse RFC-822 style mail headers. --- Parse \rfc{822} style mail headers.
\item[mimetools] \item[mimetools]
--- Tools for parsing MIME style message bodies. --- Tools for parsing MIME style message bodies.
@ -65,11 +65,11 @@ location, path, parameters, query string, fragment identifier).
representation representation
\item[xdrlib] \item[xdrlib]
--- The External Data Representation Standard as described in RFC 1014, --- The External Data Representation Standard as described in \rfc{1014},
written by Sun Microsystems, Inc. June 1987. written by Sun Microsystems, Inc. June 1987.
\item[mailcap] \item[mailcap]
--- Mailcap file handling. See RFC 1524. --- Mailcap file handling. See \rfc{1524}.
\item[base64] \item[base64]
--- Encode/decode binary files using the MIME base64 encoding. --- Encode/decode binary files using the MIME base64 encoding.

3
Doc/libxdrlib.tex
View File

@ -3,13 +3,12 @@
\stmodindex{xdrlib} \stmodindex{xdrlib}
\index{XDR} \index{XDR}
\index{External Data Representation} \index{External Data Representation}
\index{RFC!1014}
\renewcommand{\indexsubitem}{(in module xdrlib)} \renewcommand{\indexsubitem}{(in module xdrlib)}
The \code{xdrlib} module supports the External Data Representation The \code{xdrlib} module supports the External Data Representation
Standard as described in RFC 1014, written by Sun Microsystems, Standard as described in \rfc{1014}, written by Sun Microsystems,
Inc. June 1987. It supports most of the data types described in the Inc. June 1987. It supports most of the data types described in the
RFC. RFC.