summaryrefslogtreecommitdiffstats
path: root/Doc/lib/emailmimebase.tex
diff options
context:
space:
mode:
authorBarry Warsaw <barry@python.org>2002-10-01 04:33:16 (GMT)
committerBarry Warsaw <barry@python.org>2002-10-01 04:33:16 (GMT)
commit5db478fa29299416f8475445f2584b20d8e534ed (patch)
treef01a56123be3884f6466ba3898bcf965771b2e87 /Doc/lib/emailmimebase.tex
parentcc3a6df506db57d614225b3657b4e97efc078970 (diff)
downloadcpython-5db478fa29299416f8475445f2584b20d8e534ed.zip
cpython-5db478fa29299416f8475445f2584b20d8e534ed.tar.gz
cpython-5db478fa29299416f8475445f2584b20d8e534ed.tar.bz2
Proofread and spell checked, all except the Examples section (which
I'll do next).
Diffstat (limited to 'Doc/lib/emailmimebase.tex')
-rw-r--r--Doc/lib/emailmimebase.tex16
1 files changed, 8 insertions, 8 deletions
diff --git a/Doc/lib/emailmimebase.tex b/Doc/lib/emailmimebase.tex
index 97c3eda..6bbd5dd 100644
--- a/Doc/lib/emailmimebase.tex
+++ b/Doc/lib/emailmimebase.tex
@@ -1,10 +1,10 @@
Ordinarily, you get a message object structure by passing a file or
-some text to a parser, which parses the text and returns the root of
-the message object structure. However you can also build a complete
-object structure from scratch, or even individual \class{Message}
-objects by hand. In fact, you can also take an existing structure and
-add new \class{Message} objects, move them around, etc. This makes a
-very convenient interface for slicing-and-dicing MIME messages.
+some text to a parser, which parses the text and returns the root
+message object. However you can also build a complete message
+structure from scratch, or even individual \class{Message} objects by
+hand. In fact, you can also take an existing structure and add new
+\class{Message} objects, move them around, etc. This makes a very
+convenient interface for slicing-and-dicing MIME messages.
You can create a new object structure by creating \class{Message}
instances, adding attachments and all the appropriate headers manually.
@@ -99,7 +99,7 @@ callable takes one argument, which is the \class{MIMEAudio} instance.
It should use \method{get_payload()} and \method{set_payload()} to
change the payload to encoded form. It should also add any
\mailheader{Content-Transfer-Encoding} or other headers to the message
-object as necessary. The default encoding is \emph{Base64}. See the
+object as necessary. The default encoding is base64. See the
\refmodule{email.Encoders} module for a list of the built-in encoders.
\var{_params} are passed straight through to the base class constructor.
@@ -124,7 +124,7 @@ callable takes one argument, which is the \class{MIMEImage} instance.
It should use \method{get_payload()} and \method{set_payload()} to
change the payload to encoded form. It should also add any
\mailheader{Content-Transfer-Encoding} or other headers to the message
-object as necessary. The default encoding is \emph{Base64}. See the
+object as necessary. The default encoding is base64. See the
\refmodule{email.Encoders} module for a list of the built-in encoders.
\var{_params} are passed straight through to the \class{MIMEBase}