<!doctype sinfo system>
-<!-- $Id: tm-ja.sgml,v 6.1 1996/10/21 02:32:00 morioka Exp $ -->
+<!-- $Id: tm-en.sgml,v 1.2 1996/12/23 21:17:11 morioka Exp $ -->
<head>
-<title>tm 7.90 Manual (English Version)
+<title>tm 7.98 Manual (English Version)
<author>MORIOKA Tomohiko <mail>morioka@jaist.ac.jp</mail>
-<date>1996/10/15
+<date>1996/12/24
<toc>
</head>
<p>
The tm package is a set of modules to enjoy MIME on GNU Emacs. Using
tm, you can
-
+<p>
<ul>
<li> playback or view the MIME messages using tm-view
<li> compose MIME message using tm-edit
<h3> ASCII
<node> ASCII
<p>
-\e$B%"%a%j%+O"K.$G;H$o$l$kJ8;z$rId9f2=$7$?\e(B <dref>94-character set</dref>.
-A-Z, a-z
\e$B$N
\e(B Latin
\e$BJ8;z$H?t;z!"4v$D$+$N5-9f$+$i$J$k!#
\e(B<a node="ISO
-646">ISO 646</a> \e$B$N0l$D!#\e(B
+<concept>ASCII</concept> is a <dref>94-character set</dref> 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 <a
+node="ISO 646">ISO 646</a>.
<standard abbrev="ASCII" title-en="Coded Character Set -- 7-Bit
American Standard Code for Information Interchange"
<h3> binary
<node> binary
<p>
-\e$BG$0U$N\e(B byte \e$BNs$r\e(B <concept>binary</concept> \e$B$H8F$V$3$H$K$7$^$9!#\e(B
-<p>
-<a node="8bit">8bit</a> \e$B$H0[$J$k$N$O\e(B data \e$B$K9T$N9=B$$r2>Dj$7$J$$$3$H$G\e(B
-\e$B$9!#\e(B
-<p>
-\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$V$3$H$K$7$^$9!#\e(B
+Any byte stream is called <concept>binary</concept>.
<p>
-
\e$B$A$J$_$K!"
\e(B<a node="7bit">7bit</a>
\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=$G$-$^$9!#$h$C$F!"\e(B<concept>binary data</concept> \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
-
-
-<h3> Graphic Character Set
-<node> graphic character set
+It does not require structureof lines. It differs from from <a
+node="8bit">8bit</a>.
<p>
-<dref>Coded character set</dref> for graphic characters.
+In addition, if line structured data contain too long line (more than
+998 bytes), it is regarded as binary.
<h3> cn-gb, gb2312
<node> cn-gb
<p>
-
\e$BCf9qBgN&$G$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N
\e(B <a
-node="MIME charset">MIME charset</a> \e$B$N#1$D!#\e(B
+A <a node="MIME charset">MIME charset</a> for simplified Chinese
+mainly used in the Chinese mainland.
<p>
-<dref>ISO 2022</dref> \e$B$K4p$$$F\e(B <dref>ASCII</dref> \e$B$K\e(B <dref>GB
-2312</dref>
\e$B$r
\e(B <dref>8bit</dref>
\e$B$G
\e(B<a node="Code extension">
\e$BId9f
\e(B
-\e$B3HD%\e(B</a>\e$B$7$F$$$k!#\e(B
+It is a <dref>8bit</dref> <dref>coded character set</dref> based on
+<dref>ISO 2022</dref>. It extends <dref>ASCII</dref> to combine
+<dref>GB 2312</dref>.
<p>
-<a node="RFC 1922">RFC 1922</a> \e$B$GDj5A$5$l$F$$$k!#\e(B
+It is defined in <a node="RFC 1922">RFC 1922</a>.
<h3> cn-big5, big5
<node> cn-big5
<p>
-\e$BBfOQ$d9a9A$GMQ$$$i$l$F$$$k<g$KHKBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N\e(B
-<a node="MIME charset">MIME charset</a> \e$B$N#1$D!#\e(B
+A <a node="MIME charset">MIME charset</a> for traditional Chinese
+mainly used in Taiwan and Hon Kong.
+<p>
+It is a <dref>8bit</dref> <dref>coded character set</dref> not based
+on <dref>ISO 2022</dref>. It is a de-fact standard.
<p>
-<dref>ISO 2022</dref> \e$B$K4p$+$J$$\e(B <dref>8bit</dref> \e$B$N\e(B
-<dref>coded character set</dref>\e$B$G\e(B de-fact standard \e$B$G\e(B
-
\e$B$"$k!#
\e(B<a node="RFC 1922">RFC 1922</a>
\e$B$GDj5A$5$l$F$$$k!#
\e(B
+It is defined in <a node="RFC 1922">RFC 1922</a>.
<p>
cf. <report abbrev="BIG5" author="Institute for Information Industry"
title-en="Chinese Coded Character Set in Computer"
date="March 1984">
<p>
-<a node="CNS">CNS 11643-1986</a> \e$B$HBP1~4X78$,$"$k!#\e(B
+It corresponds to <dref>CNS 11643</dref>.
<h3> CNS 11643-1992
-<node> CNS
+<node> CNS 11643
<p>
-\e$BBfOQ$d9a9A$GMQ$$$i$l$F$$$k<g$KHKBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N\e(B
-<a node="Character set">
\e$BJ8;z=89g
\e(B</a>
\e$B!#BfOQ$NI8=`!#8=:_!"
\e(B<a node="94x94
-character set">94\e$B!_\e(B94</a> \e$B$NLL$,Bh#1LL$+$iBh#7LL$^$G$"$k!#\e(B
+<dref>Graphic character set</dref>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 <dref>94x94
+character set</dref>.
<p>
-<dref>ISO 2022</dref> \e$B$G$N=*C<J8;z$O!"Bh#1LL$,\e(B `G', \e$BBh#2LL$,\e(B
-`H', \e$BBh#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$"$k!#\e(B
+Final byte of <dref>ISO 2022</dref> are following:
+
+<dl>
+<dt>plane 1<dd>04/07 (`G')
+<dt>plane 2<dd>04/08 (`H')
+<dt>plane 3<dd>04/09 (`I')
+<dt>plane 4<dd>04/10 (`J')
+<dt>plane 5<dd>04/11 (`K')
+<dt>plane 6<dd>04/12 (`L')
+<dt>plane 7<dd>04/13 (`M')
+</dl>
<standard abbrev="CNS 11643-1992" title-en="Standard Interchange Code
for Generally-Used Chinese Characters" number="CNS
<h3> Content-Disposition field
<node> Content-Disposition
<p>
-Content
\e$B$NI=<($N;EJ}$d
\e(B file
\e$BL>$rI=8=$9$k$?$a$N
\e(B field. <a
-node="MIME">MIME</a> \e$B$N3HD%$N#1$D!#\e(B
+A field to specify presentation of entity or file name. It is an
+extension for <dref>MIME</dref>.
<p>
<rfc number="1806" type="Experimental" author="E R. Troost and
S. Dorner" title="Communicating Presentation Information
date="June 1995">
-<h3> media type
-<node> media type
-<p>
-<concept>media type</concept> specifies the nature of the data in the
-body of <dref>MIME</dref> <dref>entity</dref>. It consists of
-<concept>type</> and <concept>subtype</concept>. It is defined in
-<dref>RFC 2046</dref>.
-<p>
-Currently there are following types:
-
-<ul>
-<li><concept>text</concept>
-</li>
-<li><concept>image</concept>
-</li>
-<li><concept>audio</concept>
-</li>
-<li><concept>video</concept>
-</li>
-<li><concept>application</concept>
-</li>
-<li><a node="multipart"><concept>multipart</concept></a>
-</li>
-<li><concept>message</concept>
-</ul>
-
-<p>
-And there are various subtypes, for example, application/octet-stream,
-audio/basic, image/jpeg, <dref>multipart/mixed</dref>,
-<dref>text/plain</dref>, video/mpeg...
-<p>
-You can refer registered media types at <a
-href="ftp://ftp.isi.edu/in-notes/iana/assignments/media-types">MEDIA
-TYPES</a>.
-<p>
-In addition, you can use private type or subtype using
-<concept>x-token</concept>, which as the prefix `x-'. However you can
-not use them in public.
-<p>
-<cf node="Content-Type field">
-
-
<h3> Content-Type field
<node> Content-Type field
<p>
<h3> Emacs
<node> Emacs
<p>
-\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.
<h3> encoded-word
<h3> encapsulation
<node> encapsulation
<p>
-<a node="RFC 822">Internet mail</a> \e$B$rB>$N5-;v$K$^$k$4$HF~$l$kJ}K!!#\e(B
+Method to insert whole <a node="RFC 822">Internet message</a> into
+another Internet message.
<p>
-\e$BNc$($P!"5-;v$rE>Aw$7$?$j$9$k$N$KMQ$$$k!#\e(B
+For example, it is used to forward a message.
<p>
<cf node="message/rfc822">
<h3> euc-kr
<node> euc-kr
<p>
-
\e$B4Z9q8l$rI=8=$9$k$?$a$N
\e(B <a node="MIME charset">MIME charset</a>
\e$B$N#1$D!#
\e(B
+A <dref>MIME charset</dref> for Korean.
<p>
-<dref>ISO 2022</dref> \e$B$K4p$$$F\e(B <dref>ASCII</dref> \e$B$K\e(B
-<a node="KS C5601">KS C5601</a>
\e$B$r
\e(B <dref>8bit</dref>
\e$B$G
\e(B<a
-node="Code extension">\e$BId9f3HD%\e(B</a>\e$B$7$F$$$k!#\e(B
+It is a <dref>8bit</dref> <dref>coded character set</dref> based on
+<dref>ISO 2022</dref>. It extends <dref>ASCII</dref> to combine
+<dref>KS C5601</dref>.
<p>
-<a node="RFC 1557">RFC 1557</a> \e$B$GDj5A$5$l$F$$$k!#\e(B
+It is defined in <dref>RFC 1557</dref>.
<p>
cf. <standard abbrev="euc-kr" org="Korea Industrial Standards
Association" title-en="Hangul Unix Environment"
<h3> FTP <node> FTP
<p>
-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\e(B
-\e$B$F$$$k!#\e(B
-<p>
<rfc name="FTP" number="959" type="STD 9" author="Postel, J. and
J. Reynolds" title="File Transfer Protocol"
date="October 1985">
<h3> GB 2312-1980
<node> GB 2312
<p>
-\e$BCf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=$9$?$a$N\e(B
-<dref>94x94-character set</dref>
\e$B!#Cf9q$N9q2HI8=`!#
\e(B<a node="ISO
-2022">ISO 2022</a> \e$B$G$N=*C<J8;z$O\e(B `A'.
+A <dref>94x94 character set</dref> for Chinese mainly written by
+simplified Chinese mainly used in the Chinese mainland. It is a
+standard of China.
<p>
-\e$B$3$l$O\e(B GB \e$B$K$*$1$k4pK\=8$G$"$k!#\e(B
+Final byte of <dref>ISO 2022</dref> is 04/01 (`A').
<standard abbrev="GB 2312"
- title-cn="\e$B?.B)8r49MQ4A;zJTb{;zId=8\e(B -- \e$B4pK\=8\e(B"
title-en="Code of Chinese Graphic Character Set for
Information Interchange - Primary Set" number="GB 2312"
year="1980">
<h3> GB 8565.2-1988
<node> GB 8565.2
<p>
-
\e$BCf9q8l$N$?$a$NJd=u
\e(B<a node="Character set">
\e$BJ8;z=89g
\e(B</a>
\e$B!#Cf9q$N9q2HI8=`!#
\e(B
-<a node="GB 2312">GB 2312</a> \e$B$N6u$-ItJ,$KJd=<$9$k$h$&$KDj5A$5$l$?$i$7\e(B
-\e$B$$!#\e(B
+A <dref>94x94 character set</dref> for Chinese as supplement to
+<dref>GB 2312</dref>. It is a standard of China.
<standard abbrev="GB 8565.2" title-en="Information Processing - Coded
Character Sets for Text Communication - Part 2: Graphic
year="1988">
+<h3> Graphic Character Set
+<node> graphic character set
+<p>
+<dref>Coded character set</dref> for graphic characters.
+
+
<h3> hz-gb2312
<node> hz-gb2312
<p>
-
\e$BCf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N
\e(B <a
-node="MIME charset">MIME charset</a> \e$B$N#1$D!#\e(B
+A <a node="MIME charset">MIME charset</a> for simplified Chinese
+mainly used in the Chinese mainland.
<p>
-<dref>ASCII</dref>
\e$B$K
\e(B <a node="GB 2312">GB 2312</a>
\e$B$r
\e(B 7bit
\e$B$G
\e(B
-<a node="Code extension">\e$BId9f3HD%\e(B</a>\e$B$7$?$b$N$r\e(B ASCII printable \e$B$K$J$k\e(B
-\e$B$h$&$K9)IW$7$F$$$k!#\e(B
+It extends <dref>ASCII</dref> to combine <dref>GB 2312</dref>, its
+technique is like <dref>iso-2022-jp</dref>, but it is designed to be
+ASCII printable to use special form for ESC sequence to designate GB
+2312 to G0.
<p>
-RFC 1842, 1843 \e$B$GDj5A$5$l$F$$$k!#\e(B
+It is defined in RFC 1842 and 1843.
<rfc number="1842" type="Informational" author="Y. Wei, Y. Zhang,
J. Li, J. Ding and Y. Jiang" title="ASCII Printable
<h3> ISO 2022
<node> ISO 2022
<p>
-<a node="Code extension">\e$BId9f3HD%\e(B</a>\e$B$N$?$a$N9q:]I8=`!#\e(B
-<p>
-
\e$B$3$l$rMQ$$$FJ#?t$N
\e(B<a node="Character set">
\e$BJ8;z=89g
\e(B</a>
\e$B$rAH9g$;$F
\e(B <a
-node="7bit">7bit</a>
\e$B$J$$$7
\e(B <dref>8bit</dref>
\e$B$N
\e(B <a node="Coded
-character set">\e$BId9f2=J8;z=89g\e(B</a> \e$B$r:n$k$3$H$,$G$-$k!#\e(B
+It is a standard for character code structure and <dref>code
+extension</dref> technique.
<standard abbrev="ISO 2022" org="International Organization for
Standardization (ISO)" title-en="Information Processing:
<h3> iso-2022-cn
<node> iso-2022-cn
<p>
-
\e$BCf9q8l$rI=8=$9$k$?$a$N
\e(B <a node="MIME charset">MIME charset</a>
\e$B$N#1$D!#
\e(B
+A <dref>MIME charset</dref> for Chinese.
<p>
-<dref>ISO 2022</dref> \e$B$K4p$$$F\e(B <dref>ASCII</dref> \e$B$K\e(B
-<a node="GB 2312">GB 2312</a>, <a node="CNS">CNS 11643 plain 1, plain
-2</a>
\e$B$r
\e(B <a node="7bit">7bit</a>
\e$B$G
\e(B<a node="Code extension">
\e$BId9f3HD%
\e(B
-</a>\e$B$7$F$$$k!#\e(B
+It is a <dref>7bit</dref> <dref>coded character set</dref> based on
+<dref>ISO 2022</dref>. It extends <dref>ASCII</dref> to combine
+<dref>GB 2312</dref> and/or <a node="CNS 11643">CNS 11643 plain 1,
+plain 2</a>.
<p>
-<a node="RFC 1922">RFC 1922</a> \e$B$GDj5A$5$l$F$$$k!#\e(B
+It is defined in <dref>RFC 1922</dref>.
<h3> iso-2022-cn-ext
<node> iso-2022-cn-ext
<p>
-
\e$BCf9q8l$rI=8=$9$k$?$a$N
\e(B <a node="MIME charset">MIME charset</a>
\e$B$N#1$D!#
\e(B
+A <dref>MIME charset</dref> for Chinese.
<p>
-<dref>ISO 2022</dref> \e$B$K4p$$$F\e(B <dref>ASCII</dref> \e$B$K\e(B
-<a node="GB 2312">GB 2312</a>, <a node="CNS">CNS 11643 plain 1
-.. 7</a>, <a node="ISO-IR-165">ISO-IR-165</a>
\e$BEy$r
\e(B <a
-node="7bit">7bit</a>
\e$B$G
\e(B<a node="Code extension">
\e$BId9f3HD%
\e(B</a>
\e$B$7$F$$$k!#
\e(B
+It is a <dref>7bit</dref> <dref>coded character set</dref> based on
+<dref>ISO 2022</dref>. It extends <dref>ASCII</dref> to combine
+<dref>GB 2312</dref>, <a node="CNS 11643">CNS 11643 plain 1 .. 7</a>,
+<dref>ISO-IR-165</dref> and other Chinese graphic character sets.
<p>
-<a node="RFC 1922">RFC 1922</a> \e$B$GDj5A$5$l$F$$$k!#\e(B
+It is defined in <dref>RFC 1922</dref>.
<p>
<memo>
-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.
<p>
-Emacs/mule \e$B$G$OMxMQ2DG=$G$"$k!#\e(B
+Emacs/mule can use it.
</memo>
<h3> iso-2022-jp
<node> iso-2022-jp
<p>
-
\e$BF|K\8l$rI=8=$9$k$?$a$N
\e(B <a node="MIME charset">MIME charset</a>
\e$B$N0l$D!#
\e(B
+A <dref>MIME charset</dref> for Japanese.
<p>
-
\e$B8E$$
\e(B <dref>ISO 2022</dref>
\e$B$K4p$$$F
\e(B <a
-node="ASCII">ASCII</a>, JIS X0201-Latin, <a node="JIS C6226-1978">JIS
-X0208-1978</a>, <a node="JIS X0208">JIS X0208-1983</a>
\e$B$r@Z$jBX$($k
\e(B <a
-node="7bit">7bit</a> \e$BJ8;zId9f!#\e(B
+It is a <dref>7bit</dref> <dref>coded character set</dref> based on
+old <dref>ISO 2022</dref>. It switches <dref>ASCII</dref>, JIS
+X0201-Latin, <a node="JIS C6226-1978">JIS X0208-1978</a> and <a
+node="JIS X0208">JIS X0208-1983</a>.
<p>
-RFC 1468 \e$B$GDj5A$5$l$F$$$k!#\e(B
+It is defined in RFC 1468.
<p>
<memo>
-JIS X0208-1996? \e$B$G$O\e(B <dref>ISO 2022</dref> \e$B$HFHN)$KDj5A$5$l\e(B
-\e$B$kM=Dj!#\e(B
+JIS X0208-1997? will define it in annex as non-<dref>ISO 2022</dref>
+encoding.
</memo>
<rfc name="iso-2022-jp" number="1468" author="Murai J., M. Crispin,
script).
<p>
It is based on <dref>ISO 2022</dref> <dref>code extension</dref>
-technique to extends <dref>ASCII</dref> to use <dref>KS C5601</dref>
-as <dref>7bit</dref> text.
+technique to extend <dref>ASCII</dref> to use <dref>KS C5601</dref> as
+<dref>7bit</dref> text.
<p>
It is defined in <dref>RFC 1557</dref>.
<h3> ISO 646
<node> ISO 646
<p>
-
\e$B3F9q$G6&DL$K;H$($k:G>.8BEY$N
\e(B<a node="Character set">
\e$BJ8;z=89g
\e(B</a>
\e$B$rDj$a
\e(B
-
\e$B$?$b$N!#
\e(B<a node="94 character set">94
\e$BJ8;z=89g
\e(B</a>
\e$B$N#1$D!#
\e(BISO 646 IRV
-\e$B!J9q:]4p=`HG!K$r85$K4v$D$+$NJ8;z$O3F9q$G0c$&J8;z$r3dEv$k$3$H$r5v$7$F$$\e(B
-\e$B$F!"4v$D$+$NJQ<o$,B8:_$9$k!#\e(B<dref>ASCII</dref> \e$B$d\e(B JIS
-X0201-Latin \e$B$O$=$N0l<o!#\e(B
-
<standard abbrev="ISO 646" org="International Organization for
Standardization (ISO)" title-en="Information technology:
ISO 7-bit coded character set for information
<concept>iso-8859-1</concept> is a <dref>MIME charset</dref> for
west-European languages written by Latin script.
<p>
-<dref>ISO 2022</dref> \e$B$K4p$$$F!"\e(B<dref>ASCII</dref> \e$B$K\e(B
-<a node="ISO 8859-1">ISO 8859-1</a>
\e$B$r
\e(B <dref>8bit</dref>
\e$B$G
\e(B<a
-node="Code extension">\e$BId9f3HD%\e(B</a>\e$B$7$F$$$k!#\e(B
+It is a <dref>8bit</dref> <dref>coded character set</dref> based on
+<dref>ISO 2022</dref>. It extends <dref>ASCII</dref> to combine
+<dref>ISO 8859-1</dref>.
<p>
It is defined in <dref>RFC 2046</dref>.
<concept>iso-8859-2</concept> is a <dref>MIME charset</dref> for
east-European languages written by Latin script.
<p>
-<dref>ISO 2022</dref> \e$B$K4p$$$F!"\e(B<dref>ASCII</dref> \e$B$K\e(B
-<a node="ISO 8859-2">ISO 8859-2</a>
\e$B$r
\e(B <dref>8bit</dref>
\e$B$G
\e(B<a
-node="Code extension">\e$BId9f3HD%\e(B</a>\e$B$7$F$$$k!#\e(B
+It is a <dref>8bit</dref> <dref>coded character set</dref> based on
+<dref>ISO 2022</dref>. It extends <dref>ASCII</dref> to combine
+<dref>ISO 8859-2</dref>.
<p>
It is defined in <dref>RFC 2046</dref>.
<concept>iso-8859-5</concept> is a <dref>MIME charset</dref> for
Cyrillic script.
<p>
-<dref>ISO 2022</dref> \e$B$K4p$$$F!"\e(B<dref>ASCII</dref> \e$B$K\e(B
-<a node="ISO 8859-5">ISO 8859-5</a>
\e$B$r
\e(B <dref>8bit</dref>
\e$B$G
\e(B<a
-node="Code extension">\e$BId9f3HD%\e(B</a>\e$B$7$F$$$k!#\e(B
+It is a <dref>8bit</dref> <dref>coded character set</dref> based on
+<dref>ISO 2022</dref>. It extends <dref>ASCII</dref> to combine
+<dref>ISO 8859-5</dref>.
<p>
It is defined in <dref>RFC 2046</dref>.
<concept>iso-8859-7</concept> is a <dref>MIME charset</dref> for
Greek script.
<p>
-<dref>ISO 2022</dref> \e$B$K4p$$$F!"\e(B<dref>ASCII</dref> \e$B$K\e(B
-<a node="ISO 8859-7">ISO 8859-7</a>
\e$B$r
\e(B <dref>8bit</dref>
\e$B$G
\e(B<a
-node="Code extension">\e$BId9f3HD%\e(B</a>\e$B$7$F$$$k!#\e(B
+It is a <dref>8bit</dref> <dref>coded character set</dref> based on
+<dref>ISO 2022</dref>. It extends <dref>ASCII</dref> to combine
+<dref>ISO 8859-7</dref>.
<p>
It is defined in RFC 1947.
<h3> ISO-IR-165, CCITT Extended GB <node> ISO-IR-165
<p>
-CCITT \e$B$,EPO?$7$?!"Cf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=\e(B
-\e$B8=$9$k$?$a$N\e(B <dref>94x94-character set</dref>\e$B!#\e(B
+A <dref>94x94-character set</dref> for Chinese mainly written by
+simplified Chinese mainly used in the Chinese mainland registered by
+CCITT.
<p>
-<a node="GB 2312">GB 2312</a>
\e$B$H
\e(B <a node="GB 8865.2">GB 8565
\e$BI=#2
\e(B</a>
-\e$B$K\e(B 150 \e$BJ8;z$[$I$rDI2C$7$?$b$N$i$7$$!#\e(B
+It consists of <dref>GB 2312</dref>, <dref>GB 8865.2</dref> and
+additional 150 characters.
<p>
-<dref>ISO 2022</dref> \e$B$G$N=*C<J8;z$O\e(B `E' \e$B$G$"$k!#\e(B
+Final byte of <dref>ISO 2022</dref> is 04/05 (`E').
<h3> JIS X0201
<node> JIS X0201
<p>
-<a node="ISO 646">ISO 646</a> \e$B$NJQ<o$N#1$D$G$"$k\e(B Latin \e$BJ8;z=89g$H\e(B 1
-byte \e$B$N%+%?%+%JJ8;z=89g$+$i$J$k!#\e(B
+It defines two <dref>94-character set</dref>, for Latin script (a
+variant of <dref>ISO 646</dref>) and Katakana script, and 7bit and
+8bit <dref>coded character set</dref>s.
<p>
-\e$B85$O\e(B <concept>JIS C6220-1976</concept> \e$B$H8@$C$?$,\e(B <concept>JIS
-X0201</concept> \e$B$KHV9f$,JQ99$5$l$?!#\e(B
+It was renamed from <concept>JIS C6220-1976</concept>.
-<standard abbrev="JIS X0201-1976" org="\e$BF|K\5,3J6(2q\e(B (Japanese
- Standards Association)" title-ja="\e$B>pJs8r49MQId9f\e(B"
+<standard abbrev="JIS X0201-1976" org="Japanese Standards Association"
title-en="Code for Information Interchange" number="JIS
X 0201-1976">
-\e$B$^$?!"\e(B1996 \e$BG/$K2~DjHG$,=P$kM=Dj!#\e(B
+In addition, revised version will be published in 1997.
-<standard abbrev="JIS X0201-1996?" org="\e$BF|K\5,3J6(2q\e(B (Japanese
- Standards Association)"
- title-ja="\e$B#7%S%C%H5Z$S#8%S%C%H$N>pJs8r49MQId9f2=J8;z=89g\e(B"
- title-en="7-bit and 8-bit coded character sets for
- information interchange" number="JIS X 0201" year="1996?
- draft">
+<standard abbrev="JIS X0201-1997?" org="Japanese Standards
+ Association" title-en="7-bit and 8-bit coded character
+ sets for information interchange" number="JIS X 0201"
+ year="1997? draft">
<h3> JIS C6226-1978
<node> JIS C6226
<p>
-\e$BF|K\8l$rI=$9$?$a$K:n$i$l$?\e(B <dref>94x94-character set</dref>\e$B!#F|K\$N9q\e(B
-\e$B2HI8=`!#\e(BJIS X0208-1978 \e$B$H$b$$$&!#\e(B
+A <dref>94x94-character set</dref> for Japanese. It was renamed to
+JIS X0208-1978.
<p>
<cf node="JIS X0208">
<h3> JIS X0208
<node> JIS X0208
<p>
-\e$BF|K\8l$rI=$9$?$a$K:n$i$l$?\e(B <dref>94x94-character set</dref>\e$B!#F|K\$N9q\e(B
-\e$B2HI8=`!#\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/\e(B
-\e$BHG$,$b$C$H$bNI$/;H$o$l$F$$$k!#\e(B
+A <dref>94x94-character set</dref> for Japanese. Japanese standard.
+It was published in 1978, and revised in 1983 and 1990. In the
+Internet message, 1983 edition is major.
<p>
-JIS X0208 \e$B$O5-9f!"?t;z!"%m!<%^;z!"$R$i$,$J!"%+%?%+%J!"%.%j%7%cJ8;z!"%-\e(B
-\e$B%j%kJ8;z!"7S@~AG!"Bh#1?e=`!"Bh#2?e=`$N4A;z$,4^$^$l$k!#C"$7!"\e(B1983 \e$BG/HG\e(B
-\e$B$N0lIt$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$G$OJQ99$5$l!"$^$?!"Bh#1?e=`$HBh#2?e=`$,F~$lBX$o$C$F$$$?$j$9\e(B
-\e$B$k!#$3$N$?$a!"\e(B1978 \e$BG/HG$H\e(B 1983 \e$BG/HG$O0[$J$kJ8;z=89g$H$7$F07$o$l$k!#\e(B
+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.
<p>
-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.
-<standard abbrev="JIS X0208-1978" org="\e$BF|K\5,3J6(2q\e(B (Japanese Standards
- Association)" title-ja="\e$B>pJs8r49MQ4A;zId9f7O\e(B"
+<standard abbrev="JIS X0208-1978" org="Japanese Standards Association"
title-en="Code of the Japanese graphic character set for
information interchange" number="JIS C6226" year="1978">
-<standard abbrev="JIS X0208-1983,1990" org="\e$BF|K\5,3J6(2q\e(B (Japanese Standards
- Association)" title-ja="\e$B>pJs8r49MQ4A;zId9f7O\e(B"
- title-en="Code of the Japanese graphic character set for
- information interchange" number="JIS X0208" year="1983,1990">
+<standard abbrev="JIS X0208-1983,1990" org="Japanese Standards
+ Association" title-en="Code of the Japanese graphic
+ character set for information interchange" number="JIS
+ X0208" year="1983,1990">
<p>
-\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)
-<standard abbrev="JIS X0208-1996?" org="\e$BF|K\5,3J6(2q\e(B (Japanese
- Standards Association)" title-ja="\e$B#7%S%C%H5Z$S#8%S%C%H$N\e(B
- \e$B#2%P%$%H>pJs8r49MQId9f2=4A;z=89g\e(B" title-en="7-bit and
- 8-bit double byte coded Kanji sets for information
- interchange" number="JIS X 0208" year="1996? draft">
+<standard abbrev="JIS X0208-1997?" org="Japanese Standards
+ Association" title-en="7-bit and 8-bit double byte coded
+ Kanji sets for information interchange" number="JIS X
+ 0208" year="1997? draft">
<h3> JIS X0212-1990
<node> JIS X0212
<p>
-<a node="JIS X0208">JIS X0208</a> \e$B$K$J$+$C$?J8;z$r=8$a$?\e(B
-<dref>94x94-character set</dref>\e$B!#!VJd=u4A;z!W$H$b8F$P$l$k!#F|K\$N9q2H\e(B
-\e$BI8=`!#\e(B<dref>ISO 2022</dref> \e$B$G$N=*C<J8;z$O\e(B `D'.
+A <dref>94x94 character set</dref> for Japanese as supplement to
+<dref>JIS X0208</dref>. It is a standard of Japan.
+<p>
+Final byte of <dref>ISO 2022</dref> is 04/04 (`D').
<h3> koi8-r
<p>
A <dref>94x94-character set</dref> for Korean language (Hangul
script). Korean Standard. Final byte of <dref>ISO 2022</dref> is
-`C'.
+04/03 (`C').
<standard abbrev="KS C5601" org="Korea Industrial Standards
Association" title-en="Code for Information Interchange
(Hangul and Hanja)" number="KS C 5601" year="1987">
+<h3> media type
+<node> media type
+<p>
+<concept>media type</concept> specifies the nature of the data in the
+body of <dref>MIME</dref> <dref>entity</dref>. It consists of
+<concept>type</concept> and <concept>subtype</concept>. It is defined
+in <dref>RFC 2046</dref>.
+<p>
+Currently there are following types:
+
+<ul>
+<li><concept>text</concept>
+</li>
+<li><concept>image</concept>
+</li>
+<li><concept>audio</concept>
+</li>
+<li><concept>video</concept>
+</li>
+<li><concept>application</concept>
+</li>
+<li><a node="multipart"><concept>multipart</concept></a>
+</li>
+<li><concept>message</concept>
+</ul>
+
+<p>
+And there are various subtypes, for example, application/octet-stream,
+audio/basic, image/jpeg, <dref>multipart/mixed</dref>,
+<dref>text/plain</dref>, video/mpeg...
+<p>
+You can refer registered media types at <a
+href="ftp://ftp.isi.edu/in-notes/iana/assignments/media-types">MEDIA
+TYPES</a>.
+<p>
+In addition, you can use private type or subtype using
+<concept>x-token</concept>, which as the prefix `x-'. However you can
+not use them in public.
+<p>
+<cf node="Content-Type field">
+
+
<h3> message
<node> message
<p>
-\e$B$3$3$G$O\e(B <dref>RFC 822</dref> \e$B$GDj5A$5$l$k\e(B mail \e$B$H\e(B <dref>RFC
-1036</dref> \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 <dref>RFC 822</dref> and
+news message defined in <dref>RFC 1036</dref>.
<h3> message/rfc822
<h3> method
<node> method
<p>
-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 <concept>internal method</concept> \e$B$H\e(B C
-\e$B$d\e(B script \e$B8@8l$J$I$G=q$+$l$?\e(B <concept>external method</concept> \e$B$,$"$k!#\e(B
+Application program of tm-view to process for specified <dref>media
+type</dref> when user plays an entity.
+<p>
+There are two kinds of methods, <concept>internal method</concept> and
+<concept>external method</concept>. Internal method is written by
+Emacs Lisp. External method is written by C or script languages and
+called by asynchronous process call.
<p>
<cf file="tm-view-en" node="method">
<p>
It is defined in <dref>RFC 2045</dref>.
<p>
-<dref>iso-2022-jp</dref>
\e$B$d
\e(B <a node="euc-kr">euc-kr</a>
\e$B$O$=$N#1$D!#
\e(B
-
\e$B!J$3$3$G$O!"
\e(BMIME charset
\e$B$O
\e(B<a node="Character set">
\e$BJ8;z=89g
\e(B</a>
\e$B$H6hJL
\e(B
-\e$B$7$F>.J8;z$G=q$$$F$$$k!K\e(B
+<dref>iso-2022-jp</dref> or <dref>euc-kr</dref> are kinds of it. (In
+this document, MIME charsets are written by small letters to
+distinguish <dref>graphic character set</dref>. For example, ISO
+8859-1 is a graphic character set, and iso-8859-1 is a MIME charset)
<h3> MTA
<node> MTA
<p>
-<concept>Message Transfer Agent</concept> \e$B$NN,$G!"\e(Bsendmail \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
+<concept>Message Transfer Agent</concept>. It means mail transfer
+programs (ex. sendmail) and news servers.
<p>
<cf node="MUA">
<h3> MUA
<node> MUA
<p>
-<concept>Message User Agent</concept> \e$B$NN,$G!"\e(Bmail reader \e$B$H\e(B news
-reader \e$B$NAm>N!#\e(B
+<concept>Message User Agent</concept>. It means mail readers and news
+readers.
<p>
<cf node="MTA">
<h3> MULE
<node> MULE
<p>
-
\e$BH>ED
\e(B
\e$B7u0l;a$i$,:n$C$?!"B?8@8l$5$l$?
\e(B <a node="Emacs">Emacs</a>.
-<p>
-[MULE] Nishikimi M., Handa K. and Tomura S., ``Mule: MULtilingual
-Enhancement to GNU Emacs'', Proc. of INET'93, August, 1993.
+Multilingual extension of GNU <dref>Emacs</dref> by HANDA Ken'ichi et
+al.
+
+<inproc abbrev="MULE" author="Nishikimi M., Handa K. and Tomura S."
+ title-en="Mule: MULtilingual Enhancement to GNU Emacs"
+ book-en="Proc. of INET'93" date="August, 1993">
<p>
-
\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(B<a
-href="ftp://etlport.etl.go.jp/pub/mule/mule-19.33-gamma.taz"> alpha \e$BHG\e(B
-</a> \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 <a
+href="ftp://etlport.etl.go.jp/pub/mule/mule-19.33-delta.taz">alpha
+version of mule merged emacs</a>.
<p>
-\e$B$=$NB>!"\e(BXEmacs \e$B$K\e(B merge \e$B$7$?$b$N$bB8:_$9$k!#\e(B
+In addition, there is XEmacs with mule feature.
<p>
-\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\e(B
-\e$B$K$J$k!#\e(B
+So now, there are 3 kinds of mule variants.
<p>
-\e$B$=$3$G!"$3$3$G$O!"B?8@8l\e(B Emacs \e$B$NAm>N$r\e(B <concept>mule</concept>, \e$B85!9\e(B
-\e$B$N\e(B MULE \e$B$r\e(B <concept>MULE</concept>, mule \e$B5!G=$r\e(B merge \e$B$7$?\e(B Emacs \e$B$r\e(B
-<concept>Emacs/mule</concept>, mule \e$B5!G=$r\e(B merge \e$B$7$?\e(B XEmacs \e$B$r\e(B
-<concept>XEmacs/mule</concept> \e$B$H8F$V$3$H$K$9$k!#\e(B
+In this document, <concept>mule</concept> means any mule variants,
+<concept>MULE</concept> means original MULE (..2.3),
+<concept>Emacs/mule</concept> means mule merged Emacs,
+<concept>XEmacs/mule</concept> means XEmacs with mule feature.
<h3> Multipart
<h3> multipart/encrypted
<node> multipart/encrypted
<p>
-RFC 1847 \e$B$GDj5A$5$l$?\e(B <dref>Security multipart</dref> \e$B$N#1$D$G!"0E9f2=\e(B
-\e$B$5$l$?\e(B message \e$B$rI=8=$9$k$N$KMQ$$$k!#\e(B
+It is a <dref>Security multipart</dref> defined in
+RFC 1847, used to represent encrypted message.
<p>
<cf node="PGP/MIME">
<h3> multipart/signed
<node> multipart/signed
<p>
-RFC 1847 \e$B$GDj5A$5$l$?\e(B <dref>Security multipart</dref> \e$B$N#1$D$G!"EE;R=p\e(B
-\e$BL>$rI=8=$9$k$N$KMQ$$$k!#\e(B
+It is a <dref>Security multipart</dref> defined in
+RFC 1847, used to represent signed message.
<p>
<cf node="PGP/MIME">
<h3> PGP
<node> PGP
<p>
-Phil Zimmermann \e$B;a$,:n@.$7$?8x3+800E9f=hM}7O$N#1$D!#\e(B
-<dref>message</dref> \e$B$N0E9f2=$dEE;R=pL>$r9T$&$3$H$,$G$-$k!#\e(BPretty Good
-Privacy \e$B$NN,!#\e(B
+A public key encryption program by Phil Zimmermann. It provides
+encryption and signature for <dref>message</dref>. PGP stands for
+<concept>Pretty Good Privacy</concept>.
<p>
-\e$BEAE}E*$J\e(B PGP \e$B$G$O\e(B <dref>encapsulation</dref> \e$B$K\e(B <dref>RFC 934</dref>\e$B$K\e(B
-\e$B=`$8$?J}K!$rMQ$$$k!#$3$l$O\e(B <dref>MIME</dref> \e$B$HL7=b$9$k$N$G\e(B
-<dref>PGP/MIME</dref> \e$B$,Ds0F$5$l$F$$$k!#0lJ}!"\e(BMIME \e$B$K$*$$$F\e(B PGP \e$B$N\e(B
-encapsulation \e$B$rMQ$$$kJ}K!\e(B <cf node="PGP-kazu"> \e$B$bMxMQ$5$l$F$-$?!#$7$+\e(B
-\e$B$7!":#8e$O\e(B PGP/MIME \e$B$KE}0l$7$F$$$/J}$,K>$^$7$$!#\e(B
+Traditional PGP uses <dref>RFC 934</dref> <dref>encapsulation</dref>.
+It is conflict with <dref>MIME</dref>. So <dref>PGP/MIME</dref> is
+defined. On the other hand, <dref>PGP-kazu</dref> was proposed to use
+PGP encapsulation in MIME. But it is obsoleted.
<p>
<rfc name="PGP" number="1991" type="Informational" author="D. Atkins,
W. Stallings and P. Zimmermann" title="PGP Message
<h3> PGP-kazu
<node> PGP-kazu
<p>
-
\e$B;3K\
\e(B
\e$BOBI'
\e(B
\e$B;a$,Ds0F$7$?
\e(B <a node="MIME">MIME</a>
\e$B$G
\e(B <a
-node="PGP">PGP</a> \e$B$rMxMQ$9$k$?$a$NJ}K!$r$3$3$G$O\e(B
-<concept>PGP-kazu</concept> \e$B$H8F$V$3$H$K$9$k!#\e(B
+In this document, <concept>PGP-kazu</concept> means a method to use
+traditional PGP encapsulation in <dref>MIME</dref>, proposed by
+YAMAMOTO Kazuhiko.
<p>
-PGP-kazu \e$B$O\e(B <concept>application/pgp</concept> \e$B$H$$$&\e(B
-<dref>content-type</dref> \e$B$rDj5A$9$k!#\e(B
+PGP-kazu defines a <dref>media type</dref>,
+<concept>application/pgp</concept>.
<p>
-application/pgp \e$B$N\e(B part \e$B$G$O\e(B PGP \e$B$N\e(B <dref>encapsulation</dref> \e$B$,MQ$$\e(B
-\e$B$i$l$k!#\e(BPGP \e$B$N\e(B encapsulation <cf node="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$$8B$j!"Cf\e(B
-\e$B$K4^$^$l$?\e(B MIME message \e$B$rFI$`$3$H$,$G$-$J$/$J$k!#B($A!"\e(BPGP-kazu \e$B$KBP\e(B
-\e$B1~$7$F$$$J$$\e(B MIME \e$B$KBP1~$7$?\e(B <dref>MUA</dref> \e$B$O$=$N\e(B part \e$B$,FI$a$J$/$J\e(B
-\e$B$k!#$=$NBe$o$j!"\e(BMIME \e$B$KBP1~$7$F$$$J$$\e(B PGP \e$BBP1~$N\e(B <dref>MUA</dref> \e$B$G$b\e(B
-message \e$B$rFI$`$3$H$,$G$-$k!#\e(B
+In application/pgp entity, PGP <dref>encapsulation</dref> is used.
+PGP encapsulation conflicts with MIME, so it requires PGP-processing
+to read as MIME message.
<p>
-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\e(B
-\e$B$J$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
-\e$B$:!"\e(Bpgp \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
-<p>
-\e$B$^$?!"\e(BInternet \e$B$G$O:#8e\e(B <dref>PGP/MIME</dref> \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
-<p>
-[draft-kazu-pgp-mime-00.txt] Yamamoto K., ``PGP MIME Integration'',
-October, 1995
+It was obsoleted, so you should use <dref>PGP/MIME</dref>. However if
+you want to use traditional PGP message, it might be available.
<h3> PGP/MIME
<node> PGP/MIME
<p>
-Michael Elkins
\e$B;a$,Ds0F$7$?
\e(B <a node="MIME">MIME</a>
\e$B$G
\e(B <a
-node="PGP">PGP</a> \e$B$rMxMQ$9$k$?$a$NJ}K!!#\e(B
+<dref>PGP</dref> and <dref>MIME</dref> integration proposed by Michael
+Elkins.
<p>
-<a node="Security multipart">RFC 1847</a> \e$B$K4p$-!"\e(BMIME \e$B$N\e(B multipart \e$B$K\e(B
-\e$B$h$k\e(B <dref>encapsulation</dref> \e$B$r9T$&!#$3$N$?$a!"\e(BMIME \e$B$N<+A3$J3HD%$K\e(B
-\e$B$J$C$F$$$k!#$7$+$7!"EAE}E*$J\e(B PGP\e$B$H$N8_49@-$,<:$o$l$F$$$k!#\e(B
+It is based on <a node="Security multipart">RFC 1847</a>, 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.
<p>
-PGP/MIME \e$B$G$O\e(B <dref>PGP-kazu</dref> \e$B$H0[$J$j!"\e(BMIME \e$B$N\e(B encapsulation \e$B$N\e(B
-\e$B$_$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
-<p>
-Internet \e$B$G$O:#8e\e(B <dref>PGP/MIME</dref> \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
+<dref>PGP/MIME</dref> will be standard of PGP message.
<rfc name="PGP/MIME" number="2015" type="Standards Track"
author="M. Elkins" title="MIME Security with Pretty Good
<h3> RFC 821
<node> RFC 821
<p>
-<concept>SMTP</concept> \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.
-
<rfc name="SMTP" number="821" type="STD 10" author="J. Postel"
title="Simple Mail Transfer Protocol" date="August
1982">
<h3> RFC 822
<node> RFC 822
<p>
-Internet mail \e$B$N<g$K\e(B <concept>message header</concept> \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 <concept>message
+header</concept>.
<memo>
<p>
-news message \e$B$b$3$l$K=`$8$F$$$k$N$G!"\e(B<concept>Internet mail</concept>
-\e$B$H=q$/$h$j$b!"\e(B<concept>Internet message</concept> \e$B$H=q$$$?J}$,NI$$$+$b\e(B
-\e$B$7$l$J$$!#\e(B
+news message is based on RFC 822, so <concept>Internet
+message</concept> may be more suitable than <concept>Internet
+mail</concept> .
</memo>
<rfc number="822" type="STD 11" author="D. Crocker" title="Standard
<h3> RFC 934
<node> RFC 934
<p>
-<a node="RFC 822">Internet mail</a>
\e$B$N
\e(B <a node="encapsulation">
-<concept>encapsulation</concept></a> \e$B$NJ}K!$rDj$a$?\e(B RFC.
+A RFC defines an <a node="encapsulation">
+<concept>encapsulation</concept></a> method for <a node="RFC
+822">Internet mail</a>.
<p>
-<dref>MIME</dref> \e$B$HL7=b$9$k$N$G!"8=:_$G$O\e(B <dref>message/rfc822</dref>
-\e$B$rMQ$$$k$Y$-$G$"$k!#\e(B
-
+It conflicts with <dref>MIME</dref>, so you should use
+<dref>message/rfc822</dref>.
<rfc number="934" author="Marshall T. Rose and Einar A. Stefferud"
title="Proposed Standard for Message Encapsulation"
<h3> RFC 1036
<node> RFC 1036
<p>
-USENET
\e$B$G$N
\e(B message
\e$B$N7A<0$rDj$a$?
\e(B RFC. <a node="RFC 822">RFC 822</a>
-\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$K=`$8$F$$$k$b$N$,B?$$!#\e(B
+A RFC defines format of USENET message. It is a subset of <dref>RFC
+822</dref>. It is not Internet standard, but a lot of netnews
+excepting Usenet uses it.
<rfc name="USENET" number="1036" author="M. Horton and R. Adams"
title="Standard for Interchange of USENET Messages"
<h3> RFC 1153
<node> RFC 1153
<p>
-
\e$BJ#?t$N
\e(B <a node="RFC 822">Internet mail</a>
\e$B$r
\e(B <a node="encapsulation">
-<concept>encapsulation</concept></a> \e$B$9$k$?$a$NJ}K!$rDj$a$?\e(B
-RFC. <dref>RFC 934</dref> \e$B$rMQ$$$k!#\e(B
-<p>
-<dref>MIME</dref> \e$B$HL7=b$9$k$N$G!"8=:_$G$O\e(B <dref>message/rfc822</dref>
-\e$B$rMQ$$$?\e(B <dref>multipart</dref> \e$B$rMQ$$$k$Y$-$G$"$k!#\e(B
-<p>
-<cf node="multipart/digest">
-
<rfc number="1153" author="F. Wancho" title="Digest Message Format"
date="April 1990">
<h3> RFC 1557
<node> RFC 1557
<p>
-<dref>euc-kr</dref> \e$B$H\e(B <dref>iso-2022-kr</dref> \e$B$H$$$&4Z9q8l$N$?$a$N\e(B
-<a node="MIME charset">MIME charset</a> \e$B$rDj5A$7$F$$$k\e(B RFC.
+A RFC defines <dref>MIME charset</dref>s for Korean,
+<dref>euc-kr</dref> and <dref>iso-2022-kr</dref>.
<rfc number="1557" type="Informational" author="U. Choi, K. Chon and
H. Park" title="Korean Character Encoding for Internet
<h3> RFC 1922
<node> RFC 1922
<p>
+A RFC defines <dref>MIME charset</dref>s for Chinese,
<dref>iso-2022-cn</dref>, <dref>iso-2022-cn-ext</dref>,
-<dref>cn-gb</dref>, <dref>cn-big5</dref>
\e$B$H$$$C$?Cf9q8l$N$?$a$N
\e(B <a
-node="MIME charset">MIME charset</a> \e$B$rDj5A$7$F$$$k\e(B RFC.
+<dref>cn-gb</dref>, <dref>cn-big5</dref>, etc.
<p>
-\e$B$3$l$K2C$($F!"\e(B<concept>charset-edition</concept> \e$B$H\e(B
-<concept>charset-extension</concept> \e$B$H$$$&\e(B <dref>Content-Type
-field</dref> \e$B$N\e(B parameter \e$B$rDj5A$7$F$$$k!#\e(B
+In addition, it defines additional parameters of <dref>Content-Type
+field</dref> field, <concept>charset-edition</concept> and
+<concept>charset-extension</concept>.
<rfc number="1922" type="Informational" author="Zhu, HF., Hu, DY.,
Wang, ZG., Kao, TC., Chang, WCH. and Crispin, M."
<h3> plain text
<node> plain text
<p>
-
\e$B=qBN$dAHHG$K4X$9$k>pJs$r;}$?$J$$
\e(B <a node="Coded character set">
\e$BJ8;zId
\e(B
-\e$B9f\e(B</a>\e$B$N$_$GI=8=$5$l$k\e(B text \e$B>pJs!#\e(B<cf node="text/plain">
+A textual data represented by only <dref>coded character set</dref>.
+It does not have information about font or typesetting.
+<cf node="text/plain">
<h3> Security multipart
<node> Security multipart
<p>
-<a node="MIME">MIME</a>
\e$B$G0E9f$dEE;R=qL>$rMQ$$$k$?$a$N7A<0!#
\e(B<a
-node="multipart/signed"><concept>multipart/signed</concept></a>
\e$B$H
\e(B <a
-node="multipart/encrypted"><concept>multipart/encrypted</concept></a>
-
\e$B$H$$$&
\e(B multipart
\e$B$rMQ$$$k!#
\e(BMOSS
\e$B$d
\e(B <a node="PGP/MIME">PGP/MIME</a>
\e$B$O
\e(B
-\e$B$3$l$K4p$$$F$$$k!#\e(B
+A format to represent signed/encrypted message in <dref>MIME</dref>.
+<p>
+It defines two multipart media types, <a
+node="multipart/signed"><concept>multipart/signed</concept></a> and <a
+node="multipart/encrypted"><concept>multipart/encrypted</concept></a>.
+<p>
+MOSS and <dref>PGP/MIME</dref> are based on it.
<rfc name="Security multipart" number="1847" type="Standards Track"
author="James Galvin, Gale Murphy, Steve Crocker and Ned
<h3> text/enriched
<node> text/enriched
<p>
-RFC 1521 \e$B$GDj5A$5$l$?\e(B <concept>text/richtext</concept> \e$B$KBe$o$C$F!"=q\e(B
-\e$BBN$dAHHG$K4X$9$k>pJs$r;}$C$?\e(B text\e$B$rI=8=$9$k$?$a$N\e(B <dref>media
-type</dref>.
-
<rfc name="text/enriched" number="1896" author="P. Resnick and
A. Walker" title="The text/enriched MIME Content-type"
date="February 1996" obsolete="1563">
<h3> tm-kernel, tm
<node> tm-kernel
<p>
-Emacs
\e$B$G
\e(B <a node="MIME">MIME</a>
\e$B$rMxMQ$9$k$?$a$N
\e(B user interface
\e$B$rDs
\e(B
-\e$B6!$9$k\e(B library \e$B72!#\e(B`tools for MIME' \e$B$NN,!#\e(B
+A libraries to provide user interface about <dref>MIME</dref> for
+emacs. tm stands for `tools for MIME'.
-<memo title="\e$B$I$&$G$bNI$$$3$H\e(B(^-^;">
+<memo title="Unimportant notice(^-^;">
<p>
<ul>
- <li> tm \e$B$O\e(B ``tiny-mime'' \e$B$NN,$8$c$J$$$i$7$$$>\e(B (^-^;
- <li> tm \e$B$O:n<T$N%$%K%7%c%k$8$c$J$$$i$7$$$>\e(B (^-^;
- <li> ``Tools for MIME'' \e$B$NN,$H$$$&$N$O$3$8$D$1$i$7$$$>\e(B (^-^;
+ <li> tm may not stand for ``tiny-mime''(^-^;
+ <li> tm may not stand for initial of an author (^-^;
+ <li> ``Tools for MIME'' may be strained (^-^;
</ul>
</memo>
<h3> tm-MUA
<node> tm-MUA
<p>
-<a node="tm-kernel">tm</a>
\e$B$rMQ$$$?
\e(B <a node="MUA">MUA</a>
\e$B$b$7$/$O
\e(B MUA
-\e$B$KBP$9$k\e(B extender.
+<dref>MUA</dref> or MUA extender using <a node="tm-kernel">tm</a>.
<p>
-<concept>tm \e$BBg@9$j\e(B package</concept> \e$B$K$O\e(B
+<concept>tm oomori package</concept> has following extenders:
<ul>
-<li><a file="mh-e">mh-e</a> \e$BMQ$N\e(B <concept>tm-mh-e</concept>
-<li>GNUS \e$BMQ$N\e(B <concept>tm-gnus</concept>
-<li>Gnus
\e$BMQ$N
\e(B <a file="gnus-mime-en"><concept>gnus-mime</concept></a>
-<li>VM \e$BMQ$N\e(B <concept>tm-vm</concept>
-<li>RMAIL \e$BMQ$N\e(B <concept>tm-rmail</concept>
+<li><a file="tm-mh-e-en"><concept>tm-mh-e</concept></a>
+ for <a file="mh-e">mh-e</a>
+<li><a file="tm-gnus_en"><concept>tm-gnus</concept></a> for GNUS
+<li><a file="gnus-mime-en"><concept>gnus-mime</concept></a> for Gnus
+<li><a file="tm-vm_en"><concept>tm-vm</concept></a> for VM
+<li><concept>tm-rmail</concept> for RMAIL
</ul>
-<noindent>
-\e$B$,4^$^$l$F$$$k!#\e(B
-<p>
-
\e$BFHN)$7$?
\e(B MUA
\e$B$H$7$F$O
\e(B <a file="cmail">cmail</a>
\e$B$,
\e(B tm
\e$B$rMxMQ2DG=$G$"$k!#
\e(B
-
<h3> us-ascii
<node> us-ascii
<p>
-
\e$B%"%a%j%+O"K.$J$I$G;H$o$l$k1Q8l$J$I$rI=8=$9$k$?$a$N
\e(B <a node="MIME
-charset">MIME charset</a> \e$B$N#1$D!#\e(B
+A <a node="MIME charset">MIME charset</a> for primary Latin script
+mainly written by English or other languages.
<p>
-<dref>ASCII</dref>
\e$B$N$_$+$i$J$j
\e(B <dref>ISO 2022</dref>
\e$B$K$h$k
\e(B<a
-node="Code extension">\e$BId9f3HD%\e(B</a>\e$B$O5v$5$l$J$$!#\e(B
+It is a 7bit <dref>coded character set</dref> based on <dref>ISO
+2022</dref>, it contains only
+<dref>ASCII</dref> and <dref>code extension</dref> is not allowed.
<p>
-Internet mail
\e$B$K$*$1$kI8=`$N
\e(B<a node="Coded character set">
\e$BId9f2=J8;z=8
\e(B
-\e$B9g\e(B</a>\e$B$G$"$j!"L@<(E*$K\e(B MIME charset \e$B$,<($5$l$J$$>l9g$O86B'$H$7$F\e(B
-<concept>us-ascii</concept> \e$B$,;H$o$l$k!#\e(B
+It is standard coded character set of Internet mail. If MIME charset
+is not specified, <concept>us-ascii</concept> is used as default.
<p>
-
\e$B$^$?!"
\e(B<a node="RFC 822">RFC 822</a>
\e$B$K$*$1$k
\e(B <concept>ASCII</concept>
-
\e$B$O
\e(B us-ascii
\e$B$r;X$9$b$N$H2r<a$9$Y$-$G$"$k!#
\e(B
+In addition, <concept>ASCII</concept> of <dref>RFC 822</dref> should
+be interpreted as us-ascii.
<h1> Setting
projects / elisp / tm.git / blobdiff