\input texinfo.tex
@setfilename tm-en.info
-@settitle{tm 7.90 Manual (English Version)}
+@settitle{tm 7.98 Manual (English Version)}
@titlepage
-@title tm 7.90 Manual (English Version)
+@title tm 7.98 Manual (English Version)
@author MORIOKA Tomohiko <morioka@@jaist.ac.jp>
-@subtitle 1996/10/15
+@subtitle 1996/12/24
@end titlepage
@node Top, Introduction, (dir), (dir)
-@top tm 7.90 Manual (English Version)
+@top tm 7.98 Manual (English Version)
@ifinfo
@chapter What is tm?
The tm package is a set of modules to enjoy MIME on GNU Emacs. Using
-tm, you can
+tm, you can@refill
@itemize @bullet
@item
@menu
-* What is MIME?::
-* How is MIME?::
* Glossary::
@end menu
-@node What is MIME?, How is MIME?, Introduction, Introduction
-@section What is MIME?
-
-@cindex{MIME}@strong{MIME} stands for @cindex{Multipurpose Internet Mail
-Extensions}@strong{Multipurpose Internet Mail Extensions}, it is a
-proposed internet standard for including content and headers other than
-(ASCII) plain text in messages.@refill
-
-Current MIME standard consists of RFC 1521 and RFC 1522. RFC 1521
-describes multipurpose content in message bodies, while RFC 1522
-describes multilingual characters in headers.
-
-
-@node How is MIME?, Glossary, What is MIME?, Introduction
-@section How is MIME?
-
-In multipurpose message side, MIME can represent various contents such
-as images, sounds, videos, ... as against traditional Internet mail/news
-message can represent only (us-ascii (@ref{us-ascii})) plain
-text.@refill
-
-Interestingly, MIME can send ``procedure'', such as ftp (@ref{FTP}), ftp
-mail, file extraction, applying patch, ...@refill
-
-# Of course, it has security problem.@refill
-
-These various kinds of contents are defined by media types written in
-@cindex{Content-Type}@strong{Content-Type} (@ref{Content-Type field})
-field. Namely MIME message has information about content in header. So
-if reader defines processes for each content-type (@ref{content-type}),
-he/she can display image, or play video or sound, or get file by ftp, or
-extract file, ... only read the message.@refill
-
-In addition, MIME message can represent message includes plural parts,
-called @cindex{Multipart}@strong{Multipart} (@ref{multipart}) message.
-So it is possible to include picture and sound in one message.@refill
-
-MIME seems have philosophy of ``declaration''. In other words, MIME is
-a message description language to represent various kinds of things uses
-us-ascii (@ref{us-ascii}) as its ``alphabet''. Encoded-word defined in
-RFC 1522 (@ref{encoded-word}) is same.@refill
-
-In addition, MUA displays only what it can understand and ignore what
-can not understand. So content is saved from non-supported MUA and
-MUA is saved from unknown data.
-
-
-@node Glossary, , How is MIME?, Introduction
+@node Glossary, , Introduction, Introduction
@section Glossary
@menu
* 7bit::
* 8bit::
-* 94 character set:: 94 \e$BJ8;z=89g\e(B
-* 96 character set:: 96 \e$BJ8;z=89g\e(B
-* 94x94 character set:: 94\e$B!_\e(B94 \e$BJ8;z=89g\e(B
+* 94-character set::
+* 96-character set::
+* 94x94-character set::
* ASCII::
* Base64::
* binary::
-* Character Set:: Character Set\e$B!JJ8;z=89g!K\e(B
* cn-gb:: cn-gb, gb2312
* cn-big5:: cn-big5, big5
-* CNS:: CNS 11643-1992
-* Coded character set:: Coded character set\e$B!JId9f2=J8;z=89g!K\e(B, Character code\e$B!JJ8;zId9f!K\e(B
-* Code extension:: Code extension\e$B!JId9f3HD%!K\e(B
+* CNS 11643:: CNS 11643-1992
+* coded character set:: Coded character set, Character code
+* code extension:: Code extension
* Content-Disposition:: Content-Disposition field
-* content-type::
* Content-Type field::
* Emacs::
* encoded-word::
* FTP:: FTP
* GB 2312:: GB 2312-1980
* GB 8565.2:: GB 8565.2-1988
+* graphic character set:: Graphic Character Set
* hz-gb2312::
* ISO 2022::
* iso-2022-cn::
* JIS X0212:: JIS X0212-1990
* koi8-r::
* KS C5601:: KS C5601-1987
+* media type::
* message::
* message/rfc822::
* method::
* RFC 934::
* RFC 1036::
* RFC 1153::
-* RFC 1521:: RFC 1521
* RFC 1557::
* RFC 1922::
+* RFC 2045::
+* RFC 2046::
+* RFC 2048::
+* RFC 2049::
* plain text::
* Security multipart::
* text/enriched::
@node 7bit, 8bit, Glossary, Glossary
@subsection 7bit
-\e$B$3$3$G$O\e(B 0 \e$B$+$i\e(B 127 \e$B$N@0?t$r;X$7$^$9!#\e(B@refill
+@cindex{7bit}@strong{7bit} means any integer between 0 .. 127.@refill
-0 \e$B$+$i\e(B 127 \e$B$N@0?t$NNs$GI=8=$G$-$k$h$&$J\e(B data \e$B$r\e(B ``7bit \e$B$N\e(B data'' \e$B$H8F$S\e(B
-\e$B$^$9!#\e(B@refill
+Any data represented by 7bit integers is called @cindex{7bit
+data}@strong{7bit data}.@refill
-\e$B$^$?!"\e(B0 \e$B$+$i\e(B 31 \e$B$*$h$S\e(B 127 \e$B$GI=8=$5$l$k@)8fJ8;z$H\e(B 32 \e$B$GI=8=$5$l$k6uGr$H\e(B
-33 \e$B$+$i\e(B 126 \e$B$GI=8=$5$l$k?^7AJ8;z$+$i$J$kJ8;zNs$N$3$H$r\e(B ``7bit \e$B$NJ8;zNs\e(B''
-\e$B$H8F$S$^$9!J$3$l$O\e(B ISO 2022 (@ref{ISO 2022}) \e$B$N!V\e(B7 \e$BC10L7O!W$HF1MM$G$9!K!#\e(B
+Textual string consisted of Control characters between 0 .. 31 and 127,
+and space represented by 32, and graphic characters between 33 .. 236
+are called @cindex{7bit (textual) string}@strong{7bit (textual)
+string}.@refill
-\e$BEAE}E*$J\e(B Internet \e$B$N\e(B MTA (@ref{MTA}) \e$B$O\e(B 7bit \e$B$N\e(B data \e$B$rE>Aw$G$-$k$N$G!"\e(B
-7bit \e$B$N\e(B data \e$B$O\e(B Quoted-Printable (@ref{Quoted-Printable}) \e$B$d\e(B Base64
-(@ref{Base64}) \e$B$H$$$C$?JQ49$r9T$o$J$/$F$b$=$N$^$^E>Aw$G$-$^$9!#\e(B@refill
+Traditional Internet MTA (@ref{MTA}) can translate 7bit data, so it is
+no need to translate by Quoted-Printable (@ref{Quoted-Printable}) or
+Base64 (@ref{Base64}) for 7bit data.@refill
-\e$B$7$+$7!"\e(B7bit \e$B$G$"$l$P$I$s$J\e(B data \e$B$G$bNI$$$H$O$$$($^$;$s!#$J$<$J$i!"#19T\e(B
-\e$B$ND9$5$,$"$^$j$KD9$$$H!"\e(BMTA \e$B$O$=$N\e(B message \e$B$rE>Aw$9$k$3$H$,$G$-$J$$$+$i\e(B
-\e$B$G$9!#$A$J$_$K!"\e(BRFC 821 (@ref{RFC 821}) \e$B$O#19T$O2~9TJ8;z$r=|$$$F\e(B 998
-byte \e$B0JFb$G$"$k$3$H$r5a$a$F$$$^$9!#$h$C$F!"$3$l0J>e$N9T$,4^$^$l$k2DG=@-\e(B
-\e$B$N$"$k\e(B data, \e$BNc$($P!"\e(BPostscript \e$B$N\e(B data \e$B$J$I$O\e(B Quoted-Printable \e$BEy$G\e(B
-encode\e$B$9$kI,MQ$,$"$j$^$9!#\e(B
+However if there are too long lines, it can not translate by 7bit MTA
+even if it is 7bit data. RFC 821 (@ref{RFC 821}) and RFC 2045 (@ref{RFC
+2045}) require lines in 7bit data must be less than 998 bytes. So if a
+``7bit data'' has a line more than 999 bytes, it is regarded as binary
+(@ref{binary}). For example, Postscript file should be encoded by
+Quoted-Printable.
-@node 8bit, 94 character set, 7bit, Glossary
+@node 8bit, 94-character set, 7bit, Glossary
@subsection 8bit
-\e$B$3$3$G$O\e(B 0 \e$B$+$i\e(B 255 \e$B$N@0?t$r;X$7$^$9!#\e(B@refill
-
-0 \e$B$+$i\e(B 255 \e$B$N@0?t$NNs$GI=8=$G$-$k$h$&$J\e(B data \e$B$r\e(B ``8bit \e$B$N\e(B data'' \e$B$H8F$S\e(B
-\e$B$^$9!#\e(B@refill
+@cindex{8bit}@strong{8bit} means any integer between 0 .. 255.@refill
-\e$B$^$?!"\e(B0 \e$B$+$i\e(B 31, 127 \e$B$*$h$S\e(B 128 \e$B$+$i\e(B 159 \e$B$GI=8=$5$l$k@)8fJ8;z$H\e(B 32 \e$B$GI=\e(B
-\e$B8=$5$l$k6uGr$H\e(B 33 \e$B$+$i\e(B 126 \e$B$H\e(B 160 \e$B$+$i\e(B 255 \e$B$GI=8=$5$l$k?^7AJ8;z$+$i$J$k\e(B
-\e$BJ8;zNs$N$3$H$r\e(B ``8bit \e$B$NJ8;zNs\e(B'' \e$B$H8F$S$^$9!J$3$l$O\e(B ISO 2022 (@ref{ISO
-2022}) \e$B$N!V\e(B8 \e$BC10L7O!W$HF1MM$G$9!K!#\e(B@refill
+Any data represented by 8bit integers is called @cindex{8bit
+data}@strong{8bit data}.@refill
-iso-8859-1 (@ref{iso-8859-1}) \e$B$d\e(B euc-kr (@ref{euc-kr}) \e$B$H$$$C$?Id9f2=J8\e(B
-\e$B;z=89g$O\e(B 8bit \e$B$NJ8;zNs$G$9!#\e(B@refill
+Textual string consisted of Control characters between 0 .. 31, 127, and
+128 .. 159, and space represented by 32, and graphic characters between
+33 .. 236 and 160 .. 255 are called @cindex{8bit (textual)
+string}@strong{8bit (textual) string}.@refill
-\e$BEAE}E*$J\e(B Internet \e$B$N\e(B MTA (@ref{MTA}) \e$B$O\e(B 7bit (@ref{7bit}) \e$B$N\e(B data \e$B$7$+E>\e(B
-\e$BAw$G$-$J$$$N$G!"$=$&$7$?\e(B MTA \e$B$r7PM3$9$k>l9g!"\e(BQuoted-Printable
-(@ref{Quoted-Printable}) \e$B$d\e(B Base64 (@ref{Base64}) \e$B$H$$$C$?JQ49$r9T$o$J$/\e(B
-\e$B$F$O$J$j$^$;$s!#\e(B@refill
+For example, iso-8859-1 (@ref{iso-8859-1}) or euc-kr (@ref{euc-kr}) are
+coded-character-set represented by 8bit textual string.@refill
-\e$B$7$+$7!":G6a$G$O\e(B 8bit \e$B$NJ8;zNs$r$=$N$^$^DL$9$3$H$,$G$-$k\e(B MTA \e$B$bEP>l$7$F\e(B
-\e$B$-$?$N$G!"$=$N$^$^Aw$k$3$H$,$G$-$k>l9g$bA}$($F$-$^$7$?!#\e(B@refill
+Traditional Internet MTA (@ref{MTA}) can translate only 7bit
+(@ref{7bit}) data, so if a 8bit data will be translated such MTA, it
+must be encoded by Quoted-Printable (@ref{Quoted-Printable}) or Base64
+(@ref{Base64}).@refill
-\e$B$7$+$7!"\e(B8bit \e$B$G$"$l$P$I$s$J\e(B data \e$B$G$bNI$$$H$O$$$($^$;$s!#$J$<$J$i!"#19T\e(B
-\e$B$ND9$5$,$"$^$j$KD9$$$H!"\e(BMTA \e$B$O$=$N\e(B message \e$B$rE>Aw$9$k$3$H$,$G$-$J$$$+$i\e(B
-\e$B$G$9!#$A$J$_$K!"\e(BRFC 821 \e$B$O#19T$O2~9TJ8;z$r=|$$$F\e(B 998 byte \e$B0JFb$G$"$k$3$H\e(B
-\e$B$r5a$a$F$$$^$9!#$h$C$F!"$3$l0J>e$N9T$,4^$^$l$k2DG=@-$N$"$k\e(B data, \e$BNc$($P!"\e(B
-Postscript \e$B$N\e(B data \e$B$J$I$O\e(B Quoted-Printable \e$BEy$G\e(B encode\e$B$9$kI,MQ$,$"$j$^$9!#\e(B
-@refill
+However 8bit MTA are increasing today.@refill
-\e$B$^$?!"$3$&$7$?M}M3$+$i!"#19T$,\e(B 999 byte \e$B0J>e$N9T$,B8:_$9$k2DG=@-$N$"$k\e(B
-data \e$B$O\e(B @cindex{binary}@strong{binary} (@ref{binary}) \e$B$H8F$V$3$H$K$7$^$9!#\e(B
+However if there are too long lines, it can not translate by 8bit MTA
+even if it is 8bit data. RFC 2045 (@ref{RFC 2045}) require lines in
+8bit data must be less than 998 bytes. So if a ``8bit data'' has a line
+more than 999 bytes, it is regarded as binary (@ref{binary}), so it must
+be encoded by Base64 or Quoted-Printable.
-\e$B$A$J$_$K!"\e(B7bit \e$B$GI=8=$G$-$k\e(B data \e$B$O\e(B 8bit \e$B$G$bI=8=$G$-$^$9!#$h$C$F!"\e(B
-``8bit'' \e$B$H8@$C$?>l9g!"#19T$,\e(B 998 byte \e$B0J2<$NG$0U$N\e(B data \e$B$r;X$9$3$H$,\e(B
-\e$B$"$j$^$9!#\e(B
+@node 94-character set, 96-character set, 8bit, Glossary
+@subsection 94-character set
-@node 94 character set, 96 character set, 8bit, Glossary
-@subsection 94 \e$BJ8;z=89g\e(B
+@cindex{94-character set}@strong{94-character set} is a kind of 1 byte
+graphic character set (@ref{graphic character set}), each characters are
+in positions 02/01 (33) to 07/14 (126) or 10/01 (161) to 15/14 (254).
+(ex. ASCII (@ref{ASCII}), JIS X0201-Latin)
-33 \e$B$+$i\e(B 126 \e$B$NHO0O$N\e(B 1 byte \e$B$+$i$J$k\e(B \e$BJ8;z=89g\e(B(@ref{Character set})\e$B!#\e(B
-ASCII (@ref{ASCII}) \e$B$d\e(B JIS X0201-Latin \e$B$O$=$N0l<o!#\e(B
+@node 96-character set, 94x94-character set, 94-character set, Glossary
+@subsection 96-character set
-@node 96 character set, 94x94 character set, 94 character set, Glossary
-@subsection 96 \e$BJ8;z=89g\e(B
+@cindex{96-character set}@strong{96-character set} is a kind of 1 byte
+graphic character set (@ref{graphic character set}), each characters are
+in positions 02/00 (32) to 07/15 (126) or 10/00 (160) to 15/15
+(255). (ex. ISO 8859)
-32 \e$B$+$i\e(B 127 \e$B$NHO0O$N\e(B 1 byte \e$B$+$i$J$k\e(B \e$BJ8;z=89g\e(B(@ref{Character set})\e$B!#\e(BISO
-8859 \e$B%7%j!<%:$O$=$N0l<o!#\e(B
+@node 94x94-character set, ASCII, 96-character set, Glossary
+@subsection 94x94-character set
-@node 94x94 character set, ASCII, 96 character set, Glossary
-@subsection 94\e$B!_\e(B94 \e$BJ8;z=89g\e(B
+@cindex{94x94-character set}@strong{94x94-character set} is a kind of 2
+byte graphic character set (@ref{graphic character set}), each bytes are
+in positions 02/01 (33) to 07/14 (126) or 10/01 (161) to 15/14 (254).
+(ex. JIS X0208 (@ref{JIS X0208}), GB 2312 (@ref{GB 2312}))
-33 \e$B$+$i\e(B 126 \e$B$NHO0O$N\e(B 2 byte \e$B$+$i$J$k\e(B \e$BJ8;z=89g\e(B(@ref{Character set})\e$B!#\e(BJIS
-X0208 (@ref{JIS X0208}) \e$B$d\e(B GB 2312 (@ref{GB 2312}) \e$B$O$=$N0l<o!#\e(B
-
-@node ASCII, Base64, 94x94 character set, Glossary
+@node ASCII, Base64, 94x94-character set, Glossary
@subsection ASCII
-\e$B%"%a%j%+O"K.$G;H$o$l$kJ8;z$rId9f2=$7$?\e(B 94 \e$BJ8;z=89g\e(B(@ref{94 character
-set})\e$B!#\e(BA-Z, a-z \e$B$N\e(B Latin \e$BJ8;z$H?t;z!"4v$D$+$N5-9f$+$i$J$k!#\e(BISO 646
-(@ref{ISO 646}) \e$B$N0l$D!#\e(B
+@cindex{ASCII}@strong{ASCII} is a 94-character set (@ref{94-character
+set}) contains primary latin characters (A-Z, a-z), numbers and some
+characters. It is a standard of the United States of America. It is a
+variant of ISO 646 (@ref{ISO 646}).
@cindex{ASCII}@cindex{ANSI X3.4:1986}
@noindent
@node Base64, binary, ASCII, Glossary
@subsection Base64
-RFC 1521 (@ref{RFC 1521}) \e$B$GDj5A$5$l$F$$$k\e(B MIME (@ref{MIME}) \e$B$K$*$1$k\e(B
-binary data (@ref{binary}) \e$B$N\e(B network \e$B$G$NJQ49K!$N#1$D!#\e(B@refill
+@cindex{Base64}@strong{Base64} is a transfer encoding method of MIME
+(@ref{MIME}) defined in RFC 2045 (@ref{RFC 2045}).@refill
-\e$B!X\e(B64 \e$B?J?t!Y$H$$$&0UL#$G!"\e(B3 byte \e$B$N\e(B data \e$B$r\e(B 0 \e$B$+$i\e(B 63 \e$B$N?t$rI=$9\e(B ASCII
-(@ref{ASCII}) 4 \e$BJ8;z$KJQ49$9$kJ}K!!#!J$b$7!"\e(B4 \e$BJ8;z$K$J$i$J$1$l$P\e(B
-@cindex{pad}@strong{pad} \e$B$H8F$P$l$k5M$aJ*$r$7$FD9$5$rD4@0$9$k!K\e(B@refill
+The encoding process represents 24-bit groups of input bits as output
+strings of 4 encoded characters. Encoded characters represent integer 0
+.. 63 or @cindex{pad}@strong{pad}. Base64 data must be 4 * n bytes, so
+pad is used to adjust size.@refill
-\e$B$3$N\e(B 65 \e$B<oN`$NJ8;z$O\e(B ASCII \e$B$H\e(B EBCDIC \e$B$N6&DLItJ,$+$iA*$P$l$F$*$j!"\e(B
-Internet \e$B0J30$N\e(B network \e$B$r7PM3$9$k>l9g$G$b0BA4$KE>Aw$G$-$k$h$&$K@_7W$5\e(B
-\e$B$l$F$$$k!#\e(B
+These 65 characters are subset of all versions of ISO 646, including
+US-ASCII, and all versions of EBCDIC. So it is safe even if it is
+translated by non-Internet gateways.
-@node binary, Character Set, Base64, Glossary
+@node binary, cn-gb, Base64, Glossary
@subsection binary
-\e$BG$0U$N\e(B byte \e$BNs$r\e(B @cindex{binary}@strong{binary} \e$B$H8F$V$3$H$K$7$^$9!#\e(B
-@refill
-
-8bit (@ref{8bit}) \e$B$H0[$J$k$N$O\e(B data \e$B$K9T$N9=B$$r2>Dj$7$J$$$3$H$G$9!#\e(B
-
-\e$B$^$?!"9T$N9=B$$,$"$C$F$b!"\e(B999 byte \e$B0J>e$+$i$J$k9T$,$"$k>l9g$b\e(B binary\e$B$H8F\e(B
-\e$B$V$3$H$K$7$^$9!#\e(B@refill
-
-\e$B$A$J$_$K!"\e(B7bit (@ref{7bit}) \e$B$d\e(B 8bit \e$B$GI=8=$G$-$k\e(B data \e$B$O\e(B binary \e$B$G$bI=8=\e(B
-\e$B$G$-$^$9!#$h$C$F!"\e(B@cindex{binary data}@strong{binary data} \e$B$H8@$C$?>l9g!"\e(B
-\e$BG$0U$N\e(B data \e$B$r;X$9$3$H$,$"$j$^$9!#\e(B
+Any byte stream is called @cindex{binary}@strong{binary}.@refill
+It does not require structureof lines. It differs from from 8bit
+(@ref{8bit}).@refill
-@node Character Set, cn-gb, binary, Glossary
-@subsection Character Set\e$B!JJ8;z=89g!K\e(B
+In addition, if line structured data contain too long line (more than
+998 bytes), it is regarded as binary.
-\e$BId9f2=J8;z=89g\e(B(@ref{Coded character set})\e$B!#C"$7!"$3$3$G$O\e(B \e$BId9f3HD%\e(B
-(@ref{Code extension}) \e$B$5$l$F$J$$J8;z=89g$H$$$&%K%e%"%s%9$r9~\e(B
-\e$B$a$F$$$k!#\e(B
-
-@node cn-gb, cn-big5, Character Set, Glossary
+@node cn-gb, cn-big5, binary, Glossary
@subsection cn-gb, gb2312
-\e$BCf9qBgN&$G$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N\e(B MIME
-charset (@ref{MIME charset}) \e$B$N#1$D!#\e(B@refill
+A MIME charset (@ref{MIME charset}) for simplified Chinese mainly used
+in the Chinese mainland.@refill
-ISO 2022 (@ref{ISO 2022}) \e$B$K4p$$$F\e(B ASCII (@ref{ASCII}) \e$B$K\e(B GB 2312
-(@ref{GB 2312}) \e$B$r\e(B 8bit (@ref{8bit}) \e$B$GId9f3HD%\e(B (@ref{Code extension})\e$B$7\e(B
-\e$B$F$$$k!#\e(B@refill
+It is a 8bit (@ref{8bit}) coded character set (@ref{coded character
+set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
+(@ref{ASCII}) to combine GB 2312 (@ref{GB 2312}).@refill
-RFC 1922 (@ref{RFC 1922}) \e$B$GDj5A$5$l$F$$$k!#\e(B
+It is defined in RFC 1922 (@ref{RFC 1922}).
-@node cn-big5, CNS, cn-gb, Glossary
+@node cn-big5, CNS 11643, cn-gb, Glossary
@subsection cn-big5, big5
-\e$BBfOQ$d9a9A$GMQ$$$i$l$F$$$k<g$KHKBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N\e(B
-MIME charset (@ref{MIME charset}) \e$B$N#1$D!#\e(B@refill
+A MIME charset (@ref{MIME charset}) for traditional Chinese mainly used
+in Taiwan and Hon Kong.@refill
+
+It is a 8bit (@ref{8bit}) coded character set (@ref{coded character
+set}) not based on ISO 2022 (@ref{ISO 2022}). It is a de-fact
+standard.@refill
-ISO 2022 (@ref{ISO 2022}) \e$B$K4p$+$J$$\e(B 8bit (@ref{8bit}) \e$B$NId9f2=J8;z=89g\e(B
-(@ref{Coded character set})\e$B$G\e(B de-fact standard \e$B$G$"$k!#\e(BRFC 1922
-(@ref{RFC 1922}) \e$B$GDj5A$5$l$F$$$k!#\e(B@refill
+It is defined in RFC 1922 (@ref{RFC 1922}).@refill
cf. @cindex{BIG5}
@noindent
Computer'', March 1984.
@end quotation
-CNS 11643-1986 (@ref{CNS}) \e$B$HBP1~4X78$,$"$k!#\e(B
+It corresponds to CNS 11643 (@ref{CNS 11643}).
-@node CNS, Coded character set, cn-big5, Glossary
+@node CNS 11643, coded character set, cn-big5, Glossary
@subsection CNS 11643-1992
-\e$BBfOQ$d9a9A$GMQ$$$i$l$F$$$k<g$KHKBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N\e(B
-\e$BJ8;z=89g\e(B(@ref{Character set})\e$B!#BfOQ$NI8=`!#8=:_!"\e(B94\e$B!_\e(B94 (@ref{94x94
-character set}) \e$B$NLL$,Bh#1LL$+$iBh#7LL$^$G$"$k!#\e(B@refill
+Graphic character set (@ref{Graphic character set})s for Chinese mainly
+written by traditional Chinese mainly used in Taiwan and Hong Kong. It
+is a standard of Taiwan. Currently there are seven 94x94 character set
+(@ref{94x94 character set}).@refill
+
+Final byte of ISO 2022 (@ref{ISO 2022}) are following:
+
+@table @samp
+@item plane 1
+04/07 (`G')
+
+@item plane 2
+04/08 (`H')
+
+@item plane 3
+04/09 (`I')
+
+@item plane 4
+04/10 (`J')
+
+@item plane 5
+04/11 (`K')
+
+@item plane 6
+04/12 (`L')
+
+@item plane 7
+04/13 (`M')
+
+@end table
-ISO 2022 (@ref{ISO 2022}) \e$B$G$N=*C<J8;z$O!"Bh#1LL$,\e(B `G', \e$BBh#2LL$,\e(B `H', \e$BBh\e(B
-\e$B#3LL$,\e(B `I', \e$BBh#4LL$,\e(B `J', \e$BBh#5LL$,\e(B `K', \e$BBh#6LL$,\e(B `L', \e$BBh#7LL$,\e(B `M' \e$B$G$"\e(B
-\e$B$k!#\e(B
@cindex{CNS 11643-1992}@cindex{CNS 11643:1992}
@noindent
-@node Coded character set, Code extension, CNS, Glossary
-@subsection Coded character set\e$B!JId9f2=J8;z=89g!K\e(B, Character code\e$B!JJ8;zId9f!K\e(B
+@node coded character set, code extension, CNS 11643, Glossary
+@subsection Coded character set, Character code
-\e$BJ8;z$H\e(B byte \e$BNs$H#1BP#1$KBP1~IU$1$k[#Kf$G$J$$5,B'$N=89g!#\e(B
+A set of unambiguous rules that establishes a character set and the
+one-to-one relationship between the characters of the set and their
+bit combinations.
-@node Code extension, Content-Disposition, Coded character set, Glossary
-@subsection Code extension\e$B!JId9f3HD%!K\e(B
+@node code extension, Content-Disposition, coded character set, Glossary
+@subsection Code extension
-\e$BM?$($i$l$?J8;z=89g\e(B(@ref{Character set})\e$B$K4^$^$l$F$$$J$$J8;z$NId9f2=$N$?\e(B
-\e$B$a$KMQ$$$k<jK!!#\e(BISO 2022 (@ref{ISO 2022}) \e$B$O$=$N#1$D!#\e(B
+The techniques for the encoding of characters that are not included in
+the character set of a given code. (ex. ISO 2022 (@ref{ISO 2022}))
-@node Content-Disposition, content-type, Code extension, Glossary
+@node Content-Disposition, Content-Type field, code extension, Glossary
@subsection Content-Disposition field
-Content \e$B$NI=<($N;EJ}$d\e(B file \e$BL>$rI=8=$9$k$?$a$N\e(B field. MIME (@ref{MIME})
-\e$B$N3HD%$N#1$D!#\e(B@refill
+A field to specify presentation of entity or file name. It is an
+extension for MIME (@ref{MIME}).@refill
@cindex{Experimental}@cindex{RFC 1806}
@noindent
-@node content-type, Content-Type field, Content-Disposition, Glossary
-@subsection content-type
-
-MIME (@ref{MIME}) \e$B$K$*$1$k\e(B part (@ref{part}) \e$B$N<oN`!#\e(B
-@cindex{type}@strong{type} \e$B$H\e(B @cindex{subtype}@strong{subtype} \e$B$+$i$J$k!#\e(B
-RFC 1521 (@ref{RFC 1521}) \e$B$GDj5A$5$l$F$$$k!#\e(B@refill
-
-type \e$B$OI8=`$G$O\e(B @cindex{application}@strong{application},
-@cindex{audio}@strong{audio}, @cindex{image}@strong{image},
-@cindex{message}@strong{message}, @cindex{multipart}@strong{multipart}
-(@ref{multipart}), @cindex{text}@strong{text},
-@cindex{video}@strong{video} \e$B$,Dj5A$5$l!"$=$l$>$l$K$O\e(B
-application/octet-stream, audio/basic, image/jpeg, multipart/mixed
-(@ref{multipart/mixed}), text/plain (@ref{text/plain}), video/mpeg \e$B$J$I\e(B
-\e$B$N$5$^$6$^$J\e(B subtype \e$B$,Dj5A$5$l$F$$$k!#\e(B
-
-@noindent
-@strong{[\e$BCm0U\e(B]}
-@quotation
-
-\e$B$3$3$G$O!"\e(Btext/plain \e$B$J$I$N\e(B type/subtype \e$B$NAH$r$7$P$7$P\e(B
-@cindex{content-type/subtype}@strong{content-type/subtype} \e$B$H=q$/!#\e(B
-@end quotation
-
-
-content-type \e$B$O!"\e(BRFC 1521 \e$B$GDj5A$5$l$F$$$k$b$N$K2C$($F!"EPO?$9$k$3$H$b$G\e(B
-\e$B$-$k!#8=:_!"EPO?$5$l$F$$$k$b$N$O\e(B MEDIA TYPES
-(ftp://ftp.isi.edu/in-notes/iana/assignments/media-types) \e$B$G;2>H$G$-$k!#\e(B
-
-\e$B$^$?!"\e(Btype \e$B$b$7$/$O\e(B subtype \e$B$K!"A0$K\e(B `x-' \e$B$rIU$1$?\e(B
-@cindex{x-token}@strong{x-token} \e$B$rMQ$$$k$3$H$K$h$j!"EPO?$5$l$F$$$J$$$b\e(B
-\e$B$N$r;dE*$KMQ$$$k$3$H$b$G$-$k!#$7$+$7!"EvA3$N$3$H$J$,$i!"$3$&$7$?;dE*$J\e(B
-content-type
\e$B$ONJ2r$rF@$?<T$N4V$G$7$+2r<a$G$-$J$$$N$GMxMQ$K$OCm0U$9$k$3
\e(B
-\e$B$H!#\e(B@refill
-
-(cf. @ref{Content-Type field})
-
-
-
-@node Content-Type field, Emacs, content-type, Glossary
+@node Content-Type field, Emacs, Content-Disposition, Glossary
@subsection Content-Type field
-Header field to represent information about part, such as content-type
-(@ref{content-type}), MIME charset (@ref{MIME charset}). It is defined
-in RFC 1521 (@ref{RFC 1521}).
+Header field to represent information about body, such as media type
+(@ref{media type}), MIME charset (@ref{MIME charset}). It is defined in
+RFC 2045 (@ref{RFC 2045}).
@noindent
@strong{[Memo]}
@quotation
Historically, Content-Type field was proposed in RFC 1049. In it,
-Content-Type did not distinguish type and subtype. However RFC 1521
-parser may be able to accept RFC 1049 based Content-Type as unknown
-type.
+Content-Type did not distinguish type and subtype. However MIME parser
+may be able to accept RFC 1049 based Content-Type as unknown type.
@end quotation
@node Emacs, encoded-word, Content-Type field, Glossary
@subsection Emacs
-\e$B$3$3$G$O\e(B `Emacs' \e$B$G\e(B FSF \e$B$,G[I[$7$F$$$k\e(B GNU Emacs \e$B$r;X$7!"\e(B`emacs' \e$B$G\e(B
-GNU Emacs \e$B$NJQ<o$NAm>N$H$9$k!#\e(B
+In this document, `Emacs' means GNU Emacs released by FSF, and `emacs'
+means any variants of GNU Emacs.
@node encoded-word, encapsulation, Emacs, Glossary
@subsection encoded-word
Representation non ASCII (@ref{ASCII}) characters in header. It is
-defined in @cindex{RFC 1522}@strong{RFC 1522}.@refill
+defined in @cindex{RFC 2047}@strong{RFC 2047}.@refill
-@cindex{Standards Track}@cindex{RFC 1522}
+@cindex{Standards Track}@cindex{RFC 2047}
@noindent
-[RFC 1522]
+[RFC 2047]
@quotation
-K. Moore, ``MIME (Multipurpose Internet Mail Extensions) Part Two:
-Message Header Extensions for Non-ASCII Text'', September 1993,
-Standards Track.
+K. Moore, ``MIME (Multipurpose Internet Mail Extensions) Part Three:
+Message Header Extensions for Non-ASCII Text'', November 1996, Standards
+Track (obsolete RFC 1521,1522,1590).
@end quotation
@node encapsulation, euc-kr, encoded-word, Glossary
@subsection encapsulation
-Internet mail (@ref{RFC 822}) \e$B$rB>$N5-;v$K$^$k$4$HF~$l$kJ}K!!#\e(B@refill
+Method to insert whole Internet message (@ref{RFC 822}) into another
+Internet message.@refill
-\e$BNc$($P!"5-;v$rE>Aw$7$?$j$9$k$N$KMQ$$$k!#\e(B@refill
+For example, it is used to forward a message.@refill
(cf. @ref{message/rfc822})
@node euc-kr, FTP, encapsulation, Glossary
@subsection euc-kr
-\e$B4Z9q8l$rI=8=$9$k$?$a$N\e(B MIME charset (@ref{MIME charset}) \e$B$N#1$D!#\e(B
+A MIME charset (@ref{MIME charset}) for Korean.@refill
-ISO 2022 (@ref{ISO 2022}) \e$B$K4p$$$F\e(B ASCII (@ref{ASCII}) \e$B$K\e(BKS C5601
-(@ref{KS C5601}) \e$B$r\e(B 8bit (@ref{8bit}) \e$B$GId9f3HD%\e(B (@ref{Code extension})
-\e$B$7$F$$$k!#\e(B@refill
+It is a 8bit (@ref{8bit}) coded character set (@ref{coded character
+set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
+(@ref{ASCII}) to combine KS C5601 (@ref{KS C5601}).@refill
-RFC 1557 (@ref{RFC 1557}) \e$B$GDj5A$5$l$F$$$k!#\e(B@refill
+It is defined in RFC 1557 (@ref{RFC 1557}).@refill
cf. @cindex{euc-kr}@cindex{KS C 5861:1992}
@noindent
@node FTP, GB 2312, euc-kr, Glossary
@subsection FTP
-Internet \e$B$G\e(B file \e$B$rE>Aw$9$k$?$a$N\e(B protocol \e$B$N#1$D!#\e(BRFC 959 \e$B$GDj5A$5$l$F\e(B
-\e$B$$$k!#\e(B@refill
-
@cindex{FTP}@cindex{STD 9}@cindex{RFC 959}
@noindent
[FTP: RFC 959]
@node GB 2312, GB 8565.2, FTP, Glossary
@subsection GB 2312-1980
-\e$BCf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=$9$?$a$N\e(B 94\e$B!_\e(B94 \e$BJ8;z\e(B
-\e$B=89g\e(B(@ref{94x94 character set})\e$B!#Cf9q$N9q2HI8=`!#\e(BISO 2022 (@ref{ISO
-2022}) \e$B$G$N=*C<J8;z$O\e(B `A'.@refill
+A 94x94 character set (@ref{94x94 character set}) for Chinese mainly
+written by simplified Chinese mainly used in the Chinese mainland. It
+is a standard of China.@refill
-\e$B$3$l$O\e(B GB \e$B$K$*$1$k4pK\=8$G$"$k!#\e(B
+Final byte of ISO 2022 (@ref{ISO 2022}) is 04/01 (`A').
@cindex{GB 2312}@cindex{GB 2312:1980}
@noindent
[GB 2312]
@quotation
-\e$B!X?.B)8r49MQ4A;zJTb{;zId=8\e(B -- \e$B4pK\=8!Y\e(B, ``Code of Chinese Graphic
-Character Set for Information Interchange - Primary Set'', GB 2312:1980.
+``Code of Chinese Graphic Character Set for Information Interchange -
+Primary Set'', GB 2312:1980.
@end quotation
-@node GB 8565.2, hz-gb2312, GB 2312, Glossary
+@node GB 8565.2, graphic character set, GB 2312, Glossary
@subsection GB 8565.2-1988
-\e$BCf9q8l$N$?$a$NJd=uJ8;z=89g\e(B(@ref{Character set})\e$B!#Cf9q$N9q2HI8=`!#\e(BGB 2312
-(@ref{GB 2312}) \e$B$N6u$-ItJ,$KJd=<$9$k$h$&$KDj5A$5$l$?$i$7$$!#\e(B
+A 94x94 character set (@ref{94x94 character set}) for Chinese as
+supplement to GB 2312 (@ref{GB 2312}). It is a standard of China.
@cindex{GB 8565.2}@cindex{GB 8565.2:1988}
@noindent
-@node hz-gb2312, ISO 2022, GB 8565.2, Glossary
+@node graphic character set, hz-gb2312, GB 8565.2, Glossary
+@subsection Graphic Character Set
+
+Coded character set (@ref{Coded character set}) for graphic characters.
+
+
+@node hz-gb2312, ISO 2022, graphic character set, Glossary
@subsection hz-gb2312
-\e$BCf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N\e(B MIME
-charset (@ref{MIME charset}) \e$B$N#1$D!#\e(B@refill
+A MIME charset (@ref{MIME charset}) for simplified Chinese mainly used
+in the Chinese mainland.@refill
-ASCII (@ref{ASCII}) \e$B$K\e(B GB 2312 (@ref{GB 2312}) \e$B$r\e(B 7bit \e$B$GId9f3HD%\e(B
-(@ref{Code extension})\e$B$7$?$b$N$r\e(B ASCII printable \e$B$K$J$k$h$&$K9)IW$7$F$$\e(B
-\e$B$k!#\e(B@refill
+It extends ASCII (@ref{ASCII}) to combine GB 2312 (@ref{GB 2312}), its
+technique is like iso-2022-jp (@ref{iso-2022-jp}), but it is designed to
+be ASCII printable to use special form for ESC sequence to designate GB
+2312 to G0.@refill
-RFC 1842, 1843 \e$B$GDj5A$5$l$F$$$k!#\e(B
+It is defined in RFC 1842 and 1843.
@cindex{Informational}@cindex{RFC 1842}
@noindent
@node ISO 2022, iso-2022-cn, hz-gb2312, Glossary
@subsection ISO 2022
-\e$BId9f3HD%\e(B(@ref{Code extension})\e$B$N$?$a$N9q:]I8=`!#\e(B@refill
-
-\e$B$3$l$rMQ$$$FJ#?t$NJ8;z=89g\e(B(@ref{Character set})\e$B$rAH9g$;$F\e(B 7bit
-(@ref{7bit}) \e$B$J$$$7\e(B 8bit (@ref{8bit}) \e$B$N\e(B \e$BId9f2=J8;z=89g\e(B(@ref{Coded
-character set}) \e$B$r:n$k$3$H$,$G$-$k!#\e(B
+It is a standard for character code structure and code extension
+(@ref{code extension}) technique.
@cindex{ISO 2022}@cindex{ISO/IEC 2022:1994}
@noindent
@node iso-2022-cn, iso-2022-cn-ext, ISO 2022, Glossary
@subsection iso-2022-cn
-\e$BCf9q8l$rI=8=$9$k$?$a$N\e(B MIME charset (@ref{MIME charset}) \e$B$N#1$D!#\e(B
+A MIME charset (@ref{MIME charset}) for Chinese.@refill
-ISO 2022 (@ref{ISO 2022}) \e$B$K4p$$$F\e(B ASCII (@ref{ASCII}) \e$B$K\e(B GB 2312
-(@ref{GB 2312}), CNS 11643 plain 1, plain 2 (@ref{CNS}) \e$B$r\e(B 7bit
-(@ref{7bit}) \e$B$GId9f3HD%\e(B (@ref{Code extension})\e$B$7$F$$$k!#\e(B@refill
+It is a 7bit (@ref{7bit}) coded character set (@ref{coded character
+set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
+(@ref{ASCII}) to combine GB 2312 (@ref{GB 2312}) and/or CNS 11643 plain
+1, plain 2 (@ref{CNS 11643}).@refill
-RFC 1922 (@ref{RFC 1922}) \e$B$GDj5A$5$l$F$$$k!#\e(B
+It is defined in RFC 1922 (@ref{RFC 1922}).
@node iso-2022-cn-ext, iso-2022-jp, iso-2022-cn, Glossary
@subsection iso-2022-cn-ext
-\e$BCf9q8l$rI=8=$9$k$?$a$N\e(B MIME charset (@ref{MIME charset}) \e$B$N#1$D!#\e(B
+A MIME charset (@ref{MIME charset}) for Chinese.@refill
-ISO 2022 (@ref{ISO 2022}) \e$B$K4p$$$F\e(B ASCII (@ref{ASCII}) \e$B$K\e(B GB 2312
-(@ref{GB 2312}), CNS 11643 plain 1 .. 7 (@ref{CNS}), ISO-IR-165
-(@ref{ISO-IR-165}) \e$BEy$r\e(B 7bit (@ref{7bit}) \e$B$GId9f3HD%\e(B (@ref{Code
-extension})\e$B$7$F$$$k!#\e(B@refill
+It is a 7bit (@ref{7bit}) coded character set (@ref{coded character
+set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
+(@ref{ASCII}) to combine GB 2312 (@ref{GB 2312}), CNS 11643 plain 1 .. 7
+(@ref{CNS 11643}), ISO-IR-165 (@ref{ISO-IR-165}) and other Chinese
+graphic character sets.@refill
-RFC 1922 (@ref{RFC 1922}) \e$B$GDj5A$5$l$F$$$k!#\e(B@refill
+It is defined in RFC 1922 (@ref{RFC 1922}).@refill
@noindent
@strong{[Memo]}
@quotation
-MULE 2.3 \e$B$*$h$S!"8=:_$N\e(B XEmacs/mule \e$B$G$O@5$7$/07$&$3$H$O$G$-$J$$!#\e(B
+MULE 2.3 and current XEmacs/mule can not use it correctly.
-Emacs/mule \e$B$G$OMxMQ2DG=$G$"$k!#\e(B
+Emacs/mule can use it.
@end quotation
@node iso-2022-jp, iso-2022-jp-2, iso-2022-cn-ext, Glossary
@subsection iso-2022-jp
-\e$BF|K\8l$rI=8=$9$k$?$a$N\e(B MIME charset (@ref{MIME charset}) \e$B$N0l$D!#\e(B
+A MIME charset (@ref{MIME charset}) for Japanese.@refill
-\e$B8E$$\e(B ISO 2022 (@ref{ISO 2022}) \e$B$K4p$$$F\e(B ASCII (@ref{ASCII}), JIS
-X0201-Latin, JIS X0208-1978 (@ref{JIS C6226-1978}), JIS X0208-1983
-(@ref{JIS X0208}) \e$B$r@Z$jBX$($k\e(B 7bit (@ref{7bit}) \e$BJ8;zId9f!#\e(B@refill
+It is a 7bit (@ref{7bit}) coded character set (@ref{coded character
+set}) based on old ISO 2022 (@ref{ISO 2022}). It switches ASCII
+(@ref{ASCII}), JIS X0201-Latin, JIS X0208-1978 (@ref{JIS C6226-1978})
+and JIS X0208-1983 (@ref{JIS X0208}).@refill
-RFC 1468 \e$B$GDj5A$5$l$F$$$k!#\e(B@refill
+It is defined in RFC 1468.@refill
@noindent
@strong{[Memo]}
@quotation
-JIS X0208-1996? \e$B$G$O\e(B ISO 2022 (@ref{ISO 2022}) \e$B$HFHN)$KDj5A$5$l$kM=Dj!#\e(B
+JIS X0208-1997? will define it in annex as non-ISO 2022 (@ref{ISO 2022})
+encoding.
@end quotation
@node iso-2022-jp-2, iso-2022-kr, iso-2022-jp, Glossary
@subsection iso-2022-jp-2
-iso-2022-jp (@ref{iso-2022-jp}) \e$B$r3HD%$7$?\e(B MIME charset (@ref{MIME
-charset}) \e$B$N0l$D!#\e(B@refill
+A MIME charset (@ref{MIME charset}), which is a multilingual extension
+of iso-2022-jp (@ref{iso-2022-jp}).@refill
-RFC 1554 \e$B$GDj5A$5$l$F$$$k!#\e(B
+It is defined in RFC 1554.
@cindex{iso-2022-jp-2}@cindex{Informational}@cindex{RFC 1554}
@noindent
@node iso-2022-kr, ISO 646, iso-2022-jp-2, Glossary
@subsection iso-2022-kr
-\e$B4Z9q8l$rI=8=$9$k$?$a$N\e(B MIME charset (@ref{MIME charset}) \e$B$N#1$D!#\e(B
+A MIME charset (@ref{MIME charset}) for Korean language (Hangul
+script).@refill
-ISO 2022 (@ref{ISO 2022}) \e$B$K4p$$$F\e(B ASCII (@ref{ASCII}) \e$B$K\e(B KS C5601
-(@ref{KS C5601}) \e$B$r\e(B 7bit (@ref{7bit}) \e$B$GId9f3HD%\e(B (@ref{Code extension})
-\e$B$7$F$$$k!#\e(B@refill
+It is based on ISO 2022 (@ref{ISO 2022}) code extension (@ref{code
+extension}) technique to extend ASCII (@ref{ASCII}) to use KS C5601
+(@ref{KS C5601}) as 7bit (@ref{7bit}) text.@refill
-RFC 1557 (@ref{RFC 1557}) \e$B$GDj5A$5$l$F$$$k!#\e(B
+It is defined in RFC 1557 (@ref{RFC 1557}).
@node ISO 646, ISO 8859-1, iso-2022-kr, Glossary
@subsection ISO 646
-\e$B3F9q$G6&DL$K;H$($k:G>.8BEY$NJ8;z=89g\e(B(@ref{Character set})\e$B$rDj$a$?$b$N!#\e(B
-94 \e$BJ8;z=89g\e(B (@ref{94 character set})\e$B$N#1$D!#\e(BISO 646 IRV\e$B!J9q:]4p=`HG!K$r\e(B
-\e$B85$K4v$D$+$NJ8;z$O3F9q$G0c$&J8;z$r3dEv$k$3$H$r5v$7$F$$$F!"4v$D$+$NJQ<o$,\e(B
-\e$BB8:_$9$k!#\e(BASCII (@ref{ASCII}) \e$B$d\e(B JIS X0201-Latin \e$B$O$=$N0l<o!#\e(B
-
@cindex{ISO 646}@cindex{ISO/IEC 646:1991}
@noindent
[ISO 646]
@node ISO 8859-1, iso-8859-1, ISO 646, Glossary
@subsection ISO 8859-1
-\e$B@>2$=t8l$GMQ$$$i$l$k3HD%\e(B Latin \e$BJ8;z$d5-9f$+$i$J$k\e(B 96 \e$BJ8;z=89g\e(B(@ref{96
-character set})\e$B!#\e(B
-
@cindex{ISO 8859-1}@cindex{ISO 8859-1:1987}
@noindent
[ISO 8859-1]
@node iso-8859-1, ISO 8859-2, ISO 8859-1, Glossary
@subsection iso-8859-1
-\e$B@>2$=t8l$J$I$rI=8=$9$k$?$a$N\e(B MIME charset (@ref{MIME charset}) \e$B$N#1$D!#\e(B
+@cindex{iso-8859-1}@strong{iso-8859-1} is a MIME charset (@ref{MIME
+charset}) for west-European languages written by Latin script.@refill
-ISO 2022 (@ref{ISO 2022}) \e$B$K4p$$$F!"\e(BASCII (@ref{ASCII}) \e$B$K\e(B ISO 8859-1
-(@ref{ISO 8859-1}) \e$B$r\e(B 8bit (@ref{8bit}) \e$B$GId9f3HD%\e(B (@ref{Code
-extension})\e$B$7$F$$$k!#\e(B@refill
+It is a 8bit (@ref{8bit}) coded character set (@ref{coded character
+set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
+(@ref{ASCII}) to combine ISO 8859-1 (@ref{ISO 8859-1}).@refill
-RFC 1521 (@ref{RFC 1521}) \e$B$GDj5A$5$l$F$$$k!#\e(B
+It is defined in RFC 2046 (@ref{RFC 2046}).
@node ISO 8859-2, iso-8859-2, iso-8859-1, Glossary
@subsection ISO 8859-2
-\e$BEl2$=t8l$GMQ$$$i$l$k3HD%\e(B Latin \e$BJ8;z$d5-9f$+$i$J$k\e(B 96 \e$BJ8;z=89g\e(B(@ref{96
-character set})\e$B!#\e(B
-
@cindex{ISO 8859-2}@cindex{ISO 8859-2:1987}
@noindent
[ISO 8859-2]
@node iso-8859-2, ISO 8859-3, ISO 8859-2, Glossary
@subsection iso-8859-2
-\e$BEl2$=t8l$rI=8=$9$k$?$a$N\e(B MIME charset (@ref{MIME charset}) \e$B$N#1$D!#\e(B
+@cindex{iso-8859-2}@strong{iso-8859-2} is a MIME charset (@ref{MIME
+charset}) for east-European languages written by Latin script.@refill
-ISO 2022 (@ref{ISO 2022}) \e$B$K4p$$$F!"\e(BASCII (@ref{ASCII}) \e$B$K\e(B ISO 8859-2
-(@ref{ISO 8859-2}) \e$B$r\e(B 8bit (@ref{8bit}) \e$B$GId9f3HD%\e(B (@ref{Code
-extension})\e$B$7$F$$$k!#\e(B@refill
+It is a 8bit (@ref{8bit}) coded character set (@ref{coded character
+set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
+(@ref{ASCII}) to combine ISO 8859-2 (@ref{ISO 8859-2}).@refill
-RFC 1521 (@ref{RFC 1521}) \e$B$GDj5A$5$l$F$$$k!#\e(B
+It is defined in RFC 2046 (@ref{RFC 2046}).
@node ISO 8859-3, ISO 8859-4, iso-8859-2, Glossary
@node ISO 8859-5, iso-8859-5, ISO 8859-4, Glossary
@subsection ISO 8859-5
-\e$B%-%j%kJ8;z$d5-9f$+$i$J$k\e(B 96 \e$BJ8;z=89g\e(B(@ref{96 character set})\e$B!#\e(B
-
@cindex{ISO 8859-5}@cindex{ISO 8859-5:1988}
@noindent
[ISO 8859-5]
@node iso-8859-5, ISO 8859-6, ISO 8859-5, Glossary
@subsection iso-8859-5
-\e$B%-%j%kJ8;z$rI=8=$9$k$?$a$N\e(B MIME charset (@ref{MIME charset}) \e$B$N#1$D!#\e(B
+@cindex{iso-8859-5}@strong{iso-8859-5} is a MIME charset (@ref{MIME
+charset}) for Cyrillic script.@refill
-ISO 2022 (@ref{ISO 2022}) \e$B$K4p$$$F!"\e(BASCII (@ref{ASCII}) \e$B$K\e(B ISO 8859-5
-(@ref{ISO 8859-5}) \e$B$r\e(B 8bit (@ref{8bit}) \e$B$GId9f3HD%\e(B (@ref{Code
-extension})\e$B$7$F$$$k!#\e(B@refill
+It is a 8bit (@ref{8bit}) coded character set (@ref{coded character
+set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
+(@ref{ASCII}) to combine ISO 8859-5 (@ref{ISO 8859-5}).@refill
-RFC 1521 (@ref{RFC 1521}) \e$B$GDj5A$5$l$F$$$k!#\e(B
+It is defined in RFC 2046 (@ref{RFC 2046}).
@node ISO 8859-6, ISO 8859-7, iso-8859-5, Glossary
@node ISO 8859-7, iso-8859-7, ISO 8859-6, Glossary
@subsection ISO 8859-7
-\e$B%.%j%7%"J8;z$d5-9f$+$i$J$k\e(B 96 \e$BJ8;z=89g\e(B(@ref{96 character set})\e$B!#\e(B
-
@cindex{ISO 8859-7}@cindex{ISO 8859-7:1987}
@noindent
[ISO 8859-7]
@node iso-8859-7, ISO 8859-8, ISO 8859-7, Glossary
@subsection iso-8859-7
-\e$B%.%j%7%"8l$rI=8=$9$k$?$a$N\e(B MIME charset (@ref{MIME charset}) \e$B$N#1$D!#\e(B
+@cindex{iso-8859-7}@strong{iso-8859-7} is a MIME charset (@ref{MIME
+charset}) for Greek script.@refill
-ISO 2022 (@ref{ISO 2022}) \e$B$K4p$$$F!"\e(BASCII (@ref{ASCII}) \e$B$K\e(B ISO 8859-7
-(@ref{ISO 8859-7}) \e$B$r\e(B 8bit (@ref{8bit}) \e$B$GId9f3HD%\e(B (@ref{Code
-extension})\e$B$7$F$$$k!#\e(B@refill
+It is a 8bit (@ref{8bit}) coded character set (@ref{coded character
+set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
+(@ref{ASCII}) to combine ISO 8859-7 (@ref{ISO 8859-7}).@refill
-RFC 1947 \e$B$GDj5A$5$l$F$$$k!#\e(B
+It is defined in RFC 1947.
@cindex{iso-8859-7}@cindex{Informational}@cindex{RFC 1947}
@noindent
@node ISO-IR-165, JIS X0201, ISO 8859-9, Glossary
@subsection ISO-IR-165, CCITT Extended GB
-CCITT \e$B$,EPO?$7$?!"Cf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=\e(B
-\e$B$9$k$?$a$N\e(B 94\e$B!_\e(B94 \e$BJ8;z=89g\e(B(@ref{94x94 character set})\e$B!#\e(B@refill
+A 94x94-character set (@ref{94x94-character set}) for Chinese mainly
+written by simplified Chinese mainly used in the Chinese mainland
+registered by CCITT.@refill
-GB 2312 (@ref{GB 2312}) \e$B$H\e(B GB 8565 \e$BI=#2\e(B (@ref{GB 8865.2}) \e$B$K\e(B 150 \e$BJ8;z$[\e(B
-\e$B$I$rDI2C$7$?$b$N$i$7$$!#\e(B@refill
+It consists of GB 2312 (@ref{GB 2312}), GB 8865.2 (@ref{GB 8865.2}) and
+additional 150 characters.@refill
-ISO 2022 (@ref{ISO 2022}) \e$B$G$N=*C<J8;z$O\e(B `E' \e$B$G$"$k!#\e(B
+Final byte of ISO 2022 (@ref{ISO 2022}) is 04/05 (`E').
@node JIS X0201, JIS C6226, ISO-IR-165, Glossary
@subsection JIS X0201
-ISO 646 (@ref{ISO 646}) \e$B$NJQ<o$N#1$D$G$"$k\e(B Latin \e$BJ8;z=89g$H\e(B 1 byte \e$B$N%+\e(B
-\e$B%?%+%JJ8;z=89g$+$i$J$k!#\e(B@refill
+It defines two 94-character set (@ref{94-character set}), for Latin
+script (a variant of ISO 646 (@ref{ISO 646})) and Katakana script, and
+7bit and 8bit coded character set (@ref{coded character set})s.@refill
-\e$B85$O\e(B @cindex{JIS C6220-1976}@strong{JIS C6220-1976} \e$B$H8@$C$?$,\e(B @cindex{JIS
-X0201}@strong{JIS
-X0201} \e$B$KHV9f$,JQ99$5$l$?!#\e(B
+It was renamed from @cindex{JIS C6220-1976}@strong{JIS C6220-1976}.
@cindex{JIS X0201-1976}@cindex{JIS X 0201-1976:}
@noindent
[JIS X0201-1976]
@quotation
-\e$BF|K\5,3J6(2q\e(B (Japanese Standards Association),\e$B!X>pJs8r49MQId9f!Y\e(B, ``Code
-for Information Interchange'', JIS X 0201-1976:.
+Japanese Standards Association, ``Code for Information Interchange'',
+JIS X 0201-1976:.
@end quotation
-\e$B$^$?!"\e(B1996 \e$BG/$K2~DjHG$,=P$kM=Dj!#\e(B
+In addition, revised version will be published in 1997.
-@cindex{JIS X0201-1996?}@cindex{JIS X 0201:1996? draft}
+@cindex{JIS X0201-1997?}@cindex{JIS X 0201:1997? draft}
@noindent
-[JIS X0201-1996?]
+[JIS X0201-1997?]
@quotation
-\e$BF|K\5,3J6(2q\e(B (Japanese Standards Association),\e$B!X#7%S%C%H5Z$S#8%S%C%H$N>p\e(B
-\e$BJs8r49MQId9f2=J8;z=89g!Y\e(B, ``7-bit and 8-bit coded character sets for
-information interchange'', JIS X 0201:1996? draft.
+Japanese Standards Association, ``7-bit and 8-bit coded character sets
+for information interchange'', JIS X 0201:1997? draft.
@end quotation
@node JIS C6226, JIS X0208, JIS X0201, Glossary
@subsection JIS C6226-1978
-\e$BF|K\8l$rI=$9$?$a$K:n$i$l$?\e(B 94\e$B!_\e(B94 \e$BJ8;z=89g\e(B(@ref{94x94 character set})\e$B!#\e(B
-\e$BF|K\$N9q2HI8=`!#\e(BJIS X0208-1978 \e$B$H$b$$$&!#\e(B@refill
+A 94x94-character set (@ref{94x94-character set}) for Japanese. It was
+renamed to JIS X0208-1978.@refill
(cf. @ref{JIS X0208})
@node JIS X0208, JIS X0212, JIS C6226, Glossary
@subsection JIS X0208
-\e$BF|K\8l$rI=$9$?$a$K:n$i$l$?\e(B 94\e$B!_\e(B94 \e$BJ8;z=89g\e(B(@ref{94x94 character set})\e$B!#\e(B
-\e$BF|K\$N9q2HI8=`!#\e(B1978 \e$BG/HG!"\e(B1983 \e$BG/HG!"\e(B1990 \e$BG/HG$,$"$k$,!"\e(BInternet \e$B$G$O\e(B
-1983 \e$BG/HG$,$b$C$H$bNI$/;H$o$l$F$$$k!#\e(B@refill
+A 94x94-character set (@ref{94x94-character set}) for Japanese.
+Japanese standard. It was published in 1978, and revised in 1983 and
+1990. In the Internet message, 1983 edition is major.@refill
-JIS X0208 \e$B$O5-9f!"?t;z!"%m!<%^;z!"$R$i$,$J!"%+%?%+%J!"%.%j%7%cJ8;z!"%-%j\e(B
-\e$B%kJ8;z!"7S@~AG!"Bh#1?e=`!"Bh#2?e=`$N4A;z$,4^$^$l$k!#C"$7!"\e(B1983 \e$BG/HG$N0l\e(B
-\e$BIt$N5-9f$H7S@~AG$O\e(B 1978 \e$BG/HG$K$O$J$$!#$^$?!"0lIt$N4A;z$N;z7A$,\e(B 1983 \e$BG/HG\e(B
-\e$B$G$OJQ99$5$l!"$^$?!"Bh#1?e=`$HBh#2?e=`$,F~$lBX$o$C$F$$$?$j$9$k!#$3$N$?$a!"\e(B
-1978 \e$BG/HG$H\e(B 1983 \e$BG/HG$O0[$J$kJ8;z=89g$H$7$F07$o$l$k!#\e(B@refill
+JIS X0208 contains some symbols, numbers, primary Latin script, Hiragana
+script, Katakana script, Greek script, Cyrillic script, box drawing
+parts, Kanji (Ideographic characters used in Japanese). Notice that
+some symbols and box drawing parts were added in 1983 and some Kanjis
+were changed or swapped code points. So 1978 edition and 1983 edition
+are regarded as different graphic character set.@refill
-1990 \e$BG/$N2~Dj$G$O\e(B 1983 \e$BG/HG$KBP$9$kDI2C$,9T$o$l$?!#$3$N$?$a!"\e(B1990 \e$BG/HG\e(B
-\e$B$r;X<($9$k>l9g$OA0$K99?7%7!<%1%s%9$rMQ$$$k!#\e(B
+1990 edition added some characters, so designation of 1990 edition
+requires `identify revised registration' sequence, ESC 02/06 4/0 as
+prefix of designation sequence.
@cindex{JIS X0208-1978}@cindex{JIS C6226:1978}
@noindent
[JIS X0208-1978]
@quotation
-\e$BF|K\5,3J6(2q\e(B (Japanese Standards Association),\e$B!X>pJs8r49MQ4A;zId9f7O!Y\e(B,
-``Code of the Japanese graphic character set for information
-interchange'', JIS C6226:1978.
+Japanese Standards Association, ``Code of the Japanese graphic character
+set for information interchange'', JIS C6226:1978.
@end quotation
-@cindex{JIS X0208-1983,1990}@cindex{JIS X0208:1983,1990}
+@cindex{JIS X0208-1983,1990}@cindex{JIS X0208:1983,1990}
@noindent
[JIS X0208-1983,1990]
@quotation
-\e$BF|K\5,3J6(2q\e(B (Japanese Standards Association),\e$B!X>pJs8r49MQ4A;zId9f7O!Y\e(B,
-``Code of the Japanese graphic character set for information
-interchange'', JIS X0208:1983,1990.
+Japanese Standards Association, ``Code of the Japanese graphic character
+set for information interchange'', JIS X0208:1983,1990.
@end quotation
-\e$B$^$?!"\e(B1996 \e$BG/$K2~DjHG$,=PHG$5$l$kM=Dj!#!J;z7A$NJQ99$O9T$o$l$J$$$N$GJ8\e(B
-\e$B;z=89g$H$7$F$O\e(B 1990 \e$BG/HG$HF10l$G$"$k!K\e(B
+In addition, revised version will be published in 1997. (It does not
+change graphic character set)
-@cindex{JIS X0208-1996?}@cindex{JIS X 0208:1996? draft}
+@cindex{JIS X0208-1997?}@cindex{JIS X 0208:1997? draft}
@noindent
-[JIS X0208-1996?]
+[JIS X0208-1997?]
@quotation
-\e$BF|K\5,3J6(2q\e(B (Japanese Standards Association),\e$B!X#7%S%C%H5Z$S#8%S%C%H$N\e(B
-\e$B#2%P%$%H>pJs8r49MQId9f2=4A;z=89g!Y\e(B, ``7-bit and 8-bit double byte coded
-Kanji sets for information interchange'', JIS X 0208:1996? draft.
+Japanese Standards Association, ``7-bit and 8-bit double byte coded
+Kanji sets for information interchange'', JIS X 0208:1997? draft.
@end quotation
@node JIS X0212, koi8-r, JIS X0208, Glossary
@subsection JIS X0212-1990
-JIS X0208 (@ref{JIS X0208}) \e$B$K$J$+$C$?J8;z$r=8$a$?\e(B 94\e$B!_\e(B94 \e$BJ8;z=89g\e(B
-(@ref{94x94 character set})\e$B!#!VJd=u4A;z!W$H$b8F$P$l$k!#F|K\$N9q2HI8=`!#\e(B
-ISO 2022 (@ref{ISO 2022}) \e$B$G$N=*C<J8;z$O\e(B `D'.
+A 94x94 character set (@ref{94x94 character set}) for Japanese as
+supplement to JIS X0208 (@ref{JIS X0208}). It is a standard of
+Japan.@refill
+
+Final byte of ISO 2022 (@ref{ISO 2022}) is 04/04 (`D').
@node koi8-r, KS C5601, JIS X0212, Glossary
@subsection koi8-r
-\e$B%m%7%d8lEy$GMQ$$$i$l$k%-%j%kJ8;z$rI=8=$9$k$?$a$N\e(B MIME charset (@ref{MIME
-charset}) \e$B$N#1$D!#\e(B@refill
+A MIME charset (@ref{MIME charset}) for Cyrillic script for Russian or
+other languages.@refill
-ISO 2022 (@ref{ISO 2022}) \e$B$K4p$+$J$$\e(B 8bit (@ref{8bit}) \e$B$NId9f2=J8;z=89g\e(B
-(@ref{Coded character set})\e$B$G\e(B de-fact standard \e$B$G$"$k!#\e(B
+It is a 1 byte 8bit (@ref{8bit}) coded character set (@ref{coded
+character set}), not based on ISO 2022 (@ref{ISO 2022}). It is a
+de-fact standard.@refill
-RFC 1489 \e$B$GDj5A$5$l$F$$$k!#\e(B@refill
+It is defined in RFC 1489.@refill
@cindex{RFC 1489}
@noindent
-@node KS C5601, message, koi8-r, Glossary
+@node KS C5601, media type, koi8-r, Glossary
@subsection KS C5601-1987
-\e$B4Z9q8l$rI=$9$?$a$N\e(B 94\e$B!_\e(B94 \e$BJ8;z=89g\e(B(@ref{94x94 character set})\e$B!#4Z9q$N9q\e(B
-\e$B2HI8=`!#\e(BISO 2022 (@ref{ISO 2022}) \e$B$G$N=*C<J8;z$O\e(B `C'.
+A 94x94-character set (@ref{94x94-character set}) for Korean language
+(Hangul script). Korean Standard. Final byte of ISO 2022 (@ref{ISO
+2022}) is 04/03 (`C').
@cindex{KS C5601}@cindex{KS C 5601:1987}
@noindent
-@node message, message/rfc822, KS C5601, Glossary
+@node media type, message, KS C5601, Glossary
+@subsection media type
+
+@cindex{media type}@strong{media type} specifies the nature of the data
+in the body of MIME (@ref{MIME}) entity (@ref{entity}). It consists of
+@cindex{type}@strong{type} and @cindex{subtype}@strong{subtype}. It is
+defined in RFC 2046 (@ref{RFC 2046}).@refill
+
+Currently there are following types:
+
+@itemize @bullet
+@item
+@cindex{text}@strong{text}
+@item
+@cindex{image}@strong{image}
+@item
+@cindex{audio}@strong{audio}
+@item
+@cindex{video}@strong{video}
+@item
+@cindex{application}@strong{application}
+@item
+@cindex{multipart}@strong{multipart} (@ref{multipart})
+@item
+@cindex{message}@strong{message}
+@end itemize
+
+
+And there are various subtypes, for example, application/octet-stream,
+audio/basic, image/jpeg, multipart/mixed (@ref{multipart/mixed}),
+text/plain (@ref{text/plain}), video/mpeg...@refill
+
+You can refer registered media types at MEDIA TYPES
+(ftp://ftp.isi.edu/in-notes/iana/assignments/media-types).@refill
+
+In addition, you can use private type or subtype using
+@cindex{x-token}@strong{x-token}, which as the prefix `x-'. However you
+can not use them in public.@refill
+
+(cf. @ref{Content-Type field})
+
+
+
+@node message, message/rfc822, media type, Glossary
@subsection message
-\e$B$3$3$G$O\e(B RFC 822 (@ref{RFC 822}) \e$B$GDj5A$5$l$k\e(B mail \e$B$H\e(B RFC 1036 (@ref{RFC
-1036}) \e$B$GDj5A$5$l$k\e(B news \e$B5-;v$NAm>N$H$7$FMQ$$$k!#\e(B
+In this document, it means mail defined in RFC 822 (@ref{RFC 822}) and
+news message defined in RFC 1036 (@ref{RFC 1036}).
@node message/rfc822, method, message, Glossary
@subsection message/rfc822
-\e$BEAE}E*$J\e(B RFC 934 (@ref{RFC 934}) \e$B$KBe$o$j!"\e(BRFC 822 (@ref{RFC 822}) \e$B$GDj\e(B
-\e$B5A$5$l$k\e(B mail \e$B$rI=$9\e(B MIME \e$B$N7A<0!#\e(BRFC 1521 (@ref{RFC 1521}) \e$B$GDj5A$5$l$F\e(B
-\e$B$$$k!#\e(B
+@cindex{message/rfc822}@strong{message/rfc822} indicates that the body
+contains an encapsulated message, with the syntax of an RFC 822
+(@ref{RFC 822}) message. It is the replacement of traditional RFC 934
+(@ref{RFC 934}) encapsulation. It is defined in RFC 2046 (@ref{RFC
+2046}).
@node method, MIME, message/rfc822, Glossary
@subsection method
-tm \e$B$GFCDj$N<oN`$N\e(B data \e$B$r:F@8$7$?$H$-<B:]$K$=$N=hM}$r9T$J$&\e(B
-program. Emacs Lisp \e$B$G=q$+$l$?\e(B @cindex{internal method}@strong{internal
-method} \e$B$H\e(B C \e$B$d\e(B script \e$B8@8l$J$I$G=q$+$l$?\e(B @cindex{external
-method}@strong{external method} \e$B$,$"$k!#\e(B@refill
+Application program of tm-view to process for specified media type
+(@ref{media type}) when user plays an entity.@refill
+
+There are two kinds of methods, @cindex{internal method}@strong{internal
+method} and @cindex{external method}@strong{external method}. Internal
+method is written by Emacs Lisp. External method is written by C or
+script languages and called by asynchronous process call.@refill
(cf. @ref{(tm-view-en)method})
@node MIME, MIME charset, method, Glossary
@subsection MIME
-@cindex{Multipurpose Internet Mail Extensions}@strong{Multipurpose
-Internet Mail Extensions} \e$B$NN,$G!"\e(BInternet \e$B$N\e(B mail \e$B$d\e(B news \e$B$G\e(B us-ascii
-plain text (@ref{us-ascii}) \e$B0J30$NJ8;z$r;H$&$?$a$N\e(B RFC 822 (@ref{RFC
-822}) \e$B$KBP$9$k3HD%!#\e(B@refill
+MIME stands for @cindex{Multipurpose Internet Mail
+Extensions}@strong{Multipurpose Internet Mail Extensions}, it is an
+extension for RFC 822 (@ref{RFC 822}).@refill
+
+According to RFC 2045:@refill
-RFC 1521 (@ref{RFC 1521}) \e$B$H\e(B RFC 1522 (@ref{encoded-word}) \e$B$GDj5A$5$l$F\e(B
-\e$B$$$k!#\e(B@refill
+STD 11, RFC 822, defines a message representation protocol specifying
+considerable detail about US-ASCII message headers, and leaves the
+message content, or message body, as flat US-ASCII text. This set of
+documents, collectively called the Multipurpose Internet Mail
+Extensions, or MIME, redefines the format of messages to allow
+for@refill
+
+@enumerate
+@item
+textual message bodies in character sets other than US-ASCII,
+@item
+an extensible set of different formats for non-textual message
+bodies,
+@item
+multi-part message bodies, and
+@item
+textual header information in character sets other than US-ASCII.
+@end enumerate
-(cf. @ref{What is MIME?})
+It is defined in RFC 2045 (@ref{RFC 2045}), RFC 2046 (@ref{RFC 2046}),
+RFC 2047 (@ref{encoded-word}), RFC 2048 (@ref{RFC 2048}) and RFC 2049
+(@ref{RFC 2049}).
@node MIME charset, MTA, MIME, Glossary
@subsection MIME charset
-Content-Type field (@ref{Content-Type field}) \e$B$d\e(B encoded-word
-(@ref{encoded-word}) \e$B$N\e(B charset parameter \e$B$GMQ$$$i$l$kEPO?$5$l$?Id9f2=J8\e(B
-\e$B;z=89g\e(B (@ref{Coded character set})\e$B!#\e(B@refill
+Coded character set (@ref{Coded character set}) used in Content-Type
+field (@ref{Content-Type field}) or charset parameter of encoded-word
+(@ref{encoded-word}).@refill
-RFC 1521 (@ref{RFC 1521}) \e$B$GDj5A$5$l$F$$$k!#\e(B@refill
+It is defined in RFC 2045 (@ref{RFC 2045}).@refill
-iso-2022-jp (@ref{iso-2022-jp}) \e$B$d\e(B euc-kr (@ref{euc-kr}) \e$B$O$=$N#1$D!#\e(B
-\e$B!J$3$3$G$O!"\e(BMIME charset \e$B$OJ8;z=89g\e(B (@ref{Character set})\e$B$H6hJL$7$F>.J8\e(B
-\e$B;z$G=q$$$F$$$k!K\e(B
+iso-2022-jp (@ref{iso-2022-jp}) or euc-kr (@ref{euc-kr}) are kinds of
+it. (In this document, MIME charsets are written by small letters to
+distinguish graphic character set (@ref{graphic character set}). For
+example, ISO 8859-1 is a graphic character set, and iso-8859-1 is a MIME
+charset)
@node MTA, MUA, MIME charset, Glossary
@subsection MTA
-@cindex{Message Transfer Agent}@strong{Message Transfer Agent} \e$B$NN,$G!"\e(B
-sendmail \e$B$J$I$N\e(B mail \e$BG[Aw\e(B program \e$B$H\e(B news server \e$B$NAm>N!#\e(B@refill
+@cindex{Message Transfer Agent}@strong{Message Transfer Agent}. It
+means mail transfer programs (ex. sendmail) and news servers.@refill
(cf. @ref{MUA})
@node MUA, MULE, MTA, Glossary
@subsection MUA
-@cindex{Message User Agent}@strong{Message User Agent} \e$B$NN,$G!"\e(Bmail
-reader \e$B$H\e(B news reader \e$B$NAm>N!#\e(B@refill
+@cindex{Message User Agent}@strong{Message User Agent}. It means mail
+readers and news readers.@refill
(cf. @ref{MTA})
@node MULE, multipart, MUA, Glossary
@subsection MULE
-\e$BH>ED\e(B \e$B7u0l;a$i$,:n$C$?!"B?8@8l$5$l$?\e(B Emacs (@ref{Emacs}).@refill
+Multilingual extension of GNU Emacs (@ref{Emacs}) by HANDA Ken'ichi et
+al.
-[MULE] Nishikimi M., Handa K. and Tomura S., ``Mule: MULtilingual
-Enhancement to GNU Emacs'', Proc. of INET'93, August, 1993.@refill
+@cindex{MULE}
+@noindent
+[MULE]
+@quotation
+Nishikimi M., Handa K. and Tomura S., ``Mule: MULtilingual Enhancement
+to GNU Emacs'', Proc. of INET'93, August, 1993.
+@end quotation
-\e$B8=:_!"\e(BMULE \e$B$N5!G=$r\e(B Emacs \e$B$K\e(B merge \e$B$9$k:n6H$,9T$o$l$F$*$j!"\e(Balpha \e$BHG\e(B
-(ftp://etlport.etl.go.jp/pub/mule/mule-19.33-gamma.taz) \e$B$,B8:_$9$k!#\e(B
+Now, FSF and HANDA Ken'ichi et al. are working to merge MULE feature
+into Emacs, there is alpha version of mule merged emacs
+(ftp://etlport.etl.go.jp/pub/mule/mule-19.33-delta.taz).@refill
-\e$B$=$NB>!"\e(BXEmacs \e$B$K\e(B merge \e$B$7$?$b$N$bB8:_$9$k!#\e(B@refill
+In addition, there is XEmacs with mule feature.@refill
-\e$B$3$N$?$a!"8=:_$G$OB?8@8l\e(B Emacs \e$B$O!"85!9$N\e(B MULE \e$B$r4^$a$F#3<oN`$"$k$3$H$K\e(B
-\e$B$J$k!#\e(B@refill
+So now, there are 3 kinds of mule variants.@refill
-\e$B$=$3$G!"$3$3$G$O!"B?8@8l\e(B Emacs \e$B$NAm>N$r\e(B @cindex{mule}@strong{mule}, \e$B85!9\e(B
-\e$B$N\e(B MULE \e$B$r\e(B @cindex{MULE}@strong{MULE}, mule \e$B5!G=$r\e(B merge \e$B$7$?\e(B Emacs \e$B$r\e(B
-@cindex{Emacs/mule}@strong{Emacs/mule}, mule \e$B5!G=$r\e(B merge \e$B$7$?\e(B XEmacs \e$B$r\e(B
-@cindex{XEmacs/mule}@strong{XEmacs/mule} \e$B$H8F$V$3$H$K$9$k!#\e(B
+In this document, @cindex{mule}@strong{mule} means any mule variants,
+@cindex{MULE}@strong{MULE} means original MULE (..2.3),
+@cindex{Emacs/mule}@strong{Emacs/mule} means mule merged Emacs,
+@cindex{XEmacs/mule}@strong{XEmacs/mule} means XEmacs with mule feature.
@node multipart, multipart/alternative, MULE, Glossary
@subsection Multipart
-\e$B#1$D$N\e(B message (@ref{message}) \e$B$KJ#?t$N\e(B part \e$B$rF~$l$k$?$a$N\e(B MIME
-(@ref{MIME}) \e$B$K$*$1$kI=8=K!!"$b$7$/$O!"J#?t$N\e(B part \e$B$+$i$J$k\e(B message \e$B$r;X\e(B
-\e$B$9!#\e(B(cf. @ref{content-type}) @refill
+@cindex{multipart}@strong{multipart} means media type (@ref{media type})
+to insert multiple entities (@ref{entities}) in a single body. Or it
+also indicates a message consists of multiple entities.@refill
-\e$B8=:_!"Dj5A$5$l$F$$$k\e(B @cindex{multipart}@strong{multipart} \e$B$H$7$F$O!"\e(BRFC
-1521 (@ref{RFC 1521}) \e$B$GDj5A$5$l$?\e(B
+There are following subtypes registered in RFC 2046 (@ref{RFC 2046}):
@itemize @bullet
@item
@end itemize
@noindent
-\e$B$N$[$+\e(B RFC 1847 (@ref{Security multipart}) \e$B$GDj5A$5$l$?\e(B
+and registered in RFC 1847 (@ref{Security multipart}):
@itemize @bullet
@item
multipart/encrypted (@ref{multipart/encrypted})
@end itemize
-@noindent
-\e$B$J$I$,$"$k!#\e(B
@node multipart/alternative, multipart/digest, multipart, Glossary
@subsection multipart/alternative
-multipart (@ref{multipart}) \e$B$N#1$D$G!"F1$8>pJs$r0[$C$?7A<0$GF~$l!"A*Br;h\e(B
-\e$B$H$9$k>l9g$KMQ$$$k!#\e(B@refill
+@cindex{multipart/digest}@strong{multipart/digest} is one of multipart
+(@ref{multipart}) media types. This type is syntactically identical to
+multipart/mixed (@ref{multipart/mixed}), but the semantics are
+different. In particular, each of the body parts is an ``alternative''
+version of the same information.@refill
-(cf. @ref{RFC 1521})
+(cf. @ref{RFC 2046})
@node multipart/digest, multipart/encrypted, multipart/alternative, Glossary
@subsection multipart/digest
-multipart (@ref{multipart}) \e$B$N#1$D$G!"4^$^$l$k\e(B part \e$B$N\e(B default \e$B$N\e(B
-content-type (@ref{content-type}) \e$B$,\e(B multipart/mixed
-(@ref{multipart/mixed}) \e$B$J$I$N>l9g\e(B text/plain (@ref{text/plain}) \e$B$G$"$k\e(B
-\e$B$N$KBP$7!"\e(B@cindex{multipart/digest}@strong{multipart/digest}\e$B$G$O\e(B
-message/rfc822 (@ref{message/rfc822}) \e$B$,MQ$$$i$l$kE@$,0[$J$k!#\e(B@refill
+@cindex{multipart/digest}@strong{multipart/digest} is one of multipart
+(@ref{multipart}) media types. This type is syntactically identical to
+multipart/mixed (@ref{multipart/mixed}), but the semantics are
+different. In particular, in a digest, the default Content-Type value
+for a body part is changed from text/plain (@ref{text/plain}) to
+message/rfc822 (@ref{message/rfc822}).@refill
-\e$B$3$l$OEAE}E*$J\e(B RFC 1153 (@ref{RFC 1153}) \e$B$K4p$E$/\e(B encapsulation
-(@ref{encapsulation}) \e$B$KBe$o$k$b$N$G$"$k!#\e(B@refill
+This is the replacement of traditional RFC 1153 (@ref{RFC 1153}) based
+encapsulation (@ref{encapsulation}).@refill
-(cf. @ref{RFC 1521})
+(cf. @ref{RFC 2046})
@node multipart/encrypted, multipart/mixed, multipart/digest, Glossary
@subsection multipart/encrypted
-RFC 1847 \e$B$GDj5A$5$l$?\e(B Security multipart (@ref{Security multipart}) \e$B$N#1\e(B
-\e$B$D$G!"0E9f2=$5$l$?\e(B message \e$B$rI=8=$9$k$N$KMQ$$$k!#\e(B@refill
+It is a Security multipart (@ref{Security multipart}) defined in RFC
+1847, used to represent encrypted message.@refill
(cf. @ref{PGP/MIME})
@node multipart/mixed, multipart/parallel, multipart/encrypted, Glossary
@subsection multipart/mixed
-multipart (@ref{multipart}) \e$B$N<gMW$J\e(B subtype \e$B$G!"J#?t$N\e(B part \e$B$r=g=xIU$1\e(B
-\e$B$FJB$Y$k>l9g$KMQ$$$k!#\e(B@refill
+Primary and default subtype of multipart (@ref{multipart}), it is used
+when the body parts are independent and need to be bundled in a
+particular order.@refill
-(cf. @ref{RFC 1521})
+(cf. @ref{RFC 2046})
@node multipart/parallel, multipart/signed, multipart/mixed, Glossary
@subsection multipart/parallel
-multipart (@ref{multipart}) \e$B$N#1$D$G!"J#?t$N\e(B part \e$B$r=g=xIU$1$:$K4^$a$k>l\e(B
-\e$B9g$KMQ$$$k!#\e(B@refill
+@cindex{multipart/parallel}@strong{multipart/parallel} is a subtype of
+multipart (@ref{multipart}). This type is syntactically identical to
+multipart/mixed (@ref{multipart/mixed}), but the semantics are
+different. In particular, in a parallel entity, the order of body parts
+is not significant.@refill
-(cf. @ref{RFC 1521})
+(cf. @ref{RFC 2046})
@node multipart/signed, PGP, multipart/parallel, Glossary
@subsection multipart/signed
-RFC 1847 \e$B$GDj5A$5$l$?\e(B Security multipart (@ref{Security multipart}) \e$B$N#1\e(B
-\e$B$D$G!"EE;R=pL>$rI=8=$9$k$N$KMQ$$$k!#\e(B@refill
+It is a Security multipart (@ref{Security multipart}) defined in RFC
+1847, used to represent signed message.@refill
(cf. @ref{PGP/MIME})
@node PGP, PGP-kazu, multipart/signed, Glossary
@subsection PGP
-Phil Zimmermann \e$B;a$,:n@.$7$?8x3+800E9f=hM}7O$N#1$D!#\e(Bmessage
-(@ref{message}) \e$B$N0E9f2=$dEE;R=pL>$r9T$&$3$H$,$G$-$k!#\e(BPretty Good
-Privacy \e$B$NN,!#\e(B@refill
+A public key encryption program by Phil Zimmermann. It provides
+encryption and signature for message (@ref{message}). PGP stands for
+@cindex{Pretty Good Privacy}@strong{Pretty Good Privacy}.@refill
-\e$BEAE}E*$J\e(B PGP \e$B$G$O\e(B encapsulation (@ref{encapsulation}) \e$B$K\e(B RFC 934
-(@ref{RFC 934})\e$B$K=`$8$?J}K!$rMQ$$$k!#$3$l$O\e(B MIME (@ref{MIME}) \e$B$HL7=b$9$k\e(B
-\e$B$N$G\e(B PGP/MIME (@ref{PGP/MIME}) \e$B$,Ds0F$5$l$F$$$k!#0lJ}!"\e(BMIME \e$B$K$*$$$F\e(B PGP
-\e$B$N\e(Bencapsulation \e$B$rMQ$$$kJ}K!\e(B (cf. @ref{PGP-kazu})
- \e$B$bMxMQ$5$l$F$-$?!#$7$+$7!":#8e$O\e(B PGP/MIME \e$B$KE}0l$7$F$$$/J}$,K>$^$7$$!#\e(B
-@refill
+Traditional PGP uses RFC 934 (@ref{RFC 934}) encapsulation
+(@ref{encapsulation}). It is conflict with MIME (@ref{MIME}). So
+PGP/MIME (@ref{PGP/MIME}) is defined. On the other hand, PGP-kazu
+(@ref{PGP-kazu}) was proposed to use PGP encapsulation in MIME. But it
+is obsoleted.@refill
@cindex{PGP}@cindex{Informational}@cindex{RFC 1991}
@noindent
@node PGP-kazu, PGP/MIME, PGP, Glossary
@subsection PGP-kazu
-\e$B;3K\\e(B \e$BOBI'\e(B \e$B;a$,Ds0F$7$?\e(B MIME (@ref{MIME}) \e$B$G\e(B PGP (@ref{PGP}) \e$B$rMxMQ$9$k$?\e(B
-\e$B$a$NJ}K!$r$3$3$G$O\e(B @cindex{PGP-kazu}@strong{PGP-kazu} \e$B$H8F$V$3$H$K$9$k!#\e(B
-
-PGP-kazu \e$B$O\e(B @cindex{application/pgp}@strong{application/pgp} \e$B$H$$$&\e(B
-content-type (@ref{content-type}) \e$B$rDj5A$9$k!#\e(B@refill
-
-application/pgp \e$B$N\e(B part \e$B$G$O\e(B PGP \e$B$N\e(B encapsulation (@ref{encapsulation})
-\e$B$,MQ$$$i$l$k!#\e(BPGP \e$B$N\e(B encapsulation (cf. @ref{RFC 934})
- \e$B$H\e(B MIME \e$B$N\e(B encapsulation \e$B$OL7=b$9$k$N$G!"\e(BPGP \e$B$N\e(B encapsulation \e$B$r2r$+$J\e(B
-\e$B$$8B$j!"Cf$K4^$^$l$?\e(B MIME message \e$B$rFI$`$3$H$,$G$-$J$/$J$k!#B($A!"\e(B
-PGP-kazu \e$B$KBP1~$7$F$$$J$$\e(B MIME \e$B$KBP1~$7$?\e(B MUA (@ref{MUA}) \e$B$O$=$N\e(B part \e$B$,\e(B
-\e$BFI$a$J$/$J$k!#$=$NBe$o$j!"\e(BMIME \e$B$KBP1~$7$F$$$J$$\e(B PGP \e$BBP1~$N\e(B MUA
-(@ref{MUA}) \e$B$G$b\e(B message \e$B$rFI$`$3$H$,$G$-$k!#\e(B@refill
+In this document, @cindex{PGP-kazu}@strong{PGP-kazu} means a method to
+use traditional PGP encapsulation in MIME (@ref{MIME}), proposed by
+YAMAMOTO Kazuhiko.@refill
-PGP-kazu \e$B$G$O\e(B MUA \e$B$O\e(B PGP \e$B$N$H\e(B MIME \e$B$N$H$$$$D$N\e(B encapsulation \e$B$rCN$i$J\e(B
-\e$B$1$l$P$J$i$J$$!#$^$?!"\e(Bapplication/pgp part \e$B$r\e(B parse \e$B$9$k$?$a$K$O!"$^$:!"\e(B
-pgp \e$B$N=hM}$r9T$o$J$1$l$P$J$i$J$$$N$G!"\e(Bparse \e$B=hM}$,J#;($K$J$k!#\e(B@refill
+PGP-kazu defines a media type (@ref{media type}),
+@cindex{application/pgp}@strong{application/pgp}.@refill
-\e$B$^$?!"\e(BInternet \e$B$G$O:#8e\e(B PGP/MIME (@ref{PGP/MIME}) \e$B$NJ}8~$GI8=`2=$7$F$$$3\e(B
-\e$B$&$H$$$&$3$H$G9g0U$,<h$l$F$$$k!#$h$C$F!":#8e$O\e(B PGP-kazu \e$B$OMQ$$$J$$$N$,K>\e(B
-\e$B$^$7$$!#\e(B@refill
+In application/pgp entity, PGP encapsulation (@ref{encapsulation}) is
+used. PGP encapsulation conflicts with MIME, so it requires
+PGP-processing to read as MIME message.@refill
-[draft-kazu-pgp-mime-00.txt] Yamamoto K., ``PGP MIME Integration'',
-October, 1995
+It was obsoleted, so you should use PGP/MIME (@ref{PGP/MIME}). However
+if you want to use traditional PGP message, it might be available.
@node PGP/MIME, Quoted-Printable, PGP-kazu, Glossary
@subsection PGP/MIME
-Michael Elkins \e$B;a$,Ds0F$7$?\e(B MIME (@ref{MIME}) \e$B$G\e(B PGP (@ref{PGP}) \e$B$rMxMQ\e(B
-\e$B$9$k$?$a$NJ}K!!#\e(B@refill
+PGP (@ref{PGP}) and MIME (@ref{MIME}) integration proposed by Michael
+Elkins.@refill
-RFC 1847 (@ref{Security multipart}) \e$B$K4p$-!"\e(BMIME \e$B$N\e(B multipart \e$B$K$h$k\e(B
-encapsulation (@ref{encapsulation}) \e$B$r9T$&!#$3$N$?$a!"\e(BMIME \e$B$N<+A3$J3HD%\e(B
-\e$B$K$J$C$F$$$k!#$7$+$7!"EAE}E*$J\e(B PGP\e$B$H$N8_49@-$,<:$o$l$F$$$k!#\e(B@refill
+It is based on RFC 1847 (@ref{Security multipart}), so it is harmonious
+with MIME, but it is not compatible with traditional PGP encapsulation.
+However MIME MUA can read PGP/MIME signed message even if it does not
+support PGP/MIME.@refill
-PGP/MIME \e$B$G$O\e(B PGP-kazu (@ref{PGP-kazu}) \e$B$H0[$J$j!"\e(BMIME \e$B$N\e(B encapsulation
-\e$B$N$_$rMQ$$$k!#$^$?!"$3$N$?$a!"\e(BPGP \e$B$N=hM}$r9T$&A0$K\e(B message \e$B$N\e(B parse \e$B$r9T\e(B
-\e$B$&$3$H$,$G$-$k!#\e(B@refill
-
-Internet \e$B$G$O:#8e\e(B PGP/MIME (@ref{PGP/MIME}) \e$B$NJ}8~$GI8=`2=$7$F$$$3$&$H$$\e(B
-\e$B$&$3$H$G9g0U$,<h$l$F$$$k!#$h$C$F!":#8e$O\e(B PGP \e$B$rMQ$$$k>l9g$O\e(B PGP/MIME\e$B$rMQ\e(B
-\e$B$$$k$N$,K>$^$7$$!#\e(B
+PGP/MIME (@ref{PGP/MIME}) will be standard of PGP message.
@cindex{PGP/MIME}@cindex{Standards Track}@cindex{RFC 2015}
@noindent
@node Quoted-Printable, RFC 821, PGP/MIME, Glossary
@subsection Quoted-Printable
-RFC 1521 (@ref{RFC 1521}) \e$B$GDj5A$5$l$F$$$k\e(B MIME (@ref{MIME}) \e$B$K$*$1$k\e(B
-binary data (@ref{binary}) \e$B$N\e(B network \e$B$G$NJQ49K!$N#1$D!#\e(B@refill
+@cindex{Quoted-Printable}@strong{Quoted-Printable} is a transfer
+encoding method of MIME (@ref{MIME}) defined in RFC 2045 (@ref{RFC
+2045}).@refill
+
+If the data being encoded are mostly US-ASCII text, the encoded form of
+the data remains largely recognizable by humans.@refill
-`=' \e$B$d@)8fJ8;z$d\e(B 128 \e$B0J>e$NJ8;z$J$I$O\e(B `=AF' \e$B$N$h$&$K\e(B `=' \e$B$N8e$KB3$/\e(B 16
-\e$B?J?t$GI=8=$9$k!#$3$N$?$a!"\e(BASCII (@ref{ASCII}) \e$BJ8;zCf?4$N\e(B data \e$B$G$O\e(B
-Base64 (@ref{Base64}) \e$B$KHf$Y$k$H2DFI@-$,9b$/$J$k2DG=@-$,$"$k!#\e(B@refill
+(cf. @ref{Base64})
-\e$B$7$+$7$J$,$i!"\e(BEBCDIC \e$B$K$OB8:_$7$J$$J8;z$rMxMQ$9$k>l9g!"\e(BEBCDIC \e$B$rMxMQ$7\e(B
-\e$B$F$$$k\e(B network \e$B$G$O0BA4$KE>Aw$9$k$3$H$,$G$-$:!"\e(BBase64 \e$B$KHf$Y$F0BA4@-$O\e(B
-\e$BDc$$!#\e(B
@node RFC 821, RFC 822, Quoted-Printable, Glossary
@subsection RFC 821
-@cindex{SMTP}@strong{SMTP} \e$B$H8F$P$l$k\e(B Internet mail \e$B$NG[AwK!$NI8=`$rDj$a\e(B
-\e$B$F$$$k\e(B RFC.
-
@cindex{SMTP}@cindex{STD 10}@cindex{RFC 821}
@noindent
[SMTP: RFC 821]
@node RFC 822, RFC 934, RFC 821, Glossary
@subsection RFC 822
-Internet mail \e$B$N<g$K\e(B @cindex{message header}@strong{message header} \e$B$K4X$9$k7A<0$K\e(B
-\e$B4X$9$kI8=`$rDj$a$F$$$k\e(B RFC.
+A RFC defines format of Internet mail message, mainly @cindex{message
+header}@strong{message
+header}.
@noindent
@strong{[Memo]}
@quotation
-news message \e$B$b$3$l$K=`$8$F$$$k$N$G!"\e(B@cindex{Internet
-mail}@strong{Internet mail} \e$B$H=q$/$h$j$b!"\e(B@cindex{Internet
-message}@strong{Internet message} \e$B$H=q$$$?J}$,NI$$$+$b$7$l$J$$!#\e(B
+news message is based on RFC 822, so @cindex{Internet
+message}@strong{Internet message} may be more suitable than
+@cindex{Internet mail}@strong{Internet mail} .
@end quotation
@node RFC 934, RFC 1036, RFC 822, Glossary
@subsection RFC 934
-Internet mail (@ref{RFC 822}) \e$B$N\e(B
-@cindex{encapsulation}@strong{encapsulation} (@ref{encapsulation}) \e$B$NJ}\e(B
-\e$BK!$rDj$a$?\e(B RFC.@refill
-
-MIME (@ref{MIME}) \e$B$HL7=b$9$k$N$G!"8=:_$G$O\e(B message/rfc822
-(@ref{message/rfc822}) \e$B$rMQ$$$k$Y$-$G$"$k!#\e(B
+A RFC defines an @cindex{encapsulation}@strong{encapsulation}
+(@ref{encapsulation}) method for Internet mail (@ref{RFC 822}).@refill
+It conflicts with MIME (@ref{MIME}), so you should use message/rfc822
+(@ref{message/rfc822}).
@cindex{RFC 934}
@noindent
@node RFC 1036, RFC 1153, RFC 934, Glossary
@subsection RFC 1036
-USENET \e$B$G$N\e(B message \e$B$N7A<0$rDj$a$?\e(B RFC. RFC 822 (@ref{RFC 822})\e$B$N\e(B subset
-\e$B$K$J$C$F$$$k!#\e(BInternet \e$B$NI8=`$G$O$J$$$,!"\e(BUSENET \e$B0J30$N\e(B netnews \e$B$G$b$3$l\e(B
-\e$B$K=`$8$F$$$k$b$N$,B?$$!#\e(B
+A RFC defines format of USENET message. It is a subset of RFC 822
+(@ref{RFC 822}). It is not Internet standard, but a lot of netnews
+excepting Usenet uses it.
@cindex{USENET}@cindex{RFC 1036}
@noindent
-@node RFC 1153, RFC 1521, RFC 1036, Glossary
+@node RFC 1153, RFC 1557, RFC 1036, Glossary
@subsection RFC 1153
-\e$BJ#?t$N\e(B Internet mail (@ref{RFC 822}) \e$B$r\e(B
-@cindex{encapsulation}@strong{encapsulation} (@ref{encapsulation}) \e$B$9$k\e(B
-\e$B$?$a$NJ}K!$rDj$a$?\e(B RFC. RFC 934 (@ref{RFC 934}) \e$B$rMQ$$$k!#\e(B@refill
-
-MIME (@ref{MIME}) \e$B$HL7=b$9$k$N$G!"8=:_$G$O\e(B message/rfc822
-(@ref{message/rfc822}) \e$B$rMQ$$$?\e(B multipart (@ref{multipart}) \e$B$rMQ$$$k$Y$-\e(B
-\e$B$G$"$k!#\e(B@refill
-
-(cf. @ref{multipart/digest})
-
-
@cindex{RFC 1153}
@noindent
[RFC 1153]
-@node RFC 1521, RFC 1557, RFC 1153, Glossary
-@subsection RFC 1521
-
-MIME (@ref{MIME}) \e$B$rDj5A$7$F$$$k\e(B RFC \e$B$N#1$D!#\e(B
-
-@cindex{Standards Track}@cindex{RFC 1521}
-@noindent
-[RFC 1521]
-@quotation
-N. Borenstein and N. Freed, ``MIME (Multipurpose Internet Mail
-Extensions) Part One: Mechanisms for Specifying and Describing the
-Format of Internet Message Bodies'', September 1993, Standards Track
-(obsolete RFC 1341).
-@end quotation
-
-
-(RFC 1522 (@ref{encoded-word}))
-
-
-@node RFC 1557, RFC 1922, RFC 1521, Glossary
+@node RFC 1557, RFC 1922, RFC 1153, Glossary
@subsection RFC 1557
-euc-kr (@ref{euc-kr}) \e$B$H\e(B iso-2022-kr (@ref{iso-2022-kr}) \e$B$H$$$&4Z9q8l$N\e(B
-\e$B$?$a$N\e(B MIME charset (@ref{MIME charset}) \e$B$rDj5A$7$F$$$k\e(B RFC.
+A RFC defines MIME charset (@ref{MIME charset})s for Korean, euc-kr
+(@ref{euc-kr}) and iso-2022-kr (@ref{iso-2022-kr}).
@cindex{Informational}@cindex{RFC 1557}
@noindent
-@node RFC 1922, plain text, RFC 1557, Glossary
+@node RFC 1922, RFC 2045, RFC 1557, Glossary
@subsection RFC 1922
+A RFC defines MIME charset (@ref{MIME charset})s for Chinese,
iso-2022-cn (@ref{iso-2022-cn}), iso-2022-cn-ext
-(@ref{iso-2022-cn-ext}), cn-gb (@ref{cn-gb}), cn-big5 (@ref{cn-big5}) \e$B$H\e(B
-\e$B$$$C$?Cf9q8l$N$?$a$N\e(B MIME charset (@ref{MIME charset}) \e$B$rDj5A$7$F$$$k\e(B
-RFC.@refill
+(@ref{iso-2022-cn-ext}), cn-gb (@ref{cn-gb}), cn-big5 (@ref{cn-big5}),
+etc.@refill
-\e$B$3$l$K2C$($F!"\e(B@cindex{charset-edition}@strong{charset-edition} \e$B$H\e(B
-@cindex{charset-extension}@strong{charset-extension} \e$B$H$$$&\e(B Content-Type
-field (@ref{Content-Type field}) \e$B$N\e(B parameter \e$B$rDj5A$7$F$$$k!#\e(B
+In addition, it defines additional parameters of Content-Type field
+(@ref{Content-Type field}) field,
+@cindex{charset-edition}@strong{charset-edition} and
+@cindex{charset-extension}@strong{charset-extension}.
@cindex{Informational}@cindex{RFC 1922}
@noindent
-@node plain text, Security multipart, RFC 1922, Glossary
+@node RFC 2045, RFC 2046, RFC 1922, Glossary
+@subsection RFC 2045
+
+@cindex{Standards Track}@cindex{RFC 2045}
+@noindent
+[RFC 2045]
+@quotation
+N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
+(MIME) Part One: Format of Internet Message Bodies'', November 1996,
+Standards Track (obsolete RFC 1521, 1522, 1590).
+@end quotation
+
+
+
+@node RFC 2046, RFC 2048, RFC 2045, Glossary
+@subsection RFC 2046
+
+@cindex{Standards Track}@cindex{RFC 2046}
+@noindent
+[RFC 2046]
+@quotation
+N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
+(MIME) Part Two: Media Types'', November 1996, Standards Track (obsolete
+RFC 1521, 1522, 1590).
+@end quotation
+
+
+
+@node RFC 2048, RFC 2049, RFC 2046, Glossary
+@subsection RFC 2048
+
+@cindex{Standards Track}@cindex{RFC 2048}
+@noindent
+[RFC 2048]
+@quotation
+N. Freed, J. Klensin and J. Postel, ``Multipurpose Internet Mail
+Extensions (MIME) Part Four: Registration Procedures'', November 1996,
+Standards Track (obsolete RFC 1521, 1522, 1590).
+@end quotation
+
+
+
+@node RFC 2049, plain text, RFC 2048, Glossary
+@subsection RFC 2049
+
+@cindex{Standards Track}@cindex{RFC 2049}
+@noindent
+[RFC 2049]
+@quotation
+N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
+(MIME) Part Five: Conformance Criteria and Examples'', November 1996,
+Standards Track (obsolete RFC 1521, 1522, 1590).
+@end quotation
+
+
+
+@node plain text, Security multipart, RFC 2049, Glossary
@subsection plain text
-\e$B=qBN$dAHHG$K4X$9$k>pJs$r;}$?$J$$\e(B \e$BJ8;zId9f\e(B(@ref{Coded character set})\e$B$N$_\e(B
-\e$B$GI=8=$5$l$k\e(B text \e$B>pJs!#\e(B(cf. @ref{text/plain})
+A textual data represented by only coded character set (@ref{coded
+character set}). It does not have information about font or
+typesetting. (cf. @ref{text/plain})
@node Security multipart, text/enriched, plain text, Glossary
@subsection Security multipart
-MIME (@ref{MIME}) \e$B$G0E9f$dEE;R=qL>$rMQ$$$k$?$a$N7A<0!#\e(B
+A format to represent signed/encrypted message in MIME
+(@ref{MIME}).@refill
+
+It defines two multipart media types,
@cindex{multipart/signed}@strong{multipart/signed}
-(@ref{multipart/signed}) \e$B$H\e(B
+(@ref{multipart/signed}) and
@cindex{multipart/encrypted}@strong{multipart/encrypted}
-(@ref{multipart/encrypted}) \e$B$H$$$&\e(B multipart \e$B$rMQ$$$k!#\e(BMOSS \e$B$d\e(B PGP/MIME
-(@ref{PGP/MIME}) \e$B$O$3$l$K4p$$$F$$$k!#\e(B
+(@ref{multipart/encrypted}).@refill
+
+MOSS and PGP/MIME (@ref{PGP/MIME}) are based on it.
@cindex{Security multipart}@cindex{Standards Track}@cindex{RFC 1847}
@noindent
@node text/enriched, text/plain, Security multipart, Glossary
@subsection text/enriched
-RFC 1521 (@ref{RFC 1521}) \e$B$GDj5A$5$l$?\e(B
-@cindex{text/richtext}@strong{text/richtext} \e$B$KBe$o$C$F!"=qBN$dAHHG$K4X\e(B
-\e$B$9$k>pJs$r;}$C$?\e(B text\e$B$rI=8=$9$k$?$a$N\e(B content-type (@ref{content-type}).
-
@cindex{text/enriched}@cindex{RFC 1896}
@noindent
[text/enriched: RFC 1896]
@node text/plain, tm-kernel, text/enriched, Glossary
@subsection text/plain
-RFC 1521 (@ref{RFC 1521}) \e$B$GDj5A$5$l$?!"\e(Bplain text (@ref{plain text}) \e$B$r\e(B
-\e$BI=8=$9$k$?$a$N\e(B content-type (@ref{content-type}).@refill
+@cindex{text/plain}@strong{text/plain} is a media type (@ref{media
+type}) for plain text (@ref{plain text}), defined in RFC 2046 (@ref{RFC
+2046}).@refill
+
+The default media type of ``text/plain; charset=us-ascii'' for Internet
+mail describes existing Internet practice. That is, it is the type of
+body defined by RFC 822 (@ref{RFC 822}).@refill
+
+(cf. @ref{MIME charset}) (cf. @ref{us-ascii})
-\e$BHs\e(B MIME message \e$B$J$I$N\e(B content-type \e$B$,Dj5A$5$l$J$$\e(B part \e$B$O\e(B MIME charset
-(@ref{MIME charset}) \e$B$,\e(B us-ascii (@ref{us-ascii}) \e$B$G$"$k\e(B
-@cindex{text/plain}@strong{text/plain} \e$B$N\e(B part \e$B$G$"$k$H8+Pv$5$l$k$3$H$K\e(B
-\e$B$J$C$F$$$k!#\e(B
@node tm-kernel, tm-MUA, text/plain, Glossary
@subsection tm-kernel, tm
-Emacs \e$B$G\e(B MIME (@ref{MIME}) \e$B$rMxMQ$9$k$?$a$N\e(B user interface \e$B$rDs6!$9$k\e(B
-library \e$B72!#\e(B`tools for MIME' \e$B$NN,!#\e(B
+A libraries to provide user interface about MIME (@ref{MIME}) for emacs.
+tm stands for `tools for MIME'.
@noindent
-@strong{[\e$B$I$&$G$bNI$$$3$H\e(B(^-^;]}
+@strong{[Unimportant notice(^-^;]}
@quotation
@itemize @bullet
@item
- tm \e$B$O\e(B ``tiny-mime'' \e$B$NN,$8$c$J$$$i$7$$$>\e(B (^-^;
+ tm may not stand for ``tiny-mime''(^-^;
@item
- tm \e$B$O:n<T$N%$%K%7%c%k$8$c$J$$$i$7$$$>\e(B (^-^;
+ tm may not stand for initial of an author (^-^;
@item
- ``Tools for MIME'' \e$B$NN,$H$$$&$N$O$3$8$D$1$i$7$$$>\e(B (^-^;
+ ``Tools for MIME'' may be strained (^-^;
@end itemize
@end quotation
@node tm-MUA, us-ascii, tm-kernel, Glossary
@subsection tm-MUA
-tm (@ref{tm-kernel}) \e$B$rMQ$$$?\e(B MUA (@ref{MUA}) \e$B$b$7$/$O\e(B MUA \e$B$KBP$9$k\e(B
-extender.@refill
+MUA (@ref{MUA}) or MUA extender using tm (@ref{tm-kernel}).@refill
-@cindex{tm \e$BBg@9$j\e(B package}@strong{tm \e$BBg@9$j\e(B package} \e$B$K$O\e(B
+@cindex{tm oomori package}@strong{tm oomori package} has following extenders:
@itemize @bullet
@item
-mh-e (@ref{(mh-e)}) \e$BMQ$N\e(B @cindex{tm-mh-e}@strong{tm-mh-e}
+@cindex{tm-mh-e}@strong{tm-mh-e} (@ref{(tm-mh-e-en)})
+ for mh-e (@ref{(mh-e)})
@item
-GNUS \e$BMQ$N\e(B @cindex{tm-gnus}@strong{tm-gnus}
+@cindex{tm-gnus}@strong{tm-gnus} (@ref{(tm-gnus_en)}) for GNUS
@item
-Gnus \e$BMQ$N\e(B @cindex{gnus-mime}@strong{gnus-mime} (@ref{(gnus-mime-en)})
+@cindex{gnus-mime}@strong{gnus-mime} (@ref{(gnus-mime-en)}) for Gnus
@item
-VM \e$BMQ$N\e(B @cindex{tm-vm}@strong{tm-vm}
+@cindex{tm-vm}@strong{tm-vm} (@ref{(tm-vm_en)}) for VM
@item
-RMAIL \e$BMQ$N\e(B @cindex{tm-rmail}@strong{tm-rmail}
+@cindex{tm-rmail}@strong{tm-rmail} for RMAIL
@end itemize
-@noindent
-\e$B$,4^$^$l$F$$$k!#\e(B
-
-\e$BFHN)$7$?\e(B MUA \e$B$H$7$F$O\e(B cmail (@ref{(cmail)}) \e$B$,\e(B tm \e$B$rMxMQ2DG=$G$"$k!#\e(B
@node us-ascii, , tm-MUA, Glossary
@subsection us-ascii
-\e$B%"%a%j%+O"K.$J$I$G;H$o$l$k1Q8l$J$I$rI=8=$9$k$?$a$N\e(B MIME charset
-(@ref{MIME charset}) \e$B$N#1$D!#\e(B@refill
+A MIME charset (@ref{MIME charset}) for primary Latin script mainly
+written by English or other languages.@refill
-ASCII (@ref{ASCII}) \e$B$N$_$+$i$J$j\e(B ISO 2022 (@ref{ISO 2022}) \e$B$K$h$kId9f3H\e(B
-\e$BD%\e(B (@ref{Code extension})\e$B$O5v$5$l$J$$!#\e(B@refill
+It is a 7bit coded character set (@ref{coded character set}) based on
+ISO 2022 (@ref{ISO 2022}), it contains only ASCII (@ref{ASCII}) and code
+extension (@ref{code extension}) is not allowed.@refill
-Internet mail \e$B$K$*$1$kI8=`$NId9f2=J8;z=89g\e(B(@ref{Coded character set})\e$B$G\e(B
-\e$B$"$j!"L@<(E*$K\e(B MIME charset \e$B$,<($5$l$J$$>l9g$O86B'$H$7$F\e(B
-@cindex{us-ascii}@strong{us-ascii} \e$B$,;H$o$l$k!#\e(B@refill
+It is standard coded character set of Internet mail. If MIME charset is
+not specified, @cindex{us-ascii}@strong{us-ascii} is used as
+default.@refill
-\e$B$^$?!"\e(BRFC 822 (@ref{RFC 822}) \e$B$K$*$1$k\e(B @cindex{ASCII}@strong{ASCII} \e$B$O\e(B
-us-ascii
\e$B$r;X$9$b$N$H2r<a$9$Y$-$G$"$k!#
\e(B
+In addition, @cindex{ASCII}@strong{ASCII} of RFC 822 (@ref{RFC 822})
+should be interpreted as us-ascii.
@node Setting, Bug report, Introduction, Top
@itemize @bullet
@item
- \e$BF|K\8l\e(B <tm-ja-admin@@chamonix.jaist.ac.jp>
+ Japanese <tm-ja-admin@@chamonix.jaist.ac.jp>
@item
- \e$B1Q8l\e(B <tm-en-admin@@chamonix.jaist.ac.jp>
+ English <tm-en-admin@@chamonix.jaist.ac.jp>
@end itemize
@noindent
projects / elisp / tm.git / blobdiff