Mercurial > hg > xemacs-beta
diff man/tm/tm-en.sgml @ 8:4b173ad71786 r19-15b5
Import from CVS: tag r19-15b5
| author | cvs |
|---|---|
| date | Mon, 13 Aug 2007 08:47:35 +0200 |
| parents | |
| children | 49a24b4fd526 |
line wrap: on
line diff
--- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/man/tm/tm-en.sgml Mon Aug 13 08:47:35 2007 +0200 @@ -0,0 +1,1582 @@ +<!doctype sinfo system> +<!-- $Id: tm-en.sgml,v 1.1 1996/12/22 00:09:33 steve Exp $ --> +<head> +<title>tm 7.90 Manual (English Version) +<author>MORIOKA Tomohiko <mail>morioka@jaist.ac.jp</mail> +<date>1996/10/15 + +<toc> +</head> + +<body> + +<abstract> +<p> +This file documents tm, a MIME package for GNU Emacs. +</abstract> + +<h1> What is tm? +<node> Introduction +<p> +The tm package is a set of modules to enjoy MIME on GNU Emacs. Using +tm, you can + +<ul> +<li> playback or view the MIME messages using tm-view +<li> compose MIME message using tm-edit +<li> use the enhanced MIME features with mh-e, GNUS, Gnus, RMAIL and VM +</ul> + +<noindent> +and more. +<p> +Please read following about each topics: + +<ul> +<li><a file="gnus-mime-en">tm-MUA for Gnus</a> +<li><a file="tm-gnus-en">tm-MUA for GNUS</a> +<li><a file="tm-mh-e-en">tm-MUA for mh-e</a> +<li><a file="tm-view-en">mime/viewer-mode</a> +<li><a file="tm-edit-en">mime/editor-mode</a> +</ul> + + +<h2> Glossary +<node> Glossary + +<h3> 7bit +<node> 7bit +<p> +<concept>7bit</concept> means any integer between 0 .. 127. +<p> +Any data represented by 7bit integers is called <concept>7bit +data</concept>. +<p> +Textual string consisted of Control characters between 0 .. 31 and +127, and space represented by 32, and graphic characters between 33 +.. 236 are called <concept>7bit (textual) string</concept>. +<p> +Traditional Internet <a node="MTA">MTA</a> can translate 7bit data, so +it is no need to translate by <a +node="Quoted-Printable">Quoted-Printable</a> or <a +node="Base64">Base64</a> for 7bit data. +<p> +However if there are too long lines, it can not translate by 7bit MTA +even if it is 7bit data. <dref>RFC 821</dref> and <dref>RFC +2045</dref> 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 <dref>binary</dref>. For example, Postscript file should be +encoded by Quoted-Printable. + + +<h3> 8bit +<node> 8bit +<p> +<concept>8bit</concept> means any integer between 0 .. 255. +<p> +Any data represented by 8bit integers is called <concept>8bit +data</concept>. +<p> +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 <concept>8bit (textual) +string</concept>. +<p> +For example, <dref>iso-8859-1</dref> or <dref>euc-kr</dref> are +coded-character-set represented by 8bit textual string. +<p> +Traditional Internet <a node="MTA">MTA</a> can translate only +<dref>7bit</dref> data, so if a 8bit data will be translated such MTA, +it must be encoded by <dref>Quoted-Printable</dref> or +<dref>Base64</dref>. +<p> +However 8bit MTA are increasing today. +<p> +However if there are too long lines, it can not translate by 8bit MTA +even if it is 8bit data. <dref>RFC 2045</dref> 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 <dref>binary</dref>, so it must +be encoded by Base64 or Quoted-Printable. + + +<h3> 94-character set +<node> 94-character set +<p> +<concept>94-character set</concept> is a kind of 1 byte <dref>graphic +character set</dref>, each characters are in positions 02/01 (33) to +07/14 (126) or 10/01 (161) to 15/14 (254). (ex. <dref>ASCII</dref>, +JIS X0201-Latin) + + +<h3> 96-character set +<node> 96-character set +<p> +<concept>96-character set</concept> is a kind of 1 byte <dref>graphic +character set</dref>, each characters are in positions 02/00 (32) to +07/15 (126) or 10/00 (160) to 15/15 (255). (ex. ISO 8859) + + +<h3> 94x94-character set +<node> 94x94-character set +<p> +<concept>94x94-character set</concept> is a kind of 2 byte +<dref>graphic character set</dref>, each bytes are in positions 02/01 +(33) to 07/14 (126) or 10/01 (161) to 15/14 (254). (ex. <dref>JIS +X0208</dref>, <dref>GB 2312</dref>) + + +<h3> ASCII +<node> ASCII +<p> +$B%"%a%j%+O"K.$G;H$o$l$kJ8;z$rId9f2=$7$?(B <dref>94-character set</dref>. +A-Z, a-z $B$N(B Latin $BJ8;z$H?t;z!"4v$D$+$N5-9f$+$i$J$k!#(B<a node="ISO +646">ISO 646</a> $B$N0l$D!#(B + +<standard abbrev="ASCII" title-en="Coded Character Set -- 7-Bit + American Standard Code for Information Interchange" + number="ANSI X3.4" year="1986"> + + +<h3> Base64 +<node> Base64 +<p> +<concept>Base64</concept> is a transfer encoding method of +<dref>MIME</dref> defined in <dref>RFC 2045</dref>. +<p> +The encoding process represents 24-bit groups of input bits as output +strings of 4 encoded characters. Encoded characters represent integer +0 .. 63 or <concept>pad</concept>. Base64 data must be 4 * n bytes, +so pad is used to adjust size. +<p> +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. + + +<h3> binary +<node> binary +<p> +$BG$0U$N(B byte $BNs$r(B <concept>binary</concept> $B$H8F$V$3$H$K$7$^$9!#(B +<p> +<a node="8bit">8bit</a> $B$H0[$J$k$N$O(B data $B$K9T$N9=B$$r2>Dj$7$J$$$3$H$G(B +$B$9!#(B +<p> +$B$^$?!"9T$N9=B$$,$"$C$F$b!"(B999 byte $B0J>e$+$i$J$k9T$,$"$k>l9g$b(B binary +$B$H8F$V$3$H$K$7$^$9!#(B +<p> +$B$A$J$_$K!"(B<a node="7bit">7bit</a> $B$d(B 8bit $B$GI=8=$G$-$k(B data $B$O(B binary +$B$G$bI=8=$G$-$^$9!#$h$C$F!"(B<concept>binary data</concept> $B$H8@$C$?>l9g!"(B +$BG$0U$N(B data $B$r;X$9$3$H$,$"$j$^$9!#(B + + +<h3> Graphic Character Set +<node> graphic character set +<p> +<dref>Coded character set</dref> for graphic characters. + + +<h3> cn-gb, gb2312 +<node> cn-gb +<p> +$BCf9qBgN&$G$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N(B <a +node="MIME charset">MIME charset</a> $B$N#1$D!#(B +<p> +<dref>ISO 2022</dref> $B$K4p$$$F(B <dref>ASCII</dref> $B$K(B <dref>GB +2312</dref> $B$r(B <dref>8bit</dref> $B$G(B<a node="Code extension">$BId9f(B +$B3HD%(B</a>$B$7$F$$$k!#(B +<p> +<a node="RFC 1922">RFC 1922</a> $B$GDj5A$5$l$F$$$k!#(B + + +<h3> cn-big5, big5 +<node> cn-big5 +<p> +$BBfOQ$d9a9A$GMQ$$$i$l$F$$$k<g$KHKBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N(B +<a node="MIME charset">MIME charset</a> $B$N#1$D!#(B +<p> +<dref>ISO 2022</dref> $B$K4p$+$J$$(B <dref>8bit</dref> $B$N(B +<dref>coded character set</dref>$B$G(B de-fact standard $B$G(B +$B$"$k!#(B<a node="RFC 1922">RFC 1922</a> $B$GDj5A$5$l$F$$$k!#(B +<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> $B$HBP1~4X78$,$"$k!#(B + + +<h3> CNS 11643-1992 +<node> CNS +<p> +$BBfOQ$d9a9A$GMQ$$$i$l$F$$$k<g$KHKBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N(B +<a node="Character set">$BJ8;z=89g(B</a>$B!#BfOQ$NI8=`!#8=:_!"(B<a node="94x94 +character set">94$B!_(B94</a> $B$NLL$,Bh#1LL$+$iBh#7LL$^$G$"$k!#(B +<p> +<dref>ISO 2022</dref> $B$G$N=*C<J8;z$O!"Bh#1LL$,(B `G', $BBh#2LL$,(B +`H', $BBh#3LL$,(B `I', $BBh#4LL$,(B `J', $BBh#5LL$,(B `K', $BBh#6LL$,(B `L', $BBh#7LL$,(B +`M' $B$G$"$k!#(B + +<standard abbrev="CNS 11643-1992" title-en="Standard Interchange Code + for Generally-Used Chinese Characters" number="CNS + 11643" year="1992"> + + +<h3> Coded character set, Character code +<node> coded character set +<p> +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. + + +<h3> Code extension +<node> code extension +<p> +The techniques for the encoding of characters that are not included in +the character set of a given code. (ex. <dref>ISO 2022</dref>) + + +<h3> Content-Disposition field +<node> Content-Disposition +<p> +Content $B$NI=<($N;EJ}$d(B file $BL>$rI=8=$9$k$?$a$N(B field. <a +node="MIME">MIME</a> $B$N3HD%$N#1$D!#(B +<p> +<rfc number="1806" type="Experimental" author="E R. Troost and + S. Dorner" title="Communicating Presentation Information + in Internet Messages: The Content-Disposition Header" + 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> +Header field to represent information about body, such as <dref>media +type</dref>, <dref>MIME charset</dref>. It is defined in <dref>RFC +2045</dref>. + +<memo> +<p> +Historically, Content-Type field was proposed in RFC 1049. In it, +Content-Type did not distinguish type and subtype. However MIME +parser may be able to accept RFC 1049 based Content-Type as unknown +type. +</memo> + +<p> +Content-Type field is defined as following: + +<quote> +``Content-Type'' ``:'' <concept>type</concept> ``/'' +<concept>subtype</concept> *( ``;'' <concept>parameter</concept> ) +</quote> + +<p> +For example: + +<quote> +<verb> +Content-Type: image/jpeg +</verb> +</quote> + +<quote> +<verb> +Content-Type: text/plain; charset=iso-2022-jp +</verb> +</quote> + +<memo> +<p> +A part does not have content-type field is regarded as + +<quote> +<verb> +Content-Type: text/plain; charset=us-ascii +</verb> +</quote> + +<noindent> +<cf node="us-ascii"> + +And a part has unknown type/subtype is regarded as + +<quote> +<verb> +Content-Type: application/octet-stream +</verb> +</quote> + +</memo> + + +<h3> Emacs +<node> Emacs +<p> +$B$3$3$G$O(B `Emacs' $B$G(B FSF $B$,G[I[$7$F$$$k(B GNU Emacs $B$r;X$7!"(B`emacs' $B$G(B +GNU Emacs $B$NJQ<o$NAm>N$H$9$k!#(B + + +<h3> encoded-word +<node> encoded-word +<p> +Representation non <dref>ASCII</dref> characters in header. It +is defined in <concept>RFC 2047</concept>. +<p> +<rfc number="2047" type="Standards Track" author="K. Moore" + title="MIME (Multipurpose Internet Mail Extensions) Part + Three: Message Header Extensions for Non-ASCII Text" + date="November 1996" obsolete="1521,1522,1590"> + + +<h3> encapsulation +<node> encapsulation +<p> +<a node="RFC 822">Internet mail</a> $B$rB>$N5-;v$K$^$k$4$HF~$l$kJ}K!!#(B +<p> +$BNc$($P!"5-;v$rE>Aw$7$?$j$9$k$N$KMQ$$$k!#(B +<p> +<cf node="message/rfc822"> + + +<h3> euc-kr +<node> euc-kr +<p> +$B4Z9q8l$rI=8=$9$k$?$a$N(B <a node="MIME charset">MIME charset</a> $B$N#1$D!#(B +<p> +<dref>ISO 2022</dref> $B$K4p$$$F(B <dref>ASCII</dref> $B$K(B +<a node="KS C5601">KS C5601</a> $B$r(B <dref>8bit</dref> $B$G(B<a +node="Code extension">$BId9f3HD%(B</a>$B$7$F$$$k!#(B +<p> +<a node="RFC 1557">RFC 1557</a> $B$GDj5A$5$l$F$$$k!#(B +<p> +cf. <standard abbrev="euc-kr" org="Korea Industrial Standards + Association" title-en="Hangul Unix Environment" + number="KS C 5861" year="1992"> + + +<h3> FTP <node> FTP +<p> +Internet $B$G(B file $B$rE>Aw$9$k$?$a$N(B protocol $B$N#1$D!#(BRFC 959 $B$GDj5A$5$l(B +$B$F$$$k!#(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> +$BCf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=$9$?$a$N(B +<dref>94x94-character set</dref>$B!#Cf9q$N9q2HI8=`!#(B<a node="ISO +2022">ISO 2022</a> $B$G$N=*C<J8;z$O(B `A'. +<p> +$B$3$l$O(B GB $B$K$*$1$k4pK\=8$G$"$k!#(B + +<standard abbrev="GB 2312" + title-cn="$B?.B)8r49MQ4A;zJTb{;zId=8(B -- $B4pK\=8(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> +$BCf9q8l$N$?$a$NJd=u(B<a node="Character set">$BJ8;z=89g(B</a>$B!#Cf9q$N9q2HI8=`!#(B +<a node="GB 2312">GB 2312</a> $B$N6u$-ItJ,$KJd=<$9$k$h$&$KDj5A$5$l$?$i$7(B +$B$$!#(B + +<standard abbrev="GB 8565.2" title-en="Information Processing - Coded + Character Sets for Text Communication - Part 2: Graphic + Characters used with Primary Set" number="GB 8565.2" + year="1988"> + + +<h3> hz-gb2312 +<node> hz-gb2312 +<p> +$BCf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N(B <a +node="MIME charset">MIME charset</a> $B$N#1$D!#(B +<p> +<dref>ASCII</dref> $B$K(B <a node="GB 2312">GB 2312</a> $B$r(B 7bit $B$G(B +<a node="Code extension">$BId9f3HD%(B</a>$B$7$?$b$N$r(B ASCII printable $B$K$J$k(B +$B$h$&$K9)IW$7$F$$$k!#(B +<p> +RFC 1842, 1843 $B$GDj5A$5$l$F$$$k!#(B + +<rfc number="1842" type="Informational" author="Y. Wei, Y. Zhang, + J. Li, J. Ding and Y. Jiang" title="ASCII Printable + Characters-Based Chinese Character Encoding for Internet + Messages" date="August 1995"> +<rfc number="1843" type="Informational" author="F. Lee" title="HZ - A + Data Format for Exchanging Files of Arbitrarily Mixed + Chinese and ASCII characters" date="August 1995"> + + +<h3> ISO 2022 +<node> ISO 2022 +<p> +<a node="Code extension">$BId9f3HD%(B</a>$B$N$?$a$N9q:]I8=`!#(B +<p> +$B$3$l$rMQ$$$FJ#?t$N(B<a node="Character set">$BJ8;z=89g(B</a>$B$rAH9g$;$F(B <a +node="7bit">7bit</a> $B$J$$$7(B <dref>8bit</dref> $B$N(B <a node="Coded +character set">$BId9f2=J8;z=89g(B</a> $B$r:n$k$3$H$,$G$-$k!#(B + +<standard abbrev="ISO 2022" org="International Organization for + Standardization (ISO)" title-en="Information Processing: + ISO 7-bit and 8-bit coded character sets: Code extension + techniques" number="ISO/IEC 2022" year="1994"> + + +<h3> iso-2022-cn +<node> iso-2022-cn +<p> +$BCf9q8l$rI=8=$9$k$?$a$N(B <a node="MIME charset">MIME charset</a> $B$N#1$D!#(B +<p> +<dref>ISO 2022</dref> $B$K4p$$$F(B <dref>ASCII</dref> $B$K(B +<a node="GB 2312">GB 2312</a>, <a node="CNS">CNS 11643 plain 1, plain +2</a> $B$r(B <a node="7bit">7bit</a> $B$G(B<a node="Code extension">$BId9f3HD%(B +</a>$B$7$F$$$k!#(B +<p> +<a node="RFC 1922">RFC 1922</a> $B$GDj5A$5$l$F$$$k!#(B + + +<h3> iso-2022-cn-ext +<node> iso-2022-cn-ext +<p> +$BCf9q8l$rI=8=$9$k$?$a$N(B <a node="MIME charset">MIME charset</a> $B$N#1$D!#(B +<p> +<dref>ISO 2022</dref> $B$K4p$$$F(B <dref>ASCII</dref> $B$K(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> $BEy$r(B <a +node="7bit">7bit</a> $B$G(B<a node="Code extension">$BId9f3HD%(B</a>$B$7$F$$$k!#(B +<p> +<a node="RFC 1922">RFC 1922</a> $B$GDj5A$5$l$F$$$k!#(B +<p> +<memo> +MULE 2.3 $B$*$h$S!"8=:_$N(B XEmacs/mule $B$G$O@5$7$/07$&$3$H$O$G$-$J$$!#(B +<p> +Emacs/mule $B$G$OMxMQ2DG=$G$"$k!#(B +</memo> + + +<h3> iso-2022-jp +<node> iso-2022-jp +<p> +$BF|K\8l$rI=8=$9$k$?$a$N(B <a node="MIME charset">MIME charset</a> $B$N0l$D!#(B +<p> +$B8E$$(B <dref>ISO 2022</dref> $B$K4p$$$F(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> $B$r@Z$jBX$($k(B <a +node="7bit">7bit</a> $BJ8;zId9f!#(B +<p> +RFC 1468 $B$GDj5A$5$l$F$$$k!#(B +<p> +<memo> +JIS X0208-1996? $B$G$O(B <dref>ISO 2022</dref> $B$HFHN)$KDj5A$5$l(B +$B$kM=Dj!#(B +</memo> + +<rfc name="iso-2022-jp" number="1468" author="Murai J., M. Crispin, + and E. van der Poel" title="Japanese Character Encoding + for Internet Messages" date="June 1993"> + + +<h3> iso-2022-jp-2 +<node> iso-2022-jp-2 +<p> +A <dref>MIME charset</dref>, which is a multilingual extension of +<dref>iso-2022-jp</dref>. +<p> +It is defined in RFC 1554. + +<rfc name="iso-2022-jp-2" number="1554" type="Informational" + author="Ohta M. and Handa K." title="ISO-2022-JP-2: + Multilingual Extension of ISO-2022-JP" date="December + 1993"> + + +<h3> iso-2022-kr +<node> iso-2022-kr +<p> +A <a node="MIME charset">MIME charset</a> for Korean language (Hangul +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. +<p> +It is defined in <dref>RFC 1557</dref>. + + +<h3> ISO 646 +<node> ISO 646 +<p> +$B3F9q$G6&DL$K;H$($k:G>.8BEY$N(B<a node="Character set">$BJ8;z=89g(B</a>$B$rDj$a(B +$B$?$b$N!#(B<a node="94 character set">94 $BJ8;z=89g(B</a>$B$N#1$D!#(BISO 646 IRV +$B!J9q:]4p=`HG!K$r85$K4v$D$+$NJ8;z$O3F9q$G0c$&J8;z$r3dEv$k$3$H$r5v$7$F$$(B +$B$F!"4v$D$+$NJQ<o$,B8:_$9$k!#(B<dref>ASCII</dref> $B$d(B JIS +X0201-Latin $B$O$=$N0l<o!#(B + +<standard abbrev="ISO 646" org="International Organization for + Standardization (ISO)" title-en="Information technology: + ISO 7-bit coded character set for information + interchange" number="ISO/IEC 646" year="1991"> + + +<h3> ISO 8859-1 +<node> ISO 8859-1 +<p> +<standard abbrev="ISO 8859-1" org="International Organization for + Standardization (ISO)" title-en="Information Processing + -- 8-bit Single-Byte Coded Graphic Character Sets -- + Part 1: Latin Alphabet No.1" number="ISO 8859-1" + year="1987"> + + +<h3> iso-8859-1 +<node> iso-8859-1 +<p> +<concept>iso-8859-1</concept> is a <dref>MIME charset</dref> for +west-European languages written by Latin script. +<p> +<dref>ISO 2022</dref> $B$K4p$$$F!"(B<dref>ASCII</dref> $B$K(B +<a node="ISO 8859-1">ISO 8859-1</a> $B$r(B <dref>8bit</dref> $B$G(B<a +node="Code extension">$BId9f3HD%(B</a>$B$7$F$$$k!#(B +<p> +It is defined in <dref>RFC 2046</dref>. + + +<h3> ISO 8859-2 +<node> ISO 8859-2 +<p> +<standard abbrev="ISO 8859-2" org="International Organization for + Standardization (ISO)" title-en="Information Processing + -- 8-bit Single-Byte Coded Graphic Character Sets -- + Part 2: Latin alphabet No.2" number="ISO 8859-2" + year="1987"> + + +<h3> iso-8859-2 +<node> iso-8859-2 +<p> +<concept>iso-8859-2</concept> is a <dref>MIME charset</dref> for +east-European languages written by Latin script. +<p> +<dref>ISO 2022</dref> $B$K4p$$$F!"(B<dref>ASCII</dref> $B$K(B +<a node="ISO 8859-2">ISO 8859-2</a> $B$r(B <dref>8bit</dref> $B$G(B<a +node="Code extension">$BId9f3HD%(B</a>$B$7$F$$$k!#(B +<p> +It is defined in <dref>RFC 2046</dref>. + + +<h3> ISO 8859-3 +<node> ISO 8859-3 +<p> +<standard abbrev="ISO 8859-3" org="International Organization for + Standardization (ISO)" title-en="Information + Processing -- 8-bit Single-Byte Coded Graphic + Character Sets -- Part 3: Latin alphabet No.3" + number="ISO 8859-3" year="1988"> + + +<h3> ISO 8859-4 +<node> ISO 8859-4 +<p> +<standard abbrev="ISO 8859-4" org="International Organization for + Standardization (ISO)" title-en="Information + Processing -- 8-bit Single-Byte Coded Graphic + Character Sets -- Part 4: Latin alphabet No.4" + number="ISO 8859-4" year="1988"> + + +<h3> ISO 8859-5 +<node> ISO 8859-5 +<p> +<standard abbrev="ISO 8859-5" org="International Organization for + Standardization (ISO)" title-en="Information Processing + -- 8-bit Single-Byte Coded Graphic Character Sets -- + Part 5: Latin/Cyrillic alphabet" number="ISO 8859-5" + year="1988"> + + +<h3> iso-8859-5 +<node> iso-8859-5 +<p> +<concept>iso-8859-5</concept> is a <dref>MIME charset</dref> for +Cyrillic script. +<p> +<dref>ISO 2022</dref> $B$K4p$$$F!"(B<dref>ASCII</dref> $B$K(B +<a node="ISO 8859-5">ISO 8859-5</a> $B$r(B <dref>8bit</dref> $B$G(B<a +node="Code extension">$BId9f3HD%(B</a>$B$7$F$$$k!#(B +<p> +It is defined in <dref>RFC 2046</dref>. + + +<h3> ISO 8859-6 +<node> ISO 8859-6 +<p> +<standard abbrev="ISO 8859-6" org="International Organization for + Standardization (ISO)" title-en="Information + Processing -- 8-bit Single-Byte Coded Graphic + Character Sets -- Part 6: Latin/Arabic alphabet" + number="ISO 8859-6" year="1987"> + + +<h3> ISO 8859-7 +<node> ISO 8859-7 +<p> +<standard abbrev="ISO 8859-7" org="International Organization for + Standardization (ISO)" title-en="Information Processing + -- 8-bit Single-Byte Coded Graphic Character Sets -- + Part 7: Latin/Greek alphabet" number="ISO 8859-7" + year="1987"> + + +<h3> iso-8859-7 +<node> iso-8859-7 +<p> +<concept>iso-8859-7</concept> is a <dref>MIME charset</dref> for +Greek script. +<p> +<dref>ISO 2022</dref> $B$K4p$$$F!"(B<dref>ASCII</dref> $B$K(B +<a node="ISO 8859-7">ISO 8859-7</a> $B$r(B <dref>8bit</dref> $B$G(B<a +node="Code extension">$BId9f3HD%(B</a>$B$7$F$$$k!#(B +<p> +It is defined in RFC 1947. + +<rfc name="iso-8859-7" number="1947" type="Informational" + author="D. Spinellis" title="Greek Character Encoding + for Electronic Mail Messages" date="May 1996"> + + +<h3> ISO 8859-8 +<node> ISO 8859-8 +<p> +<standard abbrev="ISO 8859-8" org="International Organization for + Standardization (ISO)" title-en="Information + Processing -- 8-bit Single-Byte Coded Graphic + Character Sets -- Part 8: Latin/Hebrew alphabet" + number="ISO 8859-8" year="1988"> + + +<h3> ISO 8859-9 +<node> ISO 8859-9 +<p> +<standard abbrev="ISO 8859-9" org="International Organization for + Standardization (ISO)" title-en="Information + Processing -- 8-bit Single-Byte Coded Graphic + Character Sets -- Part 9: Latin alphabet No.5" + number="ISO 8859-9" year="1990"> + + +<h3> ISO-IR-165, CCITT Extended GB <node> ISO-IR-165 +<p> +CCITT $B$,EPO?$7$?!"Cf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=(B +$B8=$9$k$?$a$N(B <dref>94x94-character set</dref>$B!#(B +<p> +<a node="GB 2312">GB 2312</a> $B$H(B <a node="GB 8865.2">GB 8565 $BI=#2(B</a> +$B$K(B 150 $BJ8;z$[$I$rDI2C$7$?$b$N$i$7$$!#(B +<p> +<dref>ISO 2022</dref> $B$G$N=*C<J8;z$O(B `E' $B$G$"$k!#(B + + +<h3> JIS X0201 +<node> JIS X0201 +<p> +<a node="ISO 646">ISO 646</a> $B$NJQ<o$N#1$D$G$"$k(B Latin $BJ8;z=89g$H(B 1 +byte $B$N%+%?%+%JJ8;z=89g$+$i$J$k!#(B +<p> +$B85$O(B <concept>JIS C6220-1976</concept> $B$H8@$C$?$,(B <concept>JIS +X0201</concept> $B$KHV9f$,JQ99$5$l$?!#(B + +<standard abbrev="JIS X0201-1976" org="$BF|K\5,3J6(2q(B (Japanese + Standards Association)" title-ja="$B>pJs8r49MQId9f(B" + title-en="Code for Information Interchange" number="JIS + X 0201-1976"> + +$B$^$?!"(B1996 $BG/$K2~DjHG$,=P$kM=Dj!#(B + +<standard abbrev="JIS X0201-1996?" org="$BF|K\5,3J6(2q(B (Japanese + Standards Association)" + title-ja="$B#7%S%C%H5Z$S#8%S%C%H$N>pJs8r49MQId9f2=J8;z=89g(B" + title-en="7-bit and 8-bit coded character sets for + information interchange" number="JIS X 0201" year="1996? + draft"> + + +<h3> JIS C6226-1978 +<node> JIS C6226 +<p> +$BF|K\8l$rI=$9$?$a$K:n$i$l$?(B <dref>94x94-character set</dref>$B!#F|K\$N9q(B +$B2HI8=`!#(BJIS X0208-1978 $B$H$b$$$&!#(B +<p> +<cf node="JIS X0208"> + + +<h3> JIS X0208 +<node> JIS X0208 +<p> +$BF|K\8l$rI=$9$?$a$K:n$i$l$?(B <dref>94x94-character set</dref>$B!#F|K\$N9q(B +$B2HI8=`!#(B1978 $BG/HG!"(B1983 $BG/HG!"(B1990 $BG/HG$,$"$k$,!"(BInternet $B$G$O(B 1983 $BG/(B +$BHG$,$b$C$H$bNI$/;H$o$l$F$$$k!#(B +<p> +JIS X0208 $B$O5-9f!"?t;z!"%m!<%^;z!"$R$i$,$J!"%+%?%+%J!"%.%j%7%cJ8;z!"%-(B +$B%j%kJ8;z!"7S@~AG!"Bh#1?e=`!"Bh#2?e=`$N4A;z$,4^$^$l$k!#C"$7!"(B1983 $BG/HG(B +$B$N0lIt$N5-9f$H7S@~AG$O(B 1978 $BG/HG$K$O$J$$!#$^$?!"0lIt$N4A;z$N;z7A$,(B +1983 $BG/HG$G$OJQ99$5$l!"$^$?!"Bh#1?e=`$HBh#2?e=`$,F~$lBX$o$C$F$$$?$j$9(B +$B$k!#$3$N$?$a!"(B1978 $BG/HG$H(B 1983 $BG/HG$O0[$J$kJ8;z=89g$H$7$F07$o$l$k!#(B +<p> +1990 $BG/$N2~Dj$G$O(B 1983 $BG/HG$KBP$9$kDI2C$,9T$o$l$?!#$3$N$?$a!"(B1990 $BG/HG(B +$B$r;X<($9$k>l9g$OA0$K99?7%7!<%1%s%9$rMQ$$$k!#(B + +<standard abbrev="JIS X0208-1978" org="$BF|K\5,3J6(2q(B (Japanese Standards + Association)" title-ja="$B>pJs8r49MQ4A;zId9f7O(B" + title-en="Code of the Japanese graphic character set for + information interchange" number="JIS C6226" year="1978"> +<standard abbrev="JIS X0208-1983,1990" org="$BF|K\5,3J6(2q(B (Japanese Standards + Association)" title-ja="$B>pJs8r49MQ4A;zId9f7O(B" + title-en="Code of the Japanese graphic character set for + information interchange" number="JIS X0208" year="1983,1990"> + +<p> +$B$^$?!"(B1996 $BG/$K2~DjHG$,=PHG$5$l$kM=Dj!#!J;z7A$NJQ99$O9T$o$l$J$$$N$GJ8(B +$B;z=89g$H$7$F$O(B 1990 $BG/HG$HF10l$G$"$k!K(B + +<standard abbrev="JIS X0208-1996?" org="$BF|K\5,3J6(2q(B (Japanese + Standards Association)" title-ja="$B#7%S%C%H5Z$S#8%S%C%H$N(B + $B#2%P%$%H>pJs8r49MQId9f2=4A;z=89g(B" title-en="7-bit and + 8-bit double byte coded Kanji sets for information + interchange" number="JIS X 0208" year="1996? draft"> + + +<h3> JIS X0212-1990 +<node> JIS X0212 +<p> +<a node="JIS X0208">JIS X0208</a> $B$K$J$+$C$?J8;z$r=8$a$?(B +<dref>94x94-character set</dref>$B!#!VJd=u4A;z!W$H$b8F$P$l$k!#F|K\$N9q2H(B +$BI8=`!#(B<dref>ISO 2022</dref> $B$G$N=*C<J8;z$O(B `D'. + + +<h3> koi8-r +<node> koi8-r +<p> +A <dref>MIME charset</dref> for Cyrillic script for Russian or other +languages. +<p> +It is a 1 byte <dref>8bit</dref> <dref>coded character set</dref>, not +based on <dref>ISO 2022</dref>. It is a de-fact standard. +<p> +It is defined in RFC 1489. +<p> +<rfc number="1489" author="A. Chernov" title="Registration of a + Cyrillic Character Set" date="July 1993"> + + +<h3> KS C5601-1987 +<node> KS C5601 +<p> +A <dref>94x94-character set</dref> for Korean language (Hangul +script). Korean Standard. Final byte of <dref>ISO 2022</dref> is +`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> message +<node> message +<p> +$B$3$3$G$O(B <dref>RFC 822</dref> $B$GDj5A$5$l$k(B mail $B$H(B <dref>RFC +1036</dref> $B$GDj5A$5$l$k(B news $B5-;v$NAm>N$H$7$FMQ$$$k!#(B + + +<h3> message/rfc822 +<node> message/rfc822 +<p> +<concept>message/rfc822</concept> indicates that the body contains an +encapsulated message, with the syntax of an <dref>RFC 822</dref> +message. It is the replacement of traditional <dref>RFC 934</dref> +encapsulation. It is defined in <dref>RFC 2046</dref>. + + +<h3> method +<node> method +<p> +tm $B$GFCDj$N<oN`$N(B data $B$r:F@8$7$?$H$-<B:]$K$=$N=hM}$r9T$J$&(B +program. Emacs Lisp $B$G=q$+$l$?(B <concept>internal method</concept> $B$H(B C +$B$d(B script $B8@8l$J$I$G=q$+$l$?(B <concept>external method</concept> $B$,$"$k!#(B +<p> +<cf file="tm-view-en" node="method"> + + +<h3> MIME +<node> MIME +<p> +MIME stands for <concept>Multipurpose Internet Mail +Extensions</concept>, it is an extension for <dref>RFC 822</dref>. +<p> +According to RFC 2045: +<p> +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 +<p> +<ol> +<li>textual message bodies in character sets other than US-ASCII, +</li> +<li>an extensible set of different formats for non-textual message +bodies, +</li> +<li>multi-part message bodies, and +</li> +<li>textual header information in character sets other than US-ASCII. +</ol> + +<p> +It is defined in <dref>RFC 2045</dref>, <dref>RFC 2046</dref>, <a +node="encoded-word">RFC 2047</a>, <dref>RFC 2048</dref> and <dref>RFC +2049</dref>. + + +<h3> MIME charset +<node> MIME charset +<p> +<dref>Coded character set</dref> used in <dref>Content-Type +field</dref> or charset parameter of <a +node="encoded-word">encoded-word</a>. +<p> +It is defined in <dref>RFC 2045</dref>. +<p> +<dref>iso-2022-jp</dref> $B$d(B <a node="euc-kr">euc-kr</a> $B$O$=$N#1$D!#(B +$B!J$3$3$G$O!"(BMIME charset $B$O(B<a node="Character set">$BJ8;z=89g(B</a>$B$H6hJL(B +$B$7$F>.J8;z$G=q$$$F$$$k!K(B + + +<h3> MTA +<node> MTA +<p> +<concept>Message Transfer Agent</concept> $B$NN,$G!"(Bsendmail $B$J$I$N(B mail +$BG[Aw(B program $B$H(B news server $B$NAm>N!#(B +<p> +<cf node="MUA"> + + +<h3> MUA +<node> MUA +<p> +<concept>Message User Agent</concept> $B$NN,$G!"(Bmail reader $B$H(B news +reader $B$NAm>N!#(B +<p> +<cf node="MTA"> + + +<h3> MULE +<node> MULE +<p> +$BH>ED(B $B7u0l;a$i$,:n$C$?!"B?8@8l$5$l$?(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. +<p> +$B8=:_!"(BMULE $B$N5!G=$r(B Emacs $B$K(B merge $B$9$k:n6H$,9T$o$l$F$*$j!"(B<a +href="ftp://etlport.etl.go.jp/pub/mule/mule-19.33-gamma.taz"> alpha $BHG(B +</a> $B$,B8:_$9$k!#(B +<p> +$B$=$NB>!"(BXEmacs $B$K(B merge $B$7$?$b$N$bB8:_$9$k!#(B +<p> +$B$3$N$?$a!"8=:_$G$OB?8@8l(B Emacs $B$O!"85!9$N(B MULE $B$r4^$a$F#3<oN`$"$k$3$H(B +$B$K$J$k!#(B +<p> +$B$=$3$G!"$3$3$G$O!"B?8@8l(B Emacs $B$NAm>N$r(B <concept>mule</concept>, $B85!9(B +$B$N(B MULE $B$r(B <concept>MULE</concept>, mule $B5!G=$r(B merge $B$7$?(B Emacs $B$r(B +<concept>Emacs/mule</concept>, mule $B5!G=$r(B merge $B$7$?(B XEmacs $B$r(B +<concept>XEmacs/mule</concept> $B$H8F$V$3$H$K$9$k!#(B + + +<h3> Multipart +<node> multipart +<p> +<concept>multipart</concept> means <dref>media type</dref> to insert +multiple <dref>entities</dref> in a single body. Or it also indicates +a message consists of multiple entities. +<p> +There are following subtypes registered in <dref>RFC 2046</dref>: + +<ul> +<li><dref>multipart/mixed</dref> +<li><dref>multipart/alternative</dref> +<li><dref>multipart/digest</dref> +<li><dref>multipart/parallel</dref> +</ul> + +<noindent> +and registered in <a node="Security multipart">RFC 1847</a>: + +<ul> +<li><dref>multipart/signed</dref> +<li><dref>multipart/encrypted</dref> +</ul> + + +<h3> multipart/alternative +<node> multipart/alternative +<p> +<concept>multipart/digest</concept> is one of <dref>multipart</dref> +media types. This type is syntactically identical to +<dref>multipart/mixed</dref>, but the semantics are different. In +particular, each of the body parts is an ``alternative'' version of +the same information. +<p> +<cf node="RFC 2046"> + + +<h3> multipart/digest +<node> multipart/digest +<p> +<concept>multipart/digest</concept> is one of <dref>multipart</dref> +media types. This type is syntactically identical to +<dref>multipart/mixed</dref>, but the semantics are different. In +particular, in a digest, the default Content-Type value for a body +part is changed from <dref>text/plain</dref> to +<dref>message/rfc822</dref>. +<p> +This is the replacement of traditional <dref>RFC 1153</dref> based +<dref>encapsulation</dref>. +<p> +<cf node="RFC 2046"> + + +<h3> multipart/encrypted +<node> multipart/encrypted +<p> +RFC 1847 $B$GDj5A$5$l$?(B <dref>Security multipart</dref> $B$N#1$D$G!"0E9f2=(B +$B$5$l$?(B message $B$rI=8=$9$k$N$KMQ$$$k!#(B +<p> +<cf node="PGP/MIME"> + + +<h3> multipart/mixed +<node> multipart/mixed +<p> +Primary and default subtype of <dref>multipart</dref>, it is used when +the body parts are independent and need to be bundled in a particular +order. +<p> +<cf node="RFC 2046"> + + +<h3> multipart/parallel +<node> multipart/parallel +<p> +<concept>multipart/parallel</concept> is a subtype of +<dref>multipart</dref>. This type is syntactically identical to +<dref>multipart/mixed</dref>, but the semantics are different. In +particular, in a parallel entity, the order of body parts is not +significant. +<p> +<cf node="RFC 2046"> + + +<h3> multipart/signed +<node> multipart/signed +<p> +RFC 1847 $B$GDj5A$5$l$?(B <dref>Security multipart</dref> $B$N#1$D$G!"EE;R=p(B +$BL>$rI=8=$9$k$N$KMQ$$$k!#(B +<p> +<cf node="PGP/MIME"> + + +<h3> PGP +<node> PGP +<p> +Phil Zimmermann $B;a$,:n@.$7$?8x3+800E9f=hM}7O$N#1$D!#(B +<dref>message</dref> $B$N0E9f2=$dEE;R=pL>$r9T$&$3$H$,$G$-$k!#(BPretty Good +Privacy $B$NN,!#(B +<p> +$BEAE}E*$J(B PGP $B$G$O(B <dref>encapsulation</dref> $B$K(B <dref>RFC 934</dref>$B$K(B +$B=`$8$?J}K!$rMQ$$$k!#$3$l$O(B <dref>MIME</dref> $B$HL7=b$9$k$N$G(B +<dref>PGP/MIME</dref> $B$,Ds0F$5$l$F$$$k!#0lJ}!"(BMIME $B$K$*$$$F(B PGP $B$N(B +encapsulation $B$rMQ$$$kJ}K!(B <cf node="PGP-kazu"> $B$bMxMQ$5$l$F$-$?!#$7$+(B +$B$7!":#8e$O(B PGP/MIME $B$KE}0l$7$F$$$/J}$,K>$^$7$$!#(B +<p> +<rfc name="PGP" number="1991" type="Informational" author="D. Atkins, + W. Stallings and P. Zimmermann" title="PGP Message + Exchange Formats" date="August 1996"> + + + +<h3> PGP-kazu +<node> PGP-kazu +<p> +$B;3K\(B $BOBI'(B $B;a$,Ds0F$7$?(B <a node="MIME">MIME</a> $B$G(B <a +node="PGP">PGP</a> $B$rMxMQ$9$k$?$a$NJ}K!$r$3$3$G$O(B +<concept>PGP-kazu</concept> $B$H8F$V$3$H$K$9$k!#(B +<p> +PGP-kazu $B$O(B <concept>application/pgp</concept> $B$H$$$&(B +<dref>content-type</dref> $B$rDj5A$9$k!#(B +<p> +application/pgp $B$N(B part $B$G$O(B PGP $B$N(B <dref>encapsulation</dref> $B$,MQ$$(B +$B$i$l$k!#(BPGP $B$N(B encapsulation <cf node="RFC 934"> $B$H(B MIME $B$N(B +encapsulation $B$OL7=b$9$k$N$G!"(BPGP $B$N(B encapsulation $B$r2r$+$J$$8B$j!"Cf(B +$B$K4^$^$l$?(B MIME message $B$rFI$`$3$H$,$G$-$J$/$J$k!#B($A!"(BPGP-kazu $B$KBP(B +$B1~$7$F$$$J$$(B MIME $B$KBP1~$7$?(B <dref>MUA</dref> $B$O$=$N(B part $B$,FI$a$J$/$J(B +$B$k!#$=$NBe$o$j!"(BMIME $B$KBP1~$7$F$$$J$$(B PGP $BBP1~$N(B <dref>MUA</dref> $B$G$b(B +message $B$rFI$`$3$H$,$G$-$k!#(B +<p> +PGP-kazu $B$G$O(B MUA $B$O(B PGP $B$N$H(B MIME $B$N$H$$$$D$N(B encapsulation $B$rCN$i(B +$B$J$1$l$P$J$i$J$$!#$^$?!"(Bapplication/pgp part $B$r(B parse $B$9$k$?$a$K$O!"$^(B +$B$:!"(Bpgp $B$N=hM}$r9T$o$J$1$l$P$J$i$J$$$N$G!"(Bparse $B=hM}$,J#;($K$J$k!#(B +<p> +$B$^$?!"(BInternet $B$G$O:#8e(B <dref>PGP/MIME</dref> $B$NJ}8~$GI8=`2=$7$F$$$3$&(B +$B$H$$$&$3$H$G9g0U$,<h$l$F$$$k!#$h$C$F!":#8e$O(B PGP-kazu $B$OMQ$$$J$$$N$,K>(B +$B$^$7$$!#(B +<p> +[draft-kazu-pgp-mime-00.txt] Yamamoto K., ``PGP MIME Integration'', +October, 1995 + + +<h3> PGP/MIME +<node> PGP/MIME +<p> +Michael Elkins $B;a$,Ds0F$7$?(B <a node="MIME">MIME</a> $B$G(B <a +node="PGP">PGP</a> $B$rMxMQ$9$k$?$a$NJ}K!!#(B +<p> +<a node="Security multipart">RFC 1847</a> $B$K4p$-!"(BMIME $B$N(B multipart $B$K(B +$B$h$k(B <dref>encapsulation</dref> $B$r9T$&!#$3$N$?$a!"(BMIME $B$N<+A3$J3HD%$K(B +$B$J$C$F$$$k!#$7$+$7!"EAE}E*$J(B PGP$B$H$N8_49@-$,<:$o$l$F$$$k!#(B +<p> +PGP/MIME $B$G$O(B <dref>PGP-kazu</dref> $B$H0[$J$j!"(BMIME $B$N(B encapsulation $B$N(B +$B$_$rMQ$$$k!#$^$?!"$3$N$?$a!"(BPGP $B$N=hM}$r9T$&A0$K(B message $B$N(B parse $B$r9T(B +$B$&$3$H$,$G$-$k!#(B +<p> +Internet $B$G$O:#8e(B <dref>PGP/MIME</dref> $B$NJ}8~$GI8=`2=$7$F$$$3$&$H$$$&(B +$B$3$H$G9g0U$,<h$l$F$$$k!#$h$C$F!":#8e$O(B PGP $B$rMQ$$$k>l9g$O(B PGP/MIME$B$rMQ(B +$B$$$k$N$,K>$^$7$$!#(B + +<rfc name="PGP/MIME" number="2015" type="Standards Track" + author="M. Elkins" title="MIME Security with Pretty Good + Privacy (PGP)" date="October 1996"> + + +<h3> Quoted-Printable +<node> Quoted-Printable +<p> +<concept>Quoted-Printable</concept> is a transfer encoding method of +<dref>MIME</dref> defined in <dref>RFC 2045</dref>. +<p> +If the data being encoded are mostly US-ASCII text, the encoded form +of the data remains largely recognizable by humans. +<p> +<cf node="Base64"> + + +<h3> RFC 821 +<node> RFC 821 +<p> +<concept>SMTP</concept> $B$H8F$P$l$k(B Internet mail $B$NG[AwK!$NI8=`$rDj$a(B +$B$F$$$k(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 $B$N<g$K(B <concept>message header</concept> $B$K4X$9$k7A<0$K(B +$B4X$9$kI8=`$rDj$a$F$$$k(B RFC. + +<memo> +<p> +news message $B$b$3$l$K=`$8$F$$$k$N$G!"(B<concept>Internet mail</concept> +$B$H=q$/$h$j$b!"(B<concept>Internet message</concept> $B$H=q$$$?J}$,NI$$$+$b(B +$B$7$l$J$$!#(B +</memo> + +<rfc number="822" type="STD 11" author="D. Crocker" title="Standard + for the Format of ARPA Internet Text Messages" + date="August 1982"> + + +<h3> RFC 934 +<node> RFC 934 +<p> +<a node="RFC 822">Internet mail</a> $B$N(B <a node="encapsulation"> +<concept>encapsulation</concept></a> $B$NJ}K!$rDj$a$?(B RFC. +<p> +<dref>MIME</dref> $B$HL7=b$9$k$N$G!"8=:_$G$O(B <dref>message/rfc822</dref> +$B$rMQ$$$k$Y$-$G$"$k!#(B + + +<rfc number="934" author="Marshall T. Rose and Einar A. Stefferud" + title="Proposed Standard for Message Encapsulation" + date="January 1985"> + + +<h3> RFC 1036 +<node> RFC 1036 +<p> +USENET $B$G$N(B message $B$N7A<0$rDj$a$?(B RFC. <a node="RFC 822">RFC 822</a> +$B$N(B subset $B$K$J$C$F$$$k!#(BInternet $B$NI8=`$G$O$J$$$,!"(BUSENET $B0J30$N(B +netnews $B$G$b$3$l$K=`$8$F$$$k$b$N$,B?$$!#(B + +<rfc name="USENET" number="1036" author="M. Horton and R. Adams" + title="Standard for Interchange of USENET Messages" + date="December 1987" obsolete="850"> + + +<h3> RFC 1153 +<node> RFC 1153 +<p> +$BJ#?t$N(B <a node="RFC 822">Internet mail</a> $B$r(B <a node="encapsulation"> +<concept>encapsulation</concept></a> $B$9$k$?$a$NJ}K!$rDj$a$?(B +RFC. <dref>RFC 934</dref> $B$rMQ$$$k!#(B +<p> +<dref>MIME</dref> $B$HL7=b$9$k$N$G!"8=:_$G$O(B <dref>message/rfc822</dref> +$B$rMQ$$$?(B <dref>multipart</dref> $B$rMQ$$$k$Y$-$G$"$k!#(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> $B$H(B <dref>iso-2022-kr</dref> $B$H$$$&4Z9q8l$N$?$a$N(B +<a node="MIME charset">MIME charset</a> $B$rDj5A$7$F$$$k(B RFC. + +<rfc number="1557" type="Informational" author="U. Choi, K. Chon and + H. Park" title="Korean Character Encoding for Internet + Messages" date="December 1993"> + + +<h3> RFC 1922 +<node> RFC 1922 +<p> +<dref>iso-2022-cn</dref>, <dref>iso-2022-cn-ext</dref>, +<dref>cn-gb</dref>, <dref>cn-big5</dref> $B$H$$$C$?Cf9q8l$N$?$a$N(B <a +node="MIME charset">MIME charset</a> $B$rDj5A$7$F$$$k(B RFC. +<p> +$B$3$l$K2C$($F!"(B<concept>charset-edition</concept> $B$H(B +<concept>charset-extension</concept> $B$H$$$&(B <dref>Content-Type +field</dref> $B$N(B parameter $B$rDj5A$7$F$$$k!#(B + +<rfc number="1922" type="Informational" author="Zhu, HF., Hu, DY., + Wang, ZG., Kao, TC., Chang, WCH. and Crispin, M." + title="Chinese Character Encoding for Internet Messages" + date="March 1996"> + + +<h3> RFC 2045 +<node> RFC 2045 +<p> +<rfc number="2045" type="Standards Track" author="N. Freed and + N. Borenstein" title="Multipurpose Internet Mail + Extensions (MIME) Part One: Format of Internet Message + Bodies" date="November 1996" obsolete="1521, 1522, + 1590"> + + +<h3> RFC 2046 +<node> RFC 2046 +<p> +<rfc number="2046" type="Standards Track" author="N. Freed and + N. Borenstein" title="Multipurpose Internet Mail + Extensions (MIME) Part Two: Media Types" + date="November 1996" obsolete="1521, 1522, 1590"> + + +<h3> RFC 2048 +<node> RFC 2048 +<p> +<rfc number="2048" type="Standards Track" author="N. Freed, J. Klensin + and J. Postel" title="Multipurpose Internet Mail + Extensions (MIME) Part Four: Registration Procedures" + date="November 1996" obsolete="1521, 1522, 1590"> + + +<h3> RFC 2049 +<node> RFC 2049 +<p> +<rfc number="2049" type="Standards Track" author="N. Freed and + N. Borenstein" title="Multipurpose Internet Mail + Extensions (MIME) Part Five: Conformance Criteria and + Examples" date="November 1996" obsolete="1521, 1522, + 1590"> + + +<h3> plain text +<node> plain text +<p> +$B=qBN$dAHHG$K4X$9$k>pJs$r;}$?$J$$(B <a node="Coded character set">$BJ8;zId(B +$B9f(B</a>$B$N$_$GI=8=$5$l$k(B text $B>pJs!#(B<cf node="text/plain"> + + +<h3> Security multipart +<node> Security multipart +<p> +<a node="MIME">MIME</a> $B$G0E9f$dEE;R=qL>$rMQ$$$k$?$a$N7A<0!#(B<a +node="multipart/signed"><concept>multipart/signed</concept></a> $B$H(B <a +node="multipart/encrypted"><concept>multipart/encrypted</concept></a> +$B$H$$$&(B multipart $B$rMQ$$$k!#(BMOSS $B$d(B <a node="PGP/MIME">PGP/MIME</a> $B$O(B +$B$3$l$K4p$$$F$$$k!#(B + +<rfc name="Security multipart" number="1847" type="Standards Track" + author="James Galvin, Gale Murphy, Steve Crocker and Ned + Freed" title="Security Multiparts for MIME: + Multipart/Signed and Multipart/Encrypted" date="October + 1995"> + + +<h3> text/enriched +<node> text/enriched +<p> +RFC 1521 $B$GDj5A$5$l$?(B <concept>text/richtext</concept> $B$KBe$o$C$F!"=q(B +$BBN$dAHHG$K4X$9$k>pJs$r;}$C$?(B text$B$rI=8=$9$k$?$a$N(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> text/plain +<node> text/plain +<p> +<concept>text/plain</concept> is a <dref>media type</dref> for +<dref>plain text</dref>, defined in <dref>RFC 2046</dref>. +<p> +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 <dref>RFC 822</dref>. +<p> +<cf node="MIME charset"><cf node="us-ascii"> + + +<h3> tm-kernel, tm +<node> tm-kernel +<p> +Emacs $B$G(B <a node="MIME">MIME</a> $B$rMxMQ$9$k$?$a$N(B user interface $B$rDs(B +$B6!$9$k(B library $B72!#(B`tools for MIME' $B$NN,!#(B + +<memo title="$B$I$&$G$bNI$$$3$H(B(^-^;"> +<p> +<ul> + <li> tm $B$O(B ``tiny-mime'' $B$NN,$8$c$J$$$i$7$$$>(B (^-^; + <li> tm $B$O:n<T$N%$%K%7%c%k$8$c$J$$$i$7$$$>(B (^-^; + <li> ``Tools for MIME'' $B$NN,$H$$$&$N$O$3$8$D$1$i$7$$$>(B (^-^; +</ul> +</memo> + + +<h3> tm-MUA +<node> tm-MUA +<p> +<a node="tm-kernel">tm</a> $B$rMQ$$$?(B <a node="MUA">MUA</a> $B$b$7$/$O(B MUA +$B$KBP$9$k(B extender. +<p> +<concept>tm $BBg@9$j(B package</concept> $B$K$O(B + +<ul> +<li><a file="mh-e">mh-e</a> $BMQ$N(B <concept>tm-mh-e</concept> +<li>GNUS $BMQ$N(B <concept>tm-gnus</concept> +<li>Gnus $BMQ$N(B <a file="gnus-mime-en"><concept>gnus-mime</concept></a> +<li>VM $BMQ$N(B <concept>tm-vm</concept> +<li>RMAIL $BMQ$N(B <concept>tm-rmail</concept> +</ul> + +<noindent> +$B$,4^$^$l$F$$$k!#(B +<p> +$BFHN)$7$?(B MUA $B$H$7$F$O(B <a file="cmail">cmail</a> $B$,(B tm $B$rMxMQ2DG=$G$"$k!#(B + + +<h3> us-ascii +<node> us-ascii +<p> +$B%"%a%j%+O"K.$J$I$G;H$o$l$k1Q8l$J$I$rI=8=$9$k$?$a$N(B <a node="MIME +charset">MIME charset</a> $B$N#1$D!#(B +<p> +<dref>ASCII</dref> $B$N$_$+$i$J$j(B <dref>ISO 2022</dref> $B$K$h$k(B<a +node="Code extension">$BId9f3HD%(B</a>$B$O5v$5$l$J$$!#(B +<p> +Internet mail $B$K$*$1$kI8=`$N(B<a node="Coded character set">$BId9f2=J8;z=8(B +$B9g(B</a>$B$G$"$j!"L@<(E*$K(B MIME charset $B$,<($5$l$J$$>l9g$O86B'$H$7$F(B +<concept>us-ascii</concept> $B$,;H$o$l$k!#(B +<p> +$B$^$?!"(B<a node="RFC 822">RFC 822</a> $B$K$*$1$k(B <concept>ASCII</concept> +$B$O(B us-ascii $B$r;X$9$b$N$H2r<a$9$Y$-$G$"$k!#(B + + +<h1> Setting +<node> Setting +<p> +In the tm package, two files, <file>mime-setup.el</file> and +<file>tm-setup.el</file>, are provided to ease the setup. +<p> +The <file>mime-setup.el</file> is used for the whole MIME related +setup including MIME encoding using <file>tm-edit.el</file>, while +<file>tm-setup.el</file> is used to set up tm-MUA only. + + +<h2> Normal setting +<node> mime-setup +<p> +If you want normal setting, please use <concept>mime-setup</concept>. +For example, please insert following into <file>~/.emacs</file>: + +<lisp> +(load "mime-setup") +</lisp> + +<p> +As <file>mime-setup.el</file> loads <file>tm-setup.el</file>, you +don't need to load <file>tm-setup.el</file> when you use +<file>mime-setup.el</file> (Description of old version of Gnus FAQ is +wrong!) + + +<h3> signature +<node> signature +<p> +You can set up the <concept>automatic signature selection +tool</concept> using <file>mime-setup</file>. If you want to +automatically select the signature file depending on how the message +headers show, add lines like shown below to your .emacs (Refer to the +reference manual of <file>signature.el</file> for more details). + +<lisp> +(setq signature-file-alist + '((("Newsgroups" . "jokes") . "~/.signature-jokes") + (("Newsgroups" . ("zxr" "nzr")) . "~/.signature-sun") + (("To" . ("ishimaru" "z-suzuki")) . "~/.signature-sun") + (("To" . "tea") . "~/.signature-jokes") + (("To" . ("sim" "oku" "takuo")) . "~/.signature-formal") + )) +</lisp> + + +<defvar name="mime-setup-use-signature"> +<p> +If it is not <code>nil</code>, <file>mime-setup.el</file> sets up for +<file>signature.el</file>. Its default value is <code>t</code>. +</defvar> + + +<defvar name="mime-setup-signature-key-alist"> +<p> +It defines key to bind signature inserting command for each +major-mode. Its default value is following: + +<lisp> + ((mail-mode . "\C-c\C-w")) +</lisp> + +<p> +If you want to change, please rewrite it. For example: + +<lisp> +(set-alist 'mime-setup-signature-key-alist + 'news-reply-mode "\C-c\C-w") +</lisp> + +</defvar> + + +<defvar name="mime-setup-default-signature-key"> +<p> +If key to bind signature inserting command for a major-mode is not +found from <code>mime-setup-signature-key-alist</code>, its value is +used as key. Its default value is <code>"\C-c\C-s"</code>. +</defvar> + + +<h3> Notices for GNUS +<node> Notice about GNUS +<p> +When <file>mime-setup.el</file> sets up for <file>signature.el</file>, +it sets variable <code>gnus-signature-file</code> to <code>nil</code>. +Therefore GNUS does not insert signature automatically when it is +sending a message. Reason of this setting is following: +<p> +GNUS inserts signature after <file>tm-edit.el</file> composed as MIME +message. Therefore signature inserted by GNUS is not processed as a +valid MIME part. In particular, for multipart message, signature +places in outside of MIME part. So MIME MUA might not display it. +<p> +Other notice is key bind. In historical reason, key bind to insert +signature is <kbd>C-c C-s</kbd> (like <a file="mh-e">mh-e</a>) instead +of <kbd>C-c C-w</kbd>. If you change to GNUS's default, please set +following: + +<lisp> +(set-alist 'mime-setup-signature-key-alist 'news-reply-mode "\C-c\C-w") +</lisp> + + +<h2> Setting not to use tm-edit +<node> tm-setup +<p> +<concept>tm-setup</concept> only sets up <a node="tm-MUA">tm-MUA</a>s. +In other words, it is a setting to avoid to use tm-edit. If you don't +want to compose MIME message or want to use other MIME composer, +please use it instead of <file>mime-setup.el</file>. +<p> +For example, please insert following into <file>~/.emacs</file>: + +<lisp> +(load "tm-setup") +</lisp> + +<p> + +<memo> +<p> +If you use <file>mime-setup.el</file>, you you don't need to load +<file>tm-setup.el</file>. +</memo> + + +<h2> Setting for VM +<node> setting for VM +<p> +If you use <concept>vm</concept>, please insert following in +<file>~/.vm</file>: + +<lisp> +(require 'tm-vm) +</lisp> + + +<memo title="Notice"> +<p> +If you use <concept>BBDB</concept>, please insert <code>(require +'tm-vm)</code> <bf>after</bf> <code>(bbdb-insinuate-vm)</code>. +</memo> + + +<h2> Setting up without loading provided setup files +<node> manual setting +<p> +You may find the valuable hints in <file>mime-setup.el</file> or +<file>tm-setup.el</file> if you want to set up MIME environment +without loading the tm-provided setup files. + +<memo> +<p> +Current tm provides some convenient features to expect tm-edit, and +they can not use if <file>mime-setup.el</file> is not used. If you +want to set up original setting to use tm-edit, please declare +following setting: + +<lisp> +(provide 'mime-setup) +</lisp> + +</memo> + + +<h1> How to report bug and about mailing list of tm +<node> Bug report +<p> +If you write bug-reports and/or suggestions for improvement, please +send them to the tm Mailing List: + +<ul> +<li> Japanese <mail>bug-tm-ja@chamonix.jaist.ac.jp</mail> +<li> English <mail>bug-tm-en@chamonix.jaist.ac.jp</mail> +</ul> + +<p> +Notice that, we does not welcome bug reports about too old version. +Bugs in old version might be fixed. So please try latest version at +first. +<p> +You should write <concept>good bug report</concept>. If you write +only ``tm does not work'', we can not find such situations. At least, +you should write name, type, variants and version of OS, emacs, tm and +MUA, and setting. In addition, if error occurs, to send backtrace is +very important. <cf file="emacs" node="Bugs"> +<p> +Bug may not appear only your environment, but also in a lot of +environment (otherwise it might not bug). Therefor if you send mail +to author directly, we must write a lot of mails. So please send mail +to address for tm bugs instead of author. +<p> +Via the tm ML, you can report tm bugs, obtain the latest release of +tm, and discuss future enhancements to tm. To join the tm ML, send +e-mail to: + +<ul> +<li> Japanese <mail>tm-ja-admin@chamonix.jaist.ac.jp</mail> +<li> English <mail>tm-en-admin@chamonix.jaist.ac.jp</mail> +</ul> + +<noindent> +Since the user registration is done manually, please write the mail +body in human-recognizable language (^_^). + + +<h1> Concept Index +<node> Concept Index + +<cindex> + + +<h1> Variable Index +<node> Variable Index + +<vindex> + +</body>