summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBarry Warsaw <barry@python.org>2002-10-10 15:23:38 (GMT)
committerBarry Warsaw <barry@python.org>2002-10-10 15:23:38 (GMT)
commitdf88b9fadfcaf849d9f8c5c42c6013fbe8978b9e (patch)
tree41f4e82329a4b2f20dcd4333842a6404d7549ca5
parent57ce1430b2b9774662c8a162ffb16c5fda90b06f (diff)
downloadcpython-df88b9fadfcaf849d9f8c5c42c6013fbe8978b9e.zip
cpython-df88b9fadfcaf849d9f8c5c42c6013fbe8978b9e.tar.gz
cpython-df88b9fadfcaf849d9f8c5c42c6013fbe8978b9e.tar.bz2
Document that the Charset constructor coerces its argument to lower
case.
-rw-r--r--Doc/lib/emailcharsets.tex9
1 files changed, 5 insertions, 4 deletions
diff --git a/Doc/lib/emailcharsets.tex b/Doc/lib/emailcharsets.tex
index d1ae728..d654ada 100644
--- a/Doc/lib/emailcharsets.tex
+++ b/Doc/lib/emailcharsets.tex
@@ -23,10 +23,11 @@ Certain character sets must be encoded with quoted-printable or base64
when used in email headers or bodies. Certain character sets must be
converted outright, and are not allowed in email.
-Optional \var{input_charset} is as described below. After being alias
-normalized it is also used as a lookup into the registry of character
-sets to find out the header encoding, body encoding, and output
-conversion codec to be used for the character set. For example, if
+Optional \var{input_charset} is as described below; it is always
+coerced to lower case. After being alias normalized it is also used
+as a lookup into the registry of character sets to find out the header
+encoding, body encoding, and output conversion codec to be used for
+the character set. For example, if
\var{input_charset} is \code{iso-8859-1}, then headers and bodies will
be encoded using quoted-printable and no output conversion codec is
necessary. If \var{input_charset} is \code{euc-jp}, then headers will