1 <!doctype sinfo system>
2 <!-- $Id: tm-ja.sgml,v 6.1 1996/10/21 02:32:00 morioka Exp $ -->
4 <title>tm 7.90 Manual (English Version)
5 <author>MORIOKA Tomohiko <mail>morioka@jaist.ac.jp</mail>
15 This file documents tm, a MIME package for GNU Emacs.
21 The tm package is a set of modules to enjoy MIME on GNU Emacs. Using
25 <li> playback or view the MIME messages using tm-view
26 <li> compose MIME message using tm-edit
27 <li> use the enhanced MIME features with mh-e, GNUS, Gnus, RMAIL and VM
33 Please read following about each topics:
36 <li><a file="gnus-mime-en">tm-MUA for Gnus</a>
37 <li><a file="tm-gnus-en">tm-MUA for GNUS</a>
38 <li><a file="tm-mh-e-en">tm-MUA for mh-e</a>
39 <li><a file="tm-view-en">mime/viewer-mode</a>
40 <li><a file="tm-edit-en">mime/editor-mode</a>
50 <concept>7bit</concept> means any integer between 0 .. 127.
52 Any data represented by 7bit integers is called <concept>7bit
55 Textual string consisted of Control characters between 0 .. 31 and
56 127, and space represented by 32, and graphic characters between 33
57 .. 236 are called <concept>7bit (textual) string</concept>.
59 Traditional Internet <a node="MTA">MTA</a> can translate 7bit data, so
60 it is no need to translate by <a
61 node="Quoted-Printable">Quoted-Printable</a> or <a
62 node="Base64">Base64</a> for 7bit data.
64 However if there are too long lines, it can not translate by 7bit MTA
65 even if it is 7bit data. <dref>RFC 821</dref> and <dref>RFC
66 2045</dref> require lines in 7bit data must be less than 998 bytes.
67 So if a ``7bit data'' has a line more than 999 bytes, it is regarded
68 as <dref>binary</dref>. For example, Postscript file should be
69 encoded by Quoted-Printable.
75 <concept>8bit</concept> means any integer between 0 .. 255.
77 Any data represented by 8bit integers is called <concept>8bit
80 Textual string consisted of Control characters between 0 .. 31, 127,
81 and 128 .. 159, and space represented by 32, and graphic characters
82 between 33 .. 236 and 160 .. 255 are called <concept>8bit (textual)
85 For example, <dref>iso-8859-1</dref> or <dref>euc-kr</dref> are
86 coded-character-set represented by 8bit textual string.
88 Traditional Internet <a node="MTA">MTA</a> can translate only
89 <dref>7bit</dref> data, so if a 8bit data will be translated such MTA,
90 it must be encoded by <dref>Quoted-Printable</dref> or
93 However 8bit MTA are increasing today.
95 However if there are too long lines, it can not translate by 8bit MTA
96 even if it is 8bit data. <dref>RFC 2045</dref> require lines in 8bit
97 data must be less than 998 bytes. So if a ``8bit data'' has a line
98 more than 999 bytes, it is regarded as <dref>binary</dref>, so it must
99 be encoded by Base64 or Quoted-Printable.
102 <h3> 94-character set
103 <node> 94-character set
105 <concept>94-character set</concept> is a kind of 1 byte <dref>graphic
106 character set</dref>, each characters are in positions 02/01 (33) to
107 07/14 (126) or 10/01 (161) to 15/14 (254). (ex. <dref>ASCII</dref>,
111 <h3> 96-character set
112 <node> 96-character set
114 <concept>96-character set</concept> is a kind of 1 byte <dref>graphic
115 character set</dref>, each characters are in positions 02/00 (32) to
116 07/15 (126) or 10/00 (160) to 15/15 (255). (ex. ISO 8859)
119 <h3> 94x94-character set
120 <node> 94x94-character set
122 <concept>94x94-character set</concept> is a kind of 2 byte
123 <dref>graphic character set</dref>, each bytes are in positions 02/01
124 (33) to 07/14 (126) or 10/01 (161) to 15/14 (254). (ex. <dref>JIS
125 X0208</dref>, <dref>GB 2312</dref>)
131 \e$B%"%a%j%+O"K.$G;H$o$l$kJ8;z$rId9f2=$7$?
\e(B <dref>94-character set</dref>.
132 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
133 646">ISO 646</a>
\e$B$N0l$D!#
\e(B
135 <standard abbrev="ASCII" title-en="Coded Character Set -- 7-Bit
136 American Standard Code for Information Interchange"
137 number="ANSI X3.4" year="1986">
143 <concept>Base64</concept> is a transfer encoding method of
144 <dref>MIME</dref> defined in <dref>RFC 2045</dref>.
146 The encoding process represents 24-bit groups of input bits as output
147 strings of 4 encoded characters. Encoded characters represent integer
148 0 .. 63 or <concept>pad</concept>. Base64 data must be 4 * n bytes,
149 so pad is used to adjust size.
151 These 65 characters are subset of all versions of ISO 646, including
152 US-ASCII, and all versions of EBCDIC. So it is safe even if it is
153 translated by non-Internet gateways.
159 \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
161 <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
164 \e$B$^$?!"9T$N9=B$$,$"$C$F$b!"
\e(B999 byte
\e$B0J>e$+$i$J$k9T$,$"$k>l9g$b
\e(B binary
165 \e$B$H8F$V$3$H$K$7$^$9!#
\e(B
167 \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
168 \e$B$G$bI=8=$G$-$^$9!#$h$C$F!"
\e(B<concept>binary data</concept>
\e$B$H8@$C$?>l9g!"
\e(B
169 \e$BG$0U$N
\e(B data
\e$B$r;X$9$3$H$,$"$j$^$9!#
\e(B
172 <h3> Graphic Character Set
173 <node> graphic character set
175 <dref>Coded character set</dref> for graphic characters.
181 \e$BCf9qBgN&$G$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N
\e(B <a
182 node="MIME charset">MIME charset</a>
\e$B$N#1$D!#
\e(B
184 <dref>ISO 2022</dref>
\e$B$K4p$$$F
\e(B <dref>ASCII</dref>
\e$B$K
\e(B <dref>GB
185 2312</dref>
\e$B$r
\e(B <dref>8bit</dref>
\e$B$G
\e(B<a node="Code extension">
\e$BId9f
\e(B
186 \e$B3HD%
\e(B</a>
\e$B$7$F$$$k!#
\e(B
188 <a node="RFC 1922">RFC 1922</a>
\e$B$GDj5A$5$l$F$$$k!#
\e(B
194 \e$BBfOQ$d9a9A$GMQ$$$i$l$F$$$k<g$KHKBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N
\e(B
195 <a node="MIME charset">MIME charset</a>
\e$B$N#1$D!#
\e(B
197 <dref>ISO 2022</dref>
\e$B$K4p$+$J$$
\e(B <dref>8bit</dref>
\e$B$N
\e(B
198 <dref>coded character set</dref>
\e$B$G
\e(B de-fact standard
\e$B$G
\e(B
199 \e$B$"$k!#
\e(B<a node="RFC 1922">RFC 1922</a>
\e$B$GDj5A$5$l$F$$$k!#
\e(B
201 cf. <report abbrev="BIG5" author="Institute for Information Industry"
202 title-en="Chinese Coded Character Set in Computer"
205 <a node="CNS">CNS 11643-1986</a>
\e$B$HBP1~4X78$,$"$k!#
\e(B
211 \e$BBfOQ$d9a9A$GMQ$$$i$l$F$$$k<g$KHKBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N
\e(B
212 <a node="Character set">
\e$BJ8;z=89g
\e(B</a>
\e$B!#BfOQ$NI8=`!#8=:_!"
\e(B<a node="94x94
213 character set">94
\e$B!_
\e(B94</a>
\e$B$NLL$,Bh#1LL$+$iBh#7LL$^$G$"$k!#
\e(B
215 <dref>ISO 2022</dref>
\e$B$G$N=*C<J8;z$O!"Bh#1LL$,
\e(B `G',
\e$BBh#2LL$,
\e(B
216 `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
219 <standard abbrev="CNS 11643-1992" title-en="Standard Interchange Code
220 for Generally-Used Chinese Characters" number="CNS
224 <h3> Coded character set, Character code
225 <node> coded character set
227 A set of unambiguous rules that establishes a character set and the
228 one-to-one relationship between the characters of the set and their
233 <node> code extension
235 The techniques for the encoding of characters that are not included in
236 the character set of a given code. (ex. <dref>ISO 2022</dref>)
239 <h3> Content-Disposition field
240 <node> Content-Disposition
242 Content
\e$B$NI=<($N;EJ}$d
\e(B file
\e$BL>$rI=8=$9$k$?$a$N
\e(B field. <a
243 node="MIME">MIME</a>
\e$B$N3HD%$N#1$D!#
\e(B
245 <rfc number="1806" type="Experimental" author="E R. Troost and
246 S. Dorner" title="Communicating Presentation Information
247 in Internet Messages: The Content-Disposition Header"
254 <concept>media type</concept> specifies the nature of the data in the
255 body of <dref>MIME</dref> <dref>entity</dref>. It consists of
256 <concept>type</> and <concept>subtype</concept>. It is defined in
257 <dref>RFC 2046</dref>.
259 Currently there are following types:
262 <li><concept>text</concept>
264 <li><concept>image</concept>
266 <li><concept>audio</concept>
268 <li><concept>video</concept>
270 <li><concept>application</concept>
272 <li><a node="multipart"><concept>multipart</concept></a>
274 <li><concept>message</concept>
278 And there are various subtypes, for example, application/octet-stream,
279 audio/basic, image/jpeg, <dref>multipart/mixed</dref>,
280 <dref>text/plain</dref>, video/mpeg...
282 You can refer registered media types at <a
283 href="ftp://ftp.isi.edu/in-notes/iana/assignments/media-types">MEDIA
286 In addition, you can use private type or subtype using
287 <concept>x-token</concept>, which as the prefix `x-'. However you can
288 not use them in public.
290 <cf node="Content-Type field">
293 <h3> Content-Type field
294 <node> Content-Type field
296 Header field to represent information about body, such as <dref>media
297 type</dref>, <dref>MIME charset</dref>. It is defined in <dref>RFC
302 Historically, Content-Type field was proposed in RFC 1049. In it,
303 Content-Type did not distinguish type and subtype. However MIME
304 parser may be able to accept RFC 1049 based Content-Type as unknown
309 Content-Type field is defined as following:
312 ``Content-Type'' ``:'' <concept>type</concept> ``/''
313 <concept>subtype</concept> *( ``;'' <concept>parameter</concept> )
321 Content-Type: image/jpeg
327 Content-Type: text/plain; charset=iso-2022-jp
333 A part does not have content-type field is regarded as
337 Content-Type: text/plain; charset=us-ascii
344 And a part has unknown type/subtype is regarded as
348 Content-Type: application/octet-stream
358 \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
359 GNU Emacs
\e$B$NJQ<o$NAm>N$H$9$k!#
\e(B
365 Representation non <dref>ASCII</dref> characters in header. It
366 is defined in <concept>RFC 2047</concept>.
368 <rfc number="2047" type="Standards Track" author="K. Moore"
369 title="MIME (Multipurpose Internet Mail Extensions) Part
370 Three: Message Header Extensions for Non-ASCII Text"
371 date="November 1996" obsolete="1521,1522,1590">
377 <a node="RFC 822">Internet mail</a>
\e$B$rB>$N5-;v$K$^$k$4$HF~$l$kJ}K!!#
\e(B
379 \e$BNc$($P!"5-;v$rE>Aw$7$?$j$9$k$N$KMQ$$$k!#
\e(B
381 <cf node="message/rfc822">
387 \e$B4Z9q8l$rI=8=$9$k$?$a$N
\e(B <a node="MIME charset">MIME charset</a>
\e$B$N#1$D!#
\e(B
389 <dref>ISO 2022</dref>
\e$B$K4p$$$F
\e(B <dref>ASCII</dref>
\e$B$K
\e(B
390 <a node="KS C5601">KS C5601</a>
\e$B$r
\e(B <dref>8bit</dref>
\e$B$G
\e(B<a
391 node="Code extension">
\e$BId9f3HD%
\e(B</a>
\e$B$7$F$$$k!#
\e(B
393 <a node="RFC 1557">RFC 1557</a>
\e$B$GDj5A$5$l$F$$$k!#
\e(B
395 cf. <standard abbrev="euc-kr" org="Korea Industrial Standards
396 Association" title-en="Hangul Unix Environment"
397 number="KS C 5861" year="1992">
402 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
405 <rfc name="FTP" number="959" type="STD 9" author="Postel, J. and
406 J. Reynolds" title="File Transfer Protocol"
413 \e$BCf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=$9$?$a$N
\e(B
414 <dref>94x94-character set</dref>
\e$B!#Cf9q$N9q2HI8=`!#
\e(B<a node="ISO
415 2022">ISO 2022</a>
\e$B$G$N=*C<J8;z$O
\e(B `A'.
417 \e$B$3$l$O
\e(B GB
\e$B$K$*$1$k4pK\=8$G$"$k!#
\e(B
419 <standard abbrev="GB 2312"
420 title-cn="
\e$B?.B)8r49MQ4A;zJTb{;zId=8
\e(B --
\e$B4pK\=8
\e(B"
421 title-en="Code of Chinese Graphic Character Set for
422 Information Interchange - Primary Set" number="GB 2312"
429 \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
430 <a node="GB 2312">GB 2312</a>
\e$B$N6u$-ItJ,$KJd=<$9$k$h$&$KDj5A$5$l$?$i$7
\e(B
433 <standard abbrev="GB 8565.2" title-en="Information Processing - Coded
434 Character Sets for Text Communication - Part 2: Graphic
435 Characters used with Primary Set" number="GB 8565.2"
442 \e$BCf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N
\e(B <a
443 node="MIME charset">MIME charset</a>
\e$B$N#1$D!#
\e(B
445 <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
446 <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
447 \e$B$h$&$K9)IW$7$F$$$k!#
\e(B
449 RFC 1842, 1843
\e$B$GDj5A$5$l$F$$$k!#
\e(B
451 <rfc number="1842" type="Informational" author="Y. Wei, Y. Zhang,
452 J. Li, J. Ding and Y. Jiang" title="ASCII Printable
453 Characters-Based Chinese Character Encoding for Internet
454 Messages" date="August 1995">
455 <rfc number="1843" type="Informational" author="F. Lee" title="HZ - A
456 Data Format for Exchanging Files of Arbitrarily Mixed
457 Chinese and ASCII characters" date="August 1995">
463 <a node="Code extension">
\e$BId9f3HD%
\e(B</a>
\e$B$N$?$a$N9q:]I8=`!#
\e(B
465 \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
466 node="7bit">7bit</a>
\e$B$J$$$7
\e(B <dref>8bit</dref>
\e$B$N
\e(B <a node="Coded
467 character set">
\e$BId9f2=J8;z=89g
\e(B</a>
\e$B$r:n$k$3$H$,$G$-$k!#
\e(B
469 <standard abbrev="ISO 2022" org="International Organization for
470 Standardization (ISO)" title-en="Information Processing:
471 ISO 7-bit and 8-bit coded character sets: Code extension
472 techniques" number="ISO/IEC 2022" year="1994">
478 \e$BCf9q8l$rI=8=$9$k$?$a$N
\e(B <a node="MIME charset">MIME charset</a>
\e$B$N#1$D!#
\e(B
480 <dref>ISO 2022</dref>
\e$B$K4p$$$F
\e(B <dref>ASCII</dref>
\e$B$K
\e(B
481 <a node="GB 2312">GB 2312</a>, <a node="CNS">CNS 11643 plain 1, plain
482 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
483 </a>
\e$B$7$F$$$k!#
\e(B
485 <a node="RFC 1922">RFC 1922</a>
\e$B$GDj5A$5$l$F$$$k!#
\e(B
489 <node> iso-2022-cn-ext
491 \e$BCf9q8l$rI=8=$9$k$?$a$N
\e(B <a node="MIME charset">MIME charset</a>
\e$B$N#1$D!#
\e(B
493 <dref>ISO 2022</dref>
\e$B$K4p$$$F
\e(B <dref>ASCII</dref>
\e$B$K
\e(B
494 <a node="GB 2312">GB 2312</a>, <a node="CNS">CNS 11643 plain 1
495 .. 7</a>, <a node="ISO-IR-165">ISO-IR-165</a>
\e$BEy$r
\e(B <a
496 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
498 <a node="RFC 1922">RFC 1922</a>
\e$B$GDj5A$5$l$F$$$k!#
\e(B
501 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
503 Emacs/mule
\e$B$G$OMxMQ2DG=$G$"$k!#
\e(B
510 \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
512 \e$B8E$$
\e(B <dref>ISO 2022</dref>
\e$B$K4p$$$F
\e(B <a
513 node="ASCII">ASCII</a>, JIS X0201-Latin, <a node="JIS C6226-1978">JIS
514 X0208-1978</a>, <a node="JIS X0208">JIS X0208-1983</a>
\e$B$r@Z$jBX$($k
\e(B <a
515 node="7bit">7bit</a>
\e$BJ8;zId9f!#
\e(B
517 RFC 1468
\e$B$GDj5A$5$l$F$$$k!#
\e(B
520 JIS X0208-1996?
\e$B$G$O
\e(B <dref>ISO 2022</dref>
\e$B$HFHN)$KDj5A$5$l
\e(B
524 <rfc name="iso-2022-jp" number="1468" author="Murai J., M. Crispin,
525 and E. van der Poel" title="Japanese Character Encoding
526 for Internet Messages" date="June 1993">
532 A <dref>MIME charset</dref>, which is a multilingual extension of
533 <dref>iso-2022-jp</dref>.
535 It is defined in RFC 1554.
537 <rfc name="iso-2022-jp-2" number="1554" type="Informational"
538 author="Ohta M. and Handa K." title="ISO-2022-JP-2:
539 Multilingual Extension of ISO-2022-JP" date="December
546 A <a node="MIME charset">MIME charset</a> for Korean language (Hangul
549 It is based on <dref>ISO 2022</dref> <dref>code extension</dref>
550 technique to extends <dref>ASCII</dref> to use <dref>KS C5601</dref>
551 as <dref>7bit</dref> text.
553 It is defined in <dref>RFC 1557</dref>.
559 \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
560 \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
561 \e$B!J9q:]4p=`HG!K$r85$K4v$D$+$NJ8;z$O3F9q$G0c$&J8;z$r3dEv$k$3$H$r5v$7$F$$
\e(B
562 \e$B$F!"4v$D$+$NJQ<o$,B8:_$9$k!#
\e(B<dref>ASCII</dref>
\e$B$d
\e(B JIS
563 X0201-Latin
\e$B$O$=$N0l<o!#
\e(B
565 <standard abbrev="ISO 646" org="International Organization for
566 Standardization (ISO)" title-en="Information technology:
567 ISO 7-bit coded character set for information
568 interchange" number="ISO/IEC 646" year="1991">
574 <standard abbrev="ISO 8859-1" org="International Organization for
575 Standardization (ISO)" title-en="Information Processing
576 -- 8-bit Single-Byte Coded Graphic Character Sets --
577 Part 1: Latin Alphabet No.1" number="ISO 8859-1"
584 <concept>iso-8859-1</concept> is a <dref>MIME charset</dref> for
585 west-European languages written by Latin script.
587 <dref>ISO 2022</dref>
\e$B$K4p$$$F!"
\e(B<dref>ASCII</dref>
\e$B$K
\e(B
588 <a node="ISO 8859-1">ISO 8859-1</a>
\e$B$r
\e(B <dref>8bit</dref>
\e$B$G
\e(B<a
589 node="Code extension">
\e$BId9f3HD%
\e(B</a>
\e$B$7$F$$$k!#
\e(B
591 It is defined in <dref>RFC 2046</dref>.
597 <standard abbrev="ISO 8859-2" org="International Organization for
598 Standardization (ISO)" title-en="Information Processing
599 -- 8-bit Single-Byte Coded Graphic Character Sets --
600 Part 2: Latin alphabet No.2" number="ISO 8859-2"
607 <concept>iso-8859-2</concept> is a <dref>MIME charset</dref> for
608 east-European languages written by Latin script.
610 <dref>ISO 2022</dref>
\e$B$K4p$$$F!"
\e(B<dref>ASCII</dref>
\e$B$K
\e(B
611 <a node="ISO 8859-2">ISO 8859-2</a>
\e$B$r
\e(B <dref>8bit</dref>
\e$B$G
\e(B<a
612 node="Code extension">
\e$BId9f3HD%
\e(B</a>
\e$B$7$F$$$k!#
\e(B
614 It is defined in <dref>RFC 2046</dref>.
620 <standard abbrev="ISO 8859-3" org="International Organization for
621 Standardization (ISO)" title-en="Information
622 Processing -- 8-bit Single-Byte Coded Graphic
623 Character Sets -- Part 3: Latin alphabet No.3"
624 number="ISO 8859-3" year="1988">
630 <standard abbrev="ISO 8859-4" org="International Organization for
631 Standardization (ISO)" title-en="Information
632 Processing -- 8-bit Single-Byte Coded Graphic
633 Character Sets -- Part 4: Latin alphabet No.4"
634 number="ISO 8859-4" year="1988">
640 <standard abbrev="ISO 8859-5" org="International Organization for
641 Standardization (ISO)" title-en="Information Processing
642 -- 8-bit Single-Byte Coded Graphic Character Sets --
643 Part 5: Latin/Cyrillic alphabet" number="ISO 8859-5"
650 <concept>iso-8859-5</concept> is a <dref>MIME charset</dref> for
653 <dref>ISO 2022</dref>
\e$B$K4p$$$F!"
\e(B<dref>ASCII</dref>
\e$B$K
\e(B
654 <a node="ISO 8859-5">ISO 8859-5</a>
\e$B$r
\e(B <dref>8bit</dref>
\e$B$G
\e(B<a
655 node="Code extension">
\e$BId9f3HD%
\e(B</a>
\e$B$7$F$$$k!#
\e(B
657 It is defined in <dref>RFC 2046</dref>.
663 <standard abbrev="ISO 8859-6" org="International Organization for
664 Standardization (ISO)" title-en="Information
665 Processing -- 8-bit Single-Byte Coded Graphic
666 Character Sets -- Part 6: Latin/Arabic alphabet"
667 number="ISO 8859-6" year="1987">
673 <standard abbrev="ISO 8859-7" org="International Organization for
674 Standardization (ISO)" title-en="Information Processing
675 -- 8-bit Single-Byte Coded Graphic Character Sets --
676 Part 7: Latin/Greek alphabet" number="ISO 8859-7"
683 <concept>iso-8859-7</concept> is a <dref>MIME charset</dref> for
686 <dref>ISO 2022</dref>
\e$B$K4p$$$F!"
\e(B<dref>ASCII</dref>
\e$B$K
\e(B
687 <a node="ISO 8859-7">ISO 8859-7</a>
\e$B$r
\e(B <dref>8bit</dref>
\e$B$G
\e(B<a
688 node="Code extension">
\e$BId9f3HD%
\e(B</a>
\e$B$7$F$$$k!#
\e(B
690 It is defined in RFC 1947.
692 <rfc name="iso-8859-7" number="1947" type="Informational"
693 author="D. Spinellis" title="Greek Character Encoding
694 for Electronic Mail Messages" date="May 1996">
700 <standard abbrev="ISO 8859-8" org="International Organization for
701 Standardization (ISO)" title-en="Information
702 Processing -- 8-bit Single-Byte Coded Graphic
703 Character Sets -- Part 8: Latin/Hebrew alphabet"
704 number="ISO 8859-8" year="1988">
710 <standard abbrev="ISO 8859-9" org="International Organization for
711 Standardization (ISO)" title-en="Information
712 Processing -- 8-bit Single-Byte Coded Graphic
713 Character Sets -- Part 9: Latin alphabet No.5"
714 number="ISO 8859-9" year="1990">
717 <h3> ISO-IR-165, CCITT Extended GB <node> ISO-IR-165
719 CCITT
\e$B$,EPO?$7$?!"Cf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=
\e(B
720 \e$B8=$9$k$?$a$N
\e(B <dref>94x94-character set</dref>
\e$B!#
\e(B
722 <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>
723 \e$B$K
\e(B 150
\e$BJ8;z$[$I$rDI2C$7$?$b$N$i$7$$!#
\e(B
725 <dref>ISO 2022</dref>
\e$B$G$N=*C<J8;z$O
\e(B `E'
\e$B$G$"$k!#
\e(B
731 <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
732 byte
\e$B$N%+%?%+%JJ8;z=89g$+$i$J$k!#
\e(B
734 \e$B85$O
\e(B <concept>JIS C6220-1976</concept>
\e$B$H8@$C$?$,
\e(B <concept>JIS
735 X0201</concept>
\e$B$KHV9f$,JQ99$5$l$?!#
\e(B
737 <standard abbrev="JIS X0201-1976" org="
\e$BF|K\5,3J6(2q
\e(B (Japanese
738 Standards Association)" title-ja="
\e$B>pJs8r49MQId9f
\e(B"
739 title-en="Code for Information Interchange" number="JIS
742 \e$B$^$?!"
\e(B1996
\e$BG/$K2~DjHG$,=P$kM=Dj!#
\e(B
744 <standard abbrev="JIS X0201-1996?" org="
\e$BF|K\5,3J6(2q
\e(B (Japanese
745 Standards Association)"
746 title-ja="
\e$B#7%S%C%H5Z$S#8%S%C%H$N>pJs8r49MQId9f2=J8;z=89g
\e(B"
747 title-en="7-bit and 8-bit coded character sets for
748 information interchange" number="JIS X 0201" year="1996?
755 \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
756 \e$B2HI8=`!#
\e(BJIS X0208-1978
\e$B$H$b$$$&!#
\e(B
758 <cf node="JIS X0208">
764 \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
765 \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
766 \e$BHG$,$b$C$H$bNI$/;H$o$l$F$$$k!#
\e(B
768 JIS X0208
\e$B$O5-9f!"?t;z!"%m!<%^;z!"$R$i$,$J!"%+%?%+%J!"%.%j%7%cJ8;z!"%-
\e(B
769 \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
770 \e$B$N0lIt$N5-9f$H7S@~AG$O
\e(B 1978
\e$BG/HG$K$O$J$$!#$^$?!"0lIt$N4A;z$N;z7A$,
\e(B
771 1983
\e$BG/HG$G$OJQ99$5$l!"$^$?!"Bh#1?e=`$HBh#2?e=`$,F~$lBX$o$C$F$$$?$j$9
\e(B
772 \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
774 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
775 \e$B$r;X<($9$k>l9g$OA0$K99?7%7!<%1%s%9$rMQ$$$k!#
\e(B
777 <standard abbrev="JIS X0208-1978" org="
\e$BF|K\5,3J6(2q
\e(B (Japanese Standards
778 Association)" title-ja="
\e$B>pJs8r49MQ4A;zId9f7O
\e(B"
779 title-en="Code of the Japanese graphic character set for
780 information interchange" number="JIS C6226" year="1978">
781 <standard abbrev="JIS X0208-1983,1990" org="
\e$BF|K\5,3J6(2q
\e(B (Japanese Standards
782 Association)" title-ja="
\e$B>pJs8r49MQ4A;zId9f7O
\e(B"
783 title-en="Code of the Japanese graphic character set for
784 information interchange" number="JIS X0208" year="1983,1990">
787 \e$B$^$?!"
\e(B1996
\e$BG/$K2~DjHG$,=PHG$5$l$kM=Dj!#!J;z7A$NJQ99$O9T$o$l$J$$$N$GJ8
\e(B
788 \e$B;z=89g$H$7$F$O
\e(B 1990
\e$BG/HG$HF10l$G$"$k!K
\e(B
790 <standard abbrev="JIS X0208-1996?" org="
\e$BF|K\5,3J6(2q
\e(B (Japanese
791 Standards Association)" title-ja="
\e$B#7%S%C%H5Z$S#8%S%C%H$N
\e(B
792 \e$B#2%P%$%H>pJs8r49MQId9f2=4A;z=89g
\e(B" title-en="7-bit and
793 8-bit double byte coded Kanji sets for information
794 interchange" number="JIS X 0208" year="1996? draft">
800 <a node="JIS X0208">JIS X0208</a>
\e$B$K$J$+$C$?J8;z$r=8$a$?
\e(B
801 <dref>94x94-character set</dref>
\e$B!#!VJd=u4A;z!W$H$b8F$P$l$k!#F|K\$N9q2H
\e(B
802 \e$BI8=`!#
\e(B<dref>ISO 2022</dref>
\e$B$G$N=*C<J8;z$O
\e(B `D'.
808 A <dref>MIME charset</dref> for Cyrillic script for Russian or other
811 It is a 1 byte <dref>8bit</dref> <dref>coded character set</dref>, not
812 based on <dref>ISO 2022</dref>. It is a de-fact standard.
814 It is defined in RFC 1489.
816 <rfc number="1489" author="A. Chernov" title="Registration of a
817 Cyrillic Character Set" date="July 1993">
823 A <dref>94x94-character set</dref> for Korean language (Hangul
824 script). Korean Standard. Final byte of <dref>ISO 2022</dref> is
827 <standard abbrev="KS C5601" org="Korea Industrial Standards
828 Association" title-en="Code for Information Interchange
829 (Hangul and Hanja)" number="KS C 5601" year="1987">
835 \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
836 1036</dref>
\e$B$GDj5A$5$l$k
\e(B news
\e$B5-;v$NAm>N$H$7$FMQ$$$k!#
\e(B
840 <node> message/rfc822
842 <concept>message/rfc822</concept> indicates that the body contains an
843 encapsulated message, with the syntax of an <dref>RFC 822</dref>
844 message. It is the replacement of traditional <dref>RFC 934</dref>
845 encapsulation. It is defined in <dref>RFC 2046</dref>.
851 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
852 program. Emacs Lisp
\e$B$G=q$+$l$?
\e(B <concept>internal method</concept>
\e$B$H
\e(B C
853 \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
855 <cf file="tm-view-en" node="method">
861 MIME stands for <concept>Multipurpose Internet Mail
862 Extensions</concept>, it is an extension for <dref>RFC 822</dref>.
864 According to RFC 2045:
866 STD 11, RFC 822, defines a message representation protocol specifying
867 considerable detail about US-ASCII message headers, and leaves the
868 message content, or message body, as flat US-ASCII text. This set of
869 documents, collectively called the Multipurpose Internet Mail
870 Extensions, or MIME, redefines the format of messages to allow for
873 <li>textual message bodies in character sets other than US-ASCII,
875 <li>an extensible set of different formats for non-textual message
878 <li>multi-part message bodies, and
880 <li>textual header information in character sets other than US-ASCII.
884 It is defined in <dref>RFC 2045</dref>, <dref>RFC 2046</dref>, <a
885 node="encoded-word">RFC 2047</a>, <dref>RFC 2048</dref> and <dref>RFC
892 <dref>Coded character set</dref> used in <dref>Content-Type
893 field</dref> or charset parameter of <a
894 node="encoded-word">encoded-word</a>.
896 It is defined in <dref>RFC 2045</dref>.
898 <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
899 \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
900 \e$B$7$F>.J8;z$G=q$$$F$$$k!K
\e(B
906 <concept>Message Transfer Agent</concept>
\e$B$NN,$G!"
\e(Bsendmail
\e$B$J$I$N
\e(B mail
907 \e$BG[Aw
\e(B program
\e$B$H
\e(B news server
\e$B$NAm>N!#
\e(B
915 <concept>Message User Agent</concept>
\e$B$NN,$G!"
\e(Bmail reader
\e$B$H
\e(B news
916 reader
\e$B$NAm>N!#
\e(B
924 \e$BH>ED
\e(B
\e$B7u0l;a$i$,:n$C$?!"B?8@8l$5$l$?
\e(B <a node="Emacs">Emacs</a>.
926 [MULE] Nishikimi M., Handa K. and Tomura S., ``Mule: MULtilingual
927 Enhancement to GNU Emacs'', Proc. of INET'93, August, 1993.
929 \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
930 href="ftp://etlport.etl.go.jp/pub/mule/mule-19.33-gamma.taz"> alpha
\e$BHG
\e(B
931 </a>
\e$B$,B8:_$9$k!#
\e(B
933 \e$B$=$NB>!"
\e(BXEmacs
\e$B$K
\e(B merge
\e$B$7$?$b$N$bB8:_$9$k!#
\e(B
935 \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
938 \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
939 \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
940 <concept>Emacs/mule</concept>, mule
\e$B5!G=$r
\e(B merge
\e$B$7$?
\e(B XEmacs
\e$B$r
\e(B
941 <concept>XEmacs/mule</concept>
\e$B$H8F$V$3$H$K$9$k!#
\e(B
947 <concept>multipart</concept> means <dref>media type</dref> to insert
948 multiple <dref>entities</dref> in a single body. Or it also indicates
949 a message consists of multiple entities.
951 There are following subtypes registered in <dref>RFC 2046</dref>:
954 <li><dref>multipart/mixed</dref>
955 <li><dref>multipart/alternative</dref>
956 <li><dref>multipart/digest</dref>
957 <li><dref>multipart/parallel</dref>
961 and registered in <a node="Security multipart">RFC 1847</a>:
964 <li><dref>multipart/signed</dref>
965 <li><dref>multipart/encrypted</dref>
969 <h3> multipart/alternative
970 <node> multipart/alternative
972 <concept>multipart/digest</concept> is one of <dref>multipart</dref>
973 media types. This type is syntactically identical to
974 <dref>multipart/mixed</dref>, but the semantics are different. In
975 particular, each of the body parts is an ``alternative'' version of
976 the same information.
981 <h3> multipart/digest
982 <node> multipart/digest
984 <concept>multipart/digest</concept> is one of <dref>multipart</dref>
985 media types. This type is syntactically identical to
986 <dref>multipart/mixed</dref>, but the semantics are different. In
987 particular, in a digest, the default Content-Type value for a body
988 part is changed from <dref>text/plain</dref> to
989 <dref>message/rfc822</dref>.
991 This is the replacement of traditional <dref>RFC 1153</dref> based
992 <dref>encapsulation</dref>.
997 <h3> multipart/encrypted
998 <node> multipart/encrypted
1000 RFC 1847
\e$B$GDj5A$5$l$?
\e(B <dref>Security multipart</dref>
\e$B$N#1$D$G!"0E9f2=
\e(B
1001 \e$B$5$l$?
\e(B message
\e$B$rI=8=$9$k$N$KMQ$$$k!#
\e(B
1003 <cf node="PGP/MIME">
1006 <h3> multipart/mixed
1007 <node> multipart/mixed
1009 Primary and default subtype of <dref>multipart</dref>, it is used when
1010 the body parts are independent and need to be bundled in a particular
1013 <cf node="RFC 2046">
1016 <h3> multipart/parallel
1017 <node> multipart/parallel
1019 <concept>multipart/parallel</concept> is a subtype of
1020 <dref>multipart</dref>. This type is syntactically identical to
1021 <dref>multipart/mixed</dref>, but the semantics are different. In
1022 particular, in a parallel entity, the order of body parts is not
1025 <cf node="RFC 2046">
1028 <h3> multipart/signed
1029 <node> multipart/signed
1031 RFC 1847
\e$B$GDj5A$5$l$?
\e(B <dref>Security multipart</dref>
\e$B$N#1$D$G!"EE;R=p
\e(B
1032 \e$BL>$rI=8=$9$k$N$KMQ$$$k!#
\e(B
1034 <cf node="PGP/MIME">
1040 Phil Zimmermann
\e$B;a$,:n@.$7$?8x3+800E9f=hM}7O$N#1$D!#
\e(B
1041 <dref>message</dref>
\e$B$N0E9f2=$dEE;R=pL>$r9T$&$3$H$,$G$-$k!#
\e(BPretty Good
1042 Privacy
\e$B$NN,!#
\e(B
1044 \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
1045 \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
1046 <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
1047 encapsulation
\e$B$rMQ$$$kJ}K!
\e(B <cf node="PGP-kazu">
\e$B$bMxMQ$5$l$F$-$?!#$7$+
\e(B
1048 \e$B$7!":#8e$O
\e(B PGP/MIME
\e$B$KE}0l$7$F$$$/J}$,K>$^$7$$!#
\e(B
1050 <rfc name="PGP" number="1991" type="Informational" author="D. Atkins,
1051 W. Stallings and P. Zimmermann" title="PGP Message
1052 Exchange Formats" date="August 1996">
1059 \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
1060 node="PGP">PGP</a>
\e$B$rMxMQ$9$k$?$a$NJ}K!$r$3$3$G$O
\e(B
1061 <concept>PGP-kazu</concept>
\e$B$H8F$V$3$H$K$9$k!#
\e(B
1063 PGP-kazu
\e$B$O
\e(B <concept>application/pgp</concept>
\e$B$H$$$&
\e(B
1064 <dref>content-type</dref>
\e$B$rDj5A$9$k!#
\e(B
1066 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
1067 \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
1068 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
1069 \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
1070 \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
1071 \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
1072 message
\e$B$rFI$`$3$H$,$G$-$k!#
\e(B
1074 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
1075 \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
1076 \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
1078 \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
1079 \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
1082 [draft-kazu-pgp-mime-00.txt] Yamamoto K., ``PGP MIME Integration'',
1089 Michael Elkins
\e$B;a$,Ds0F$7$?
\e(B <a node="MIME">MIME</a>
\e$B$G
\e(B <a
1090 node="PGP">PGP</a>
\e$B$rMxMQ$9$k$?$a$NJ}K!!#
\e(B
1092 <a node="Security multipart">RFC 1847</a>
\e$B$K4p$-!"
\e(BMIME
\e$B$N
\e(B multipart
\e$B$K
\e(B
1093 \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
1094 \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
1096 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
1097 \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
1098 \e$B$&$3$H$,$G$-$k!#
\e(B
1100 Internet
\e$B$G$O:#8e
\e(B <dref>PGP/MIME</dref>
\e$B$NJ}8~$GI8=`2=$7$F$$$3$&$H$$$&
\e(B
1101 \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
1102 \e$B$$$k$N$,K>$^$7$$!#
\e(B
1104 <rfc name="PGP/MIME" number="2015" type="Standards Track"
1105 author="M. Elkins" title="MIME Security with Pretty Good
1106 Privacy (PGP)" date="October 1996">
1109 <h3> Quoted-Printable
1110 <node> Quoted-Printable
1112 <concept>Quoted-Printable</concept> is a transfer encoding method of
1113 <dref>MIME</dref> defined in <dref>RFC 2045</dref>.
1115 If the data being encoded are mostly US-ASCII text, the encoded form
1116 of the data remains largely recognizable by humans.
1124 <concept>SMTP</concept>
\e$B$H8F$P$l$k
\e(B Internet mail
\e$B$NG[AwK!$NI8=`$rDj$a
\e(B
1127 <rfc name="SMTP" number="821" type="STD 10" author="J. Postel"
1128 title="Simple Mail Transfer Protocol" date="August
1135 Internet mail
\e$B$N<g$K
\e(B <concept>message header</concept>
\e$B$K4X$9$k7A<0$K
\e(B
1136 \e$B4X$9$kI8=`$rDj$a$F$$$k
\e(B RFC.
1140 news message
\e$B$b$3$l$K=`$8$F$$$k$N$G!"
\e(B<concept>Internet mail</concept>
1141 \e$B$H=q$/$h$j$b!"
\e(B<concept>Internet message</concept>
\e$B$H=q$$$?J}$,NI$$$+$b
\e(B
1145 <rfc number="822" type="STD 11" author="D. Crocker" title="Standard
1146 for the Format of ARPA Internet Text Messages"
1153 <a node="RFC 822">Internet mail</a>
\e$B$N
\e(B <a node="encapsulation">
1154 <concept>encapsulation</concept></a>
\e$B$NJ}K!$rDj$a$?
\e(B RFC.
1156 <dref>MIME</dref>
\e$B$HL7=b$9$k$N$G!"8=:_$G$O
\e(B <dref>message/rfc822</dref>
1157 \e$B$rMQ$$$k$Y$-$G$"$k!#
\e(B
1160 <rfc number="934" author="Marshall T. Rose and Einar A. Stefferud"
1161 title="Proposed Standard for Message Encapsulation"
1162 date="January 1985">
1168 USENET
\e$B$G$N
\e(B message
\e$B$N7A<0$rDj$a$?
\e(B RFC. <a node="RFC 822">RFC 822</a>
1169 \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
1170 netnews
\e$B$G$b$3$l$K=`$8$F$$$k$b$N$,B?$$!#
\e(B
1172 <rfc name="USENET" number="1036" author="M. Horton and R. Adams"
1173 title="Standard for Interchange of USENET Messages"
1174 date="December 1987" obsolete="850">
1180 \e$BJ#?t$N
\e(B <a node="RFC 822">Internet mail</a>
\e$B$r
\e(B <a node="encapsulation">
1181 <concept>encapsulation</concept></a>
\e$B$9$k$?$a$NJ}K!$rDj$a$?
\e(B
1182 RFC. <dref>RFC 934</dref>
\e$B$rMQ$$$k!#
\e(B
1184 <dref>MIME</dref>
\e$B$HL7=b$9$k$N$G!"8=:_$G$O
\e(B <dref>message/rfc822</dref>
1185 \e$B$rMQ$$$?
\e(B <dref>multipart</dref>
\e$B$rMQ$$$k$Y$-$G$"$k!#
\e(B
1187 <cf node="multipart/digest">
1189 <rfc number="1153" author="F. Wancho" title="Digest Message Format"
1196 <dref>euc-kr</dref>
\e$B$H
\e(B <dref>iso-2022-kr</dref>
\e$B$H$$$&4Z9q8l$N$?$a$N
\e(B
1197 <a node="MIME charset">MIME charset</a>
\e$B$rDj5A$7$F$$$k
\e(B RFC.
1199 <rfc number="1557" type="Informational" author="U. Choi, K. Chon and
1200 H. Park" title="Korean Character Encoding for Internet
1201 Messages" date="December 1993">
1207 <dref>iso-2022-cn</dref>, <dref>iso-2022-cn-ext</dref>,
1208 <dref>cn-gb</dref>, <dref>cn-big5</dref>
\e$B$H$$$C$?Cf9q8l$N$?$a$N
\e(B <a
1209 node="MIME charset">MIME charset</a>
\e$B$rDj5A$7$F$$$k
\e(B RFC.
1211 \e$B$3$l$K2C$($F!"
\e(B<concept>charset-edition</concept>
\e$B$H
\e(B
1212 <concept>charset-extension</concept>
\e$B$H$$$&
\e(B <dref>Content-Type
1213 field</dref>
\e$B$N
\e(B parameter
\e$B$rDj5A$7$F$$$k!#
\e(B
1215 <rfc number="1922" type="Informational" author="Zhu, HF., Hu, DY.,
1216 Wang, ZG., Kao, TC., Chang, WCH. and Crispin, M."
1217 title="Chinese Character Encoding for Internet Messages"
1224 <rfc number="2045" type="Standards Track" author="N. Freed and
1225 N. Borenstein" title="Multipurpose Internet Mail
1226 Extensions (MIME) Part One: Format of Internet Message
1227 Bodies" date="November 1996" obsolete="1521, 1522,
1234 <rfc number="2046" type="Standards Track" author="N. Freed and
1235 N. Borenstein" title="Multipurpose Internet Mail
1236 Extensions (MIME) Part Two: Media Types"
1237 date="November 1996" obsolete="1521, 1522, 1590">
1243 <rfc number="2048" type="Standards Track" author="N. Freed, J. Klensin
1244 and J. Postel" title="Multipurpose Internet Mail
1245 Extensions (MIME) Part Four: Registration Procedures"
1246 date="November 1996" obsolete="1521, 1522, 1590">
1252 <rfc number="2049" type="Standards Track" author="N. Freed and
1253 N. Borenstein" title="Multipurpose Internet Mail
1254 Extensions (MIME) Part Five: Conformance Criteria and
1255 Examples" date="November 1996" obsolete="1521, 1522,
1262 \e$B=qBN$dAHHG$K4X$9$k>pJs$r;}$?$J$$
\e(B <a node="Coded character set">
\e$BJ8;zId
\e(B
1263 \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">
1266 <h3> Security multipart
1267 <node> Security multipart
1269 <a node="MIME">MIME</a>
\e$B$G0E9f$dEE;R=qL>$rMQ$$$k$?$a$N7A<0!#
\e(B<a
1270 node="multipart/signed"><concept>multipart/signed</concept></a>
\e$B$H
\e(B <a
1271 node="multipart/encrypted"><concept>multipart/encrypted</concept></a>
1272 \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
1273 \e$B$3$l$K4p$$$F$$$k!#
\e(B
1275 <rfc name="Security multipart" number="1847" type="Standards Track"
1276 author="James Galvin, Gale Murphy, Steve Crocker and Ned
1277 Freed" title="Security Multiparts for MIME:
1278 Multipart/Signed and Multipart/Encrypted" date="October
1283 <node> text/enriched
1285 RFC 1521
\e$B$GDj5A$5$l$?
\e(B <concept>text/richtext</concept>
\e$B$KBe$o$C$F!"=q
\e(B
1286 \e$BBN$dAHHG$K4X$9$k>pJs$r;}$C$?
\e(B text
\e$B$rI=8=$9$k$?$a$N
\e(B <dref>media
1289 <rfc name="text/enriched" number="1896" author="P. Resnick and
1290 A. Walker" title="The text/enriched MIME Content-type"
1291 date="February 1996" obsolete="1563">
1297 <concept>text/plain</concept> is a <dref>media type</dref> for
1298 <dref>plain text</dref>, defined in <dref>RFC 2046</dref>.
1300 The default media type of ``text/plain; charset=us-ascii'' for
1301 Internet mail describes existing Internet practice. That is, it is
1302 the type of body defined by <dref>RFC 822</dref>.
1304 <cf node="MIME charset"><cf node="us-ascii">
1310 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
1311 \e$B6!$9$k
\e(B library
\e$B72!#
\e(B`tools for MIME'
\e$B$NN,!#
\e(B
1313 <memo title="
\e$B$I$&$G$bNI$$$3$H
\e(B(^-^;">
1316 <li> tm
\e$B$O
\e(B ``tiny-mime''
\e$B$NN,$8$c$J$$$i$7$$$>
\e(B (^-^;
1317 <li> tm
\e$B$O:n<T$N%$%K%7%c%k$8$c$J$$$i$7$$$>
\e(B (^-^;
1318 <li> ``Tools for MIME''
\e$B$NN,$H$$$&$N$O$3$8$D$1$i$7$$$>
\e(B (^-^;
1326 <a node="tm-kernel">tm</a>
\e$B$rMQ$$$?
\e(B <a node="MUA">MUA</a>
\e$B$b$7$/$O
\e(B MUA
1327 \e$B$KBP$9$k
\e(B extender.
1329 <concept>tm
\e$BBg@9$j
\e(B package</concept>
\e$B$K$O
\e(B
1332 <li><a file="mh-e">mh-e</a>
\e$BMQ$N
\e(B <concept>tm-mh-e</concept>
1333 <li>GNUS
\e$BMQ$N
\e(B <concept>tm-gnus</concept>
1334 <li>Gnus
\e$BMQ$N
\e(B <a file="gnus-mime-en"><concept>gnus-mime</concept></a>
1335 <li>VM
\e$BMQ$N
\e(B <concept>tm-vm</concept>
1336 <li>RMAIL
\e$BMQ$N
\e(B <concept>tm-rmail</concept>
1340 \e$B$,4^$^$l$F$$$k!#
\e(B
1342 \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
1348 \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
1349 charset">MIME charset</a>
\e$B$N#1$D!#
\e(B
1351 <dref>ASCII</dref>
\e$B$N$_$+$i$J$j
\e(B <dref>ISO 2022</dref>
\e$B$K$h$k
\e(B<a
1352 node="Code extension">
\e$BId9f3HD%
\e(B</a>
\e$B$O5v$5$l$J$$!#
\e(B
1354 Internet mail
\e$B$K$*$1$kI8=`$N
\e(B<a node="Coded character set">
\e$BId9f2=J8;z=8
\e(B
1355 \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
1356 <concept>us-ascii</concept>
\e$B$,;H$o$l$k!#
\e(B
1358 \e$B$^$?!"
\e(B<a node="RFC 822">RFC 822</a>
\e$B$K$*$1$k
\e(B <concept>ASCII</concept>
1359 \e$B$O
\e(B us-ascii
\e$B$r;X$9$b$N$H2r<a$9$Y$-$G$"$k!#
\e(B
1365 In the tm package, two files, <file>mime-setup.el</file> and
1366 <file>tm-setup.el</file>, are provided to ease the setup.
1368 The <file>mime-setup.el</file> is used for the whole MIME related
1369 setup including MIME encoding using <file>tm-edit.el</file>, while
1370 <file>tm-setup.el</file> is used to set up tm-MUA only.
1376 If you want normal setting, please use <concept>mime-setup</concept>.
1377 For example, please insert following into <file>~/.emacs</file>:
1384 As <file>mime-setup.el</file> loads <file>tm-setup.el</file>, you
1385 don't need to load <file>tm-setup.el</file> when you use
1386 <file>mime-setup.el</file> (Description of old version of Gnus FAQ is
1393 You can set up the <concept>automatic signature selection
1394 tool</concept> using <file>mime-setup</file>. If you want to
1395 automatically select the signature file depending on how the message
1396 headers show, add lines like shown below to your .emacs (Refer to the
1397 reference manual of <file>signature.el</file> for more details).
1400 (setq signature-file-alist
1401 '((("Newsgroups" . "jokes") . "~/.signature-jokes")
1402 (("Newsgroups" . ("zxr" "nzr")) . "~/.signature-sun")
1403 (("To" . ("ishimaru" "z-suzuki")) . "~/.signature-sun")
1404 (("To" . "tea") . "~/.signature-jokes")
1405 (("To" . ("sim" "oku" "takuo")) . "~/.signature-formal")
1410 <defvar name="mime-setup-use-signature">
1412 If it is not <code>nil</code>, <file>mime-setup.el</file> sets up for
1413 <file>signature.el</file>. Its default value is <code>t</code>.
1417 <defvar name="mime-setup-signature-key-alist">
1419 It defines key to bind signature inserting command for each
1420 major-mode. Its default value is following:
1423 ((mail-mode . "\C-c\C-w"))
1427 If you want to change, please rewrite it. For example:
1430 (set-alist 'mime-setup-signature-key-alist
1431 'news-reply-mode "\C-c\C-w")
1437 <defvar name="mime-setup-default-signature-key">
1439 If key to bind signature inserting command for a major-mode is not
1440 found from <code>mime-setup-signature-key-alist</code>, its value is
1441 used as key. Its default value is <code>"\C-c\C-s"</code>.
1445 <h3> Notices for GNUS
1446 <node> Notice about GNUS
1448 When <file>mime-setup.el</file> sets up for <file>signature.el</file>,
1449 it sets variable <code>gnus-signature-file</code> to <code>nil</code>.
1450 Therefore GNUS does not insert signature automatically when it is
1451 sending a message. Reason of this setting is following:
1453 GNUS inserts signature after <file>tm-edit.el</file> composed as MIME
1454 message. Therefore signature inserted by GNUS is not processed as a
1455 valid MIME part. In particular, for multipart message, signature
1456 places in outside of MIME part. So MIME MUA might not display it.
1458 Other notice is key bind. In historical reason, key bind to insert
1459 signature is <kbd>C-c C-s</kbd> (like <a file="mh-e">mh-e</a>) instead
1460 of <kbd>C-c C-w</kbd>. If you change to GNUS's default, please set
1464 (set-alist 'mime-setup-signature-key-alist 'news-reply-mode "\C-c\C-w")
1468 <h2> Setting not to use tm-edit
1471 <concept>tm-setup</concept> only sets up <a node="tm-MUA">tm-MUA</a>s.
1472 In other words, it is a setting to avoid to use tm-edit. If you don't
1473 want to compose MIME message or want to use other MIME composer,
1474 please use it instead of <file>mime-setup.el</file>.
1476 For example, please insert following into <file>~/.emacs</file>:
1486 If you use <file>mime-setup.el</file>, you you don't need to load
1487 <file>tm-setup.el</file>.
1492 <node> setting for VM
1494 If you use <concept>vm</concept>, please insert following in
1502 <memo title="Notice">
1504 If you use <concept>BBDB</concept>, please insert <code>(require
1505 'tm-vm)</code> <bf>after</bf> <code>(bbdb-insinuate-vm)</code>.
1509 <h2> Setting up without loading provided setup files
1510 <node> manual setting
1512 You may find the valuable hints in <file>mime-setup.el</file> or
1513 <file>tm-setup.el</file> if you want to set up MIME environment
1514 without loading the tm-provided setup files.
1518 Current tm provides some convenient features to expect tm-edit, and
1519 they can not use if <file>mime-setup.el</file> is not used. If you
1520 want to set up original setting to use tm-edit, please declare
1524 (provide 'mime-setup)
1530 <h1> How to report bug and about mailing list of tm
1533 If you write bug-reports and/or suggestions for improvement, please
1534 send them to the tm Mailing List:
1537 <li> Japanese <mail>bug-tm-ja@chamonix.jaist.ac.jp</mail>
1538 <li> English <mail>bug-tm-en@chamonix.jaist.ac.jp</mail>
1542 Notice that, we does not welcome bug reports about too old version.
1543 Bugs in old version might be fixed. So please try latest version at
1546 You should write <concept>good bug report</concept>. If you write
1547 only ``tm does not work'', we can not find such situations. At least,
1548 you should write name, type, variants and version of OS, emacs, tm and
1549 MUA, and setting. In addition, if error occurs, to send backtrace is
1550 very important. <cf file="emacs" node="Bugs">
1552 Bug may not appear only your environment, but also in a lot of
1553 environment (otherwise it might not bug). Therefor if you send mail
1554 to author directly, we must write a lot of mails. So please send mail
1555 to address for tm bugs instead of author.
1557 Via the tm ML, you can report tm bugs, obtain the latest release of
1558 tm, and discuss future enhancements to tm. To join the tm ML, send
1562 <li> Japanese <mail>tm-ja-admin@chamonix.jaist.ac.jp</mail>
1563 <li> English <mail>tm-en-admin@chamonix.jaist.ac.jp</mail>
1567 Since the user registration is done manually, please write the mail
1568 body in human-recognizable language (^_^).
1572 <node> Concept Index
1578 <node> Variable Index