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
\e$BJ8;z=89g
\e(B
103 <node> 94 character set
105 33
\e$B$+$i
\e(B 126
\e$B$NHO0O$N
\e(B 1 byte
\e$B$+$i$J$k
\e(B <a node="Character set">
\e$BJ8;z=89g
\e(B
106 </a>
\e$B!#
\e(B<a node="ASCII">ASCII</a>
\e$B$d
\e(B JIS X0201-Latin
\e$B$O$=$N0l<o!#
\e(B
109 <h3> 96
\e$BJ8;z=89g
\e(B
110 <node> 96 character set
112 32
\e$B$+$i
\e(B 127
\e$B$NHO0O$N
\e(B 1 byte
\e$B$+$i$J$k
\e(B <a node="Character set">
\e$BJ8;z=89g
\e(B
113 </a>
\e$B!#
\e(BISO 8859
\e$B%7%j!<%:$O$=$N0l<o!#
\e(B
116 <h3> 94
\e$B!_
\e(B94
\e$BJ8;z=89g
\e(B
117 <node> 94x94 character set
119 33
\e$B$+$i
\e(B 126
\e$B$NHO0O$N
\e(B 2 byte
\e$B$+$i$J$k
\e(B <a node="Character set">
\e$BJ8;z=89g
\e(B
120 </a>
\e$B!#
\e(B<a node="JIS X0208">JIS X0208</a>
\e$B$d
\e(B <a node="GB 2312">GB
121 2312</a>
\e$B$O$=$N0l<o!#
\e(B
127 \e$B%"%a%j%+O"K.$G;H$o$l$kJ8;z$rId9f2=$7$?
\e(B <a node="94 character set">94
128 \e$BJ8;z=89g
\e(B</a>
\e$B!#
\e(BA-Z, a-z
\e$B$N
\e(B Latin
\e$BJ8;z$H?t;z!"4v$D$+$N5-9f$+$i$J$k!#
\e(B<a
129 node="ISO 646">ISO 646</a>
\e$B$N0l$D!#
\e(B
131 <standard abbrev="ASCII" title-en="Coded Character Set -- 7-Bit
132 American Standard Code for Information Interchange"
133 number="ANSI X3.4" year="1986">
139 <concept>Base64</concept> is a transfer encoding method of
140 <dref>MIME</dref> defined in <dref>RFC 2045</dref>.
142 The encoding process represents 24-bit groups of input bits as output
143 strings of 4 encoded characters. Encoded characters represent integer
144 0 .. 63 or <concept>pad</concept>. Base64 data must be 4 * n bytes,
145 so pad is used to adjust size.
147 These 65 characters are subset of all versions of ISO 646, including
148 US-ASCII, and all versions of EBCDIC. So it is safe even if it is
149 translated by non-Internet gateways.
155 \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
157 <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
160 \e$B$^$?!"9T$N9=B$$,$"$C$F$b!"
\e(B999 byte
\e$B0J>e$+$i$J$k9T$,$"$k>l9g$b
\e(B binary
161 \e$B$H8F$V$3$H$K$7$^$9!#
\e(B
163 \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
164 \e$B$G$bI=8=$G$-$^$9!#$h$C$F!"
\e(B<concept>binary data</concept>
\e$B$H8@$C$?>l9g!"
\e(B
165 \e$BG$0U$N
\e(B data
\e$B$r;X$9$3$H$,$"$j$^$9!#
\e(B
168 <h3> Character Set
\e$B!JJ8;z=89g!K
\e(B
171 <a node="Coded character set">
\e$BId9f2=J8;z=89g
\e(B</a>
\e$B!#C"$7!"$3$3$G$O
\e(B <a
172 node="Code extension">
\e$BId9f3HD%
\e(B</a>
\e$B$5$l$F$J$$J8;z=89g$H$$$&%K%e%"%s%9
\e(B
173 \e$B$r9~$a$F$$$k!#
\e(B
179 \e$BCf9qBgN&$G$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N
\e(B <a
180 node="MIME charset">MIME charset</a>
\e$B$N#1$D!#
\e(B
182 <a node="ISO 2022">ISO 2022</a>
\e$B$K4p$$$F
\e(B <a node="ASCII">ASCII</a>
\e$B$K
\e(B
183 <a node="GB 2312">GB 2312</a>
\e$B$r
\e(B <a node="8bit">8bit</a>
\e$B$G
\e(B<a
184 node="Code extension">
\e$BId9f3HD%
\e(B</a>
\e$B$7$F$$$k!#
\e(B
186 <a node="RFC 1922">RFC 1922</a>
\e$B$GDj5A$5$l$F$$$k!#
\e(B
192 \e$BBfOQ$d9a9A$GMQ$$$i$l$F$$$k<g$KHKBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N
\e(B
193 <a node="MIME charset">MIME charset</a>
\e$B$N#1$D!#
\e(B
195 <a node="ISO 2022">ISO 2022</a>
\e$B$K4p$+$J$$
\e(B <a node="8bit">8bit</a>
\e$B$N
\e(B
196 <a node="Coded character set">
\e$BId9f2=J8;z=89g
\e(B</a>
\e$B$G
\e(B de-fact standard
\e$B$G
\e(B
197 \e$B$"$k!#
\e(B<a node="RFC 1922">RFC 1922</a>
\e$B$GDj5A$5$l$F$$$k!#
\e(B
199 cf. <report abbrev="BIG5" author="Institute for Information Industry"
200 title-en="Chinese Coded Character Set in Computer"
203 <a node="CNS">CNS 11643-1986</a>
\e$B$HBP1~4X78$,$"$k!#
\e(B
209 \e$BBfOQ$d9a9A$GMQ$$$i$l$F$$$k<g$KHKBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N
\e(B
210 <a node="Character set">
\e$BJ8;z=89g
\e(B</a>
\e$B!#BfOQ$NI8=`!#8=:_!"
\e(B<a node="94x94
211 character set">94
\e$B!_
\e(B94</a>
\e$B$NLL$,Bh#1LL$+$iBh#7LL$^$G$"$k!#
\e(B
213 <a node="ISO 2022">ISO 2022</a>
\e$B$G$N=*C<J8;z$O!"Bh#1LL$,
\e(B `G',
\e$BBh#2LL$,
\e(B
214 `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
217 <standard abbrev="CNS 11643-1992" title-en="Standard Interchange Code
218 for Generally-Used Chinese Characters" number="CNS
222 <h3> Coded character set
\e$B!JId9f2=J8;z=89g!K
\e(B, Character code
\e$B!JJ8;zId9f!K
\e(B
223 <node> Coded character set
225 \e$BJ8;z$H
\e(B byte
\e$BNs$H#1BP#1$KBP1~IU$1$k[#Kf$G$J$$5,B'$N=89g!#
\e(B
228 <h3> Code extension
\e$B!JId9f3HD%!K
\e(B
229 <node> Code extension
231 \e$BM?$($i$l$?
\e(B<a node="Character set">
\e$BJ8;z=89g
\e(B</a>
\e$B$K4^$^$l$F$$$J$$J8;z$NId
\e(B
232 \e$B9f2=$N$?$a$KMQ$$$k<jK!!#
\e(B<a node="ISO 2022">ISO 2022</a>
\e$B$O$=$N#1$D!#
\e(B
235 <h3> Content-Disposition field
236 <node> Content-Disposition
238 Content
\e$B$NI=<($N;EJ}$d
\e(B file
\e$BL>$rI=8=$9$k$?$a$N
\e(B field. <a
239 node="MIME">MIME</a>
\e$B$N3HD%$N#1$D!#
\e(B
241 <rfc number="1806" type="Experimental" author="E R. Troost and
242 S. Dorner" title="Communicating Presentation Information
243 in Internet Messages: The Content-Disposition Header"
250 <concept>media type</concept> specifies the nature of the data in the
251 body of <dref>MIME</dref> <dref>entity</dref>. It consists of
252 <concept>type</> and <concept>subtype</concept>. It is defined in
253 <dref>RFC 2046</dref>.
255 Currently there are following types:
258 <li><concept>text</concept>
260 <li><concept>image</concept>
262 <li><concept>audio</concept>
264 <li><concept>video</concept>
266 <li><concept>application</concept>
268 <li><a node="multipart"><concept>multipart</concept></a>
270 <li><concept>message</concept>
274 And there are various subtypes, for example, application/octet-stream,
275 audio/basic, image/jpeg, <dref>multipart/mixed</dref>,
276 <dref>text/plain</dref>, video/mpeg...
278 You can refer registered media types at <a
279 href="ftp://ftp.isi.edu/in-notes/iana/assignments/media-types">MEDIA
282 In addition, you can use private type or subtype using
283 <concept>x-token</concept>, which as the prefix `x-'. However you can
284 not use them in public.
286 <cf node="Content-Type field">
289 <h3> Content-Type field
290 <node> Content-Type field
292 Header field to represent information about body, such as <dref>media
293 type</dref>, <dref>MIME charset</dref>. It is defined in <dref>RFC
298 Historically, Content-Type field was proposed in RFC 1049. In it,
299 Content-Type did not distinguish type and subtype. However MIME
300 parser may be able to accept RFC 1049 based Content-Type as unknown
305 Content-Type field is defined as following:
308 ``Content-Type'' ``:'' <concept>type</concept> ``/''
309 <concept>subtype</concept> *( ``;'' <concept>parameter</concept> )
317 Content-Type: image/jpeg
323 Content-Type: text/plain; charset=iso-2022-jp
329 A part does not have content-type field is regarded as
333 Content-Type: text/plain; charset=us-ascii
340 And a part has unknown type/subtype is regarded as
344 Content-Type: application/octet-stream
354 \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
355 GNU Emacs
\e$B$NJQ<o$NAm>N$H$9$k!#
\e(B
361 Representation non <a node="ASCII">ASCII</a> characters in header. It
362 is defined in <concept>RFC 2047</concept>.
364 <rfc number="2047" type="Standards Track" author="K. Moore"
365 title="MIME (Multipurpose Internet Mail Extensions) Part
366 Three: Message Header Extensions for Non-ASCII Text"
367 date="November 1996" obsolete="1521,1522,1590">
373 <a node="RFC 822">Internet mail</a>
\e$B$rB>$N5-;v$K$^$k$4$HF~$l$kJ}K!!#
\e(B
375 \e$BNc$($P!"5-;v$rE>Aw$7$?$j$9$k$N$KMQ$$$k!#
\e(B
377 <cf node="message/rfc822">
383 \e$B4Z9q8l$rI=8=$9$k$?$a$N
\e(B <a node="MIME charset">MIME charset</a>
\e$B$N#1$D!#
\e(B
385 <a node="ISO 2022">ISO 2022</a>
\e$B$K4p$$$F
\e(B <a node="ASCII">ASCII</a>
\e$B$K
\e(B
386 <a node="KS C5601">KS C5601</a>
\e$B$r
\e(B <a node="8bit">8bit</a>
\e$B$G
\e(B<a
387 node="Code extension">
\e$BId9f3HD%
\e(B</a>
\e$B$7$F$$$k!#
\e(B
389 <a node="RFC 1557">RFC 1557</a>
\e$B$GDj5A$5$l$F$$$k!#
\e(B
391 cf. <standard abbrev="euc-kr" org="Korea Industrial Standards
392 Association" title-en="Hangul Unix Environment"
393 number="KS C 5861" year="1992">
398 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
401 <rfc name="FTP" number="959" type="STD 9" author="Postel, J. and
402 J. Reynolds" title="File Transfer Protocol"
409 \e$BCf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=$9$?$a$N
\e(B <a
410 node="94x94 character set">94
\e$B!_
\e(B94
\e$BJ8;z=89g
\e(B</a>
\e$B!#Cf9q$N9q2HI8=`!#
\e(B<a
411 node="ISO 2022">ISO 2022</a>
\e$B$G$N=*C<J8;z$O
\e(B `A'.
413 \e$B$3$l$O
\e(B GB
\e$B$K$*$1$k4pK\=8$G$"$k!#
\e(B
415 <standard abbrev="GB 2312"
416 title-cn="
\e$B?.B)8r49MQ4A;zJTb{;zId=8
\e(B --
\e$B4pK\=8
\e(B"
417 title-en="Code of Chinese Graphic Character Set for
418 Information Interchange - Primary Set" number="GB 2312"
425 \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
426 <a node="GB 2312">GB 2312</a>
\e$B$N6u$-ItJ,$KJd=<$9$k$h$&$KDj5A$5$l$?$i$7
\e(B
429 <standard abbrev="GB 8565.2" title-en="Information Processing - Coded
430 Character Sets for Text Communication - Part 2: Graphic
431 Characters used with Primary Set" number="GB 8565.2"
438 \e$BCf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N
\e(B <a
439 node="MIME charset">MIME charset</a>
\e$B$N#1$D!#
\e(B
441 <a node="ASCII">ASCII</a>
\e$B$K
\e(B <a node="GB 2312">GB 2312</a>
\e$B$r
\e(B 7bit
\e$B$G
\e(B
442 <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
443 \e$B$h$&$K9)IW$7$F$$$k!#
\e(B
445 RFC 1842, 1843
\e$B$GDj5A$5$l$F$$$k!#
\e(B
447 <rfc number="1842" type="Informational" author="Y. Wei, Y. Zhang,
448 J. Li, J. Ding and Y. Jiang" title="ASCII Printable
449 Characters-Based Chinese Character Encoding for Internet
450 Messages" date="August 1995">
451 <rfc number="1843" type="Informational" author="F. Lee" title="HZ - A
452 Data Format for Exchanging Files of Arbitrarily Mixed
453 Chinese and ASCII characters" date="August 1995">
459 <a node="Code extension">
\e$BId9f3HD%
\e(B</a>
\e$B$N$?$a$N9q:]I8=`!#
\e(B
461 \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
462 node="7bit">7bit</a>
\e$B$J$$$7
\e(B <a node="8bit">8bit</a>
\e$B$N
\e(B <a node="Coded
463 character set">
\e$BId9f2=J8;z=89g
\e(B</a>
\e$B$r:n$k$3$H$,$G$-$k!#
\e(B
465 <standard abbrev="ISO 2022" org="International Organization for
466 Standardization (ISO)" title-en="Information Processing:
467 ISO 7-bit and 8-bit coded character sets: Code extension
468 techniques" number="ISO/IEC 2022" year="1994">
474 \e$BCf9q8l$rI=8=$9$k$?$a$N
\e(B <a node="MIME charset">MIME charset</a>
\e$B$N#1$D!#
\e(B
476 <a node="ISO 2022">ISO 2022</a>
\e$B$K4p$$$F
\e(B <a node="ASCII">ASCII</a>
\e$B$K
\e(B
477 <a node="GB 2312">GB 2312</a>, <a node="CNS">CNS 11643 plain 1, plain
478 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
479 </a>
\e$B$7$F$$$k!#
\e(B
481 <a node="RFC 1922">RFC 1922</a>
\e$B$GDj5A$5$l$F$$$k!#
\e(B
485 <node> iso-2022-cn-ext
487 \e$BCf9q8l$rI=8=$9$k$?$a$N
\e(B <a node="MIME charset">MIME charset</a>
\e$B$N#1$D!#
\e(B
489 <a node="ISO 2022">ISO 2022</a>
\e$B$K4p$$$F
\e(B <a node="ASCII">ASCII</a>
\e$B$K
\e(B
490 <a node="GB 2312">GB 2312</a>, <a node="CNS">CNS 11643 plain 1
491 .. 7</a>, <a node="ISO-IR-165">ISO-IR-165</a>
\e$BEy$r
\e(B <a
492 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
494 <a node="RFC 1922">RFC 1922</a>
\e$B$GDj5A$5$l$F$$$k!#
\e(B
497 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
499 Emacs/mule
\e$B$G$OMxMQ2DG=$G$"$k!#
\e(B
506 \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
508 \e$B8E$$
\e(B <a node="ISO 2022">ISO 2022</a>
\e$B$K4p$$$F
\e(B <a
509 node="ASCII">ASCII</a>, JIS X0201-Latin, <a node="JIS C6226-1978">JIS
510 X0208-1978</a>, <a node="JIS X0208">JIS X0208-1983</a>
\e$B$r@Z$jBX$($k
\e(B <a
511 node="7bit">7bit</a>
\e$BJ8;zId9f!#
\e(B
513 RFC 1468
\e$B$GDj5A$5$l$F$$$k!#
\e(B
516 JIS X0208-1996?
\e$B$G$O
\e(B <a node="ISO 2022">ISO 2022</a>
\e$B$HFHN)$KDj5A$5$l
\e(B
520 <rfc name="iso-2022-jp" number="1468" author="Murai J., M. Crispin,
521 and E. van der Poel" title="Japanese Character Encoding
522 for Internet Messages" date="June 1993">
528 <a node="iso-2022-jp">iso-2022-jp</a>
\e$B$r3HD%$7$?
\e(B <a node="MIME
529 charset">MIME charset</a>
\e$B$N0l$D!#
\e(B
531 RFC 1554
\e$B$GDj5A$5$l$F$$$k!#
\e(B
533 <rfc name="iso-2022-jp-2" number="1554" type="Informational"
534 author="Ohta M. and Handa K." title="ISO-2022-JP-2:
535 Multilingual Extension of ISO-2022-JP" date="December
542 \e$B4Z9q8l$rI=8=$9$k$?$a$N
\e(B <a node="MIME charset">MIME charset</a>
\e$B$N#1$D!#
\e(B
544 <a node="ISO 2022">ISO 2022</a>
\e$B$K4p$$$F
\e(B <a node="ASCII">ASCII</a>
\e$B$K
\e(B
545 <a node="KS C5601">KS C5601</a>
\e$B$r
\e(B <a node="7bit">7bit</a>
\e$B$G
\e(B<a
546 node="Code extension">
\e$BId9f3HD%
\e(B</a>
\e$B$7$F$$$k!#
\e(B
548 <a node="RFC 1557">RFC 1557</a>
\e$B$GDj5A$5$l$F$$$k!#
\e(B
554 \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
555 \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
556 \e$B!J9q:]4p=`HG!K$r85$K4v$D$+$NJ8;z$O3F9q$G0c$&J8;z$r3dEv$k$3$H$r5v$7$F$$
\e(B
557 \e$B$F!"4v$D$+$NJQ<o$,B8:_$9$k!#
\e(B<a node="ASCII">ASCII</a>
\e$B$d
\e(B JIS
558 X0201-Latin
\e$B$O$=$N0l<o!#
\e(B
560 <standard abbrev="ISO 646" org="International Organization for
561 Standardization (ISO)" title-en="Information technology:
562 ISO 7-bit coded character set for information
563 interchange" number="ISO/IEC 646" year="1991">
569 \e$B@>2$=t8l$GMQ$$$i$l$k3HD%
\e(B Latin
\e$BJ8;z$d5-9f$+$i$J$k
\e(B <a node="96
570 character set">96
\e$BJ8;z=89g
\e(B</a>
\e$B!#
\e(B
572 <standard abbrev="ISO 8859-1" org="International Organization for
573 Standardization (ISO)" title-en="Information Processing
574 -- 8-bit Single-Byte Coded Graphic Character Sets --
575 Part 1: Latin Alphabet No.1" number="ISO 8859-1"
582 <concept>iso-8859-1</concept> is a <dref>MIME charset</dref> for
583 west-European languages written by Latin script.
585 <a node="ISO 2022">ISO 2022</a>
\e$B$K4p$$$F!"
\e(B<a node="ASCII">ASCII</a>
\e$B$K
\e(B
586 <a node="ISO 8859-1">ISO 8859-1</a>
\e$B$r
\e(B <a node="8bit">8bit</a>
\e$B$G
\e(B<a
587 node="Code extension">
\e$BId9f3HD%
\e(B</a>
\e$B$7$F$$$k!#
\e(B
589 It is defined in <dref>RFC 2046</dref>.
595 \e$BEl2$=t8l$GMQ$$$i$l$k3HD%
\e(B Latin
\e$BJ8;z$d5-9f$+$i$J$k
\e(B <a node="96
596 character set">96
\e$BJ8;z=89g
\e(B</a>
\e$B!#
\e(B
598 <standard abbrev="ISO 8859-2" org="International Organization for
599 Standardization (ISO)" title-en="Information Processing
600 -- 8-bit Single-Byte Coded Graphic Character Sets --
601 Part 2: Latin alphabet No.2" number="ISO 8859-2"
608 <concept>iso-8859-2</concept> is a <dref>MIME charset</dref> for
609 east-European languages written by Latin script.
611 <a node="ISO 2022">ISO 2022</a>
\e$B$K4p$$$F!"
\e(B<a node="ASCII">ASCII</a>
\e$B$K
\e(B
612 <a node="ISO 8859-2">ISO 8859-2</a>
\e$B$r
\e(B <a node="8bit">8bit</a>
\e$B$G
\e(B<a
613 node="Code extension">
\e$BId9f3HD%
\e(B</a>
\e$B$7$F$$$k!#
\e(B
615 It is defined in <dref>RFC 2046</dref>.
621 <standard abbrev="ISO 8859-3" org="International Organization for
622 Standardization (ISO)" title-en="Information
623 Processing -- 8-bit Single-Byte Coded Graphic
624 Character Sets -- Part 3: Latin alphabet No.3"
625 number="ISO 8859-3" year="1988">
631 <standard abbrev="ISO 8859-4" org="International Organization for
632 Standardization (ISO)" title-en="Information
633 Processing -- 8-bit Single-Byte Coded Graphic
634 Character Sets -- Part 4: Latin alphabet No.4"
635 number="ISO 8859-4" year="1988">
641 \e$B%-%j%kJ8;z$d5-9f$+$i$J$k
\e(B <a node="96 character set">96
\e$BJ8;z=89g
\e(B</a>
\e$B!#
\e(B
643 <standard abbrev="ISO 8859-5" org="International Organization for
644 Standardization (ISO)" title-en="Information Processing
645 -- 8-bit Single-Byte Coded Graphic Character Sets --
646 Part 5: Latin/Cyrillic alphabet" number="ISO 8859-5"
653 <concept>iso-8859-5</concept> is a <dref>MIME charset</dref> for
656 <a node="ISO 2022">ISO 2022</a>
\e$B$K4p$$$F!"
\e(B<a node="ASCII">ASCII</a>
\e$B$K
\e(B
657 <a node="ISO 8859-5">ISO 8859-5</a>
\e$B$r
\e(B <a node="8bit">8bit</a>
\e$B$G
\e(B<a
658 node="Code extension">
\e$BId9f3HD%
\e(B</a>
\e$B$7$F$$$k!#
\e(B
660 It is defined in <dref>RFC 2046</dref>.
666 <standard abbrev="ISO 8859-6" org="International Organization for
667 Standardization (ISO)" title-en="Information
668 Processing -- 8-bit Single-Byte Coded Graphic
669 Character Sets -- Part 6: Latin/Arabic alphabet"
670 number="ISO 8859-6" year="1987">
676 \e$B%.%j%7%"J8;z$d5-9f$+$i$J$k
\e(B <a node="96 character set">96
\e$BJ8;z=89g
\e(B</a>
\e$B!#
\e(B
678 <standard abbrev="ISO 8859-7" org="International Organization for
679 Standardization (ISO)" title-en="Information Processing
680 -- 8-bit Single-Byte Coded Graphic Character Sets --
681 Part 7: Latin/Greek alphabet" number="ISO 8859-7"
688 <concept>iso-8859-7</concept> is a <dref>MIME charset</dref> for
691 <a node="ISO 2022">ISO 2022</a>
\e$B$K4p$$$F!"
\e(B<a node="ASCII">ASCII</a>
\e$B$K
\e(B
692 <a node="ISO 8859-7">ISO 8859-7</a>
\e$B$r
\e(B <a node="8bit">8bit</a>
\e$B$G
\e(B<a
693 node="Code extension">
\e$BId9f3HD%
\e(B</a>
\e$B$7$F$$$k!#
\e(B
695 It is defined in RFC 1947.
697 <rfc name="iso-8859-7" number="1947" type="Informational"
698 author="D. Spinellis" title="Greek Character Encoding
699 for Electronic Mail Messages" date="May 1996">
705 <standard abbrev="ISO 8859-8" org="International Organization for
706 Standardization (ISO)" title-en="Information
707 Processing -- 8-bit Single-Byte Coded Graphic
708 Character Sets -- Part 8: Latin/Hebrew alphabet"
709 number="ISO 8859-8" year="1988">
715 <standard abbrev="ISO 8859-9" org="International Organization for
716 Standardization (ISO)" title-en="Information
717 Processing -- 8-bit Single-Byte Coded Graphic
718 Character Sets -- Part 9: Latin alphabet No.5"
719 number="ISO 8859-9" year="1990">
722 <h3> ISO-IR-165, CCITT Extended GB <node> ISO-IR-165
724 CCITT
\e$B$,EPO?$7$?!"Cf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=
\e(B
725 \e$B8=$9$k$?$a$N
\e(B <a node="94x94 character set">94
\e$B!_
\e(B94
\e$BJ8;z=89g
\e(B</a>
\e$B!#
\e(B
727 <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>
728 \e$B$K
\e(B 150
\e$BJ8;z$[$I$rDI2C$7$?$b$N$i$7$$!#
\e(B
730 <a node="ISO 2022">ISO 2022</a>
\e$B$G$N=*C<J8;z$O
\e(B `E'
\e$B$G$"$k!#
\e(B
736 <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
737 byte
\e$B$N%+%?%+%JJ8;z=89g$+$i$J$k!#
\e(B
739 \e$B85$O
\e(B <concept>JIS C6220-1976</concept>
\e$B$H8@$C$?$,
\e(B <concept>JIS
740 X0201</concept>
\e$B$KHV9f$,JQ99$5$l$?!#
\e(B
742 <standard abbrev="JIS X0201-1976" org="
\e$BF|K\5,3J6(2q
\e(B (Japanese
743 Standards Association)" title-ja="
\e$B>pJs8r49MQId9f
\e(B"
744 title-en="Code for Information Interchange" number="JIS
747 \e$B$^$?!"
\e(B1996
\e$BG/$K2~DjHG$,=P$kM=Dj!#
\e(B
749 <standard abbrev="JIS X0201-1996?" org="
\e$BF|K\5,3J6(2q
\e(B (Japanese
750 Standards Association)"
751 title-ja="
\e$B#7%S%C%H5Z$S#8%S%C%H$N>pJs8r49MQId9f2=J8;z=89g
\e(B"
752 title-en="7-bit and 8-bit coded character sets for
753 information interchange" number="JIS X 0201" year="1996?
760 \e$BF|K\8l$rI=$9$?$a$K:n$i$l$?
\e(B <a node="94x94 character set">94
\e$B!_
\e(B94
\e$BJ8;z=8
\e(B
761 \e$B9g
\e(B</a>
\e$B!#F|K\$N9q2HI8=`!#
\e(BJIS X0208-1978
\e$B$H$b$$$&!#
\e(B
763 <cf node="JIS X0208">
769 \e$BF|K\8l$rI=$9$?$a$K:n$i$l$?
\e(B <a node="94x94 character set">94
\e$B!_
\e(B94
\e$BJ8;z=8
\e(B
770 \e$B9g
\e(B</a>
\e$B!#F|K\$N9q2HI8=`!#
\e(B1978
\e$BG/HG!"
\e(B1983
\e$BG/HG!"
\e(B1990
\e$BG/HG$,$"$k$,!"
\e(B
771 Internet
\e$B$G$O
\e(B 1983
\e$BG/HG$,$b$C$H$bNI$/;H$o$l$F$$$k!#
\e(B
773 JIS X0208
\e$B$O5-9f!"?t;z!"%m!<%^;z!"$R$i$,$J!"%+%?%+%J!"%.%j%7%cJ8;z!"%-
\e(B
774 \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
775 \e$B$N0lIt$N5-9f$H7S@~AG$O
\e(B 1978
\e$BG/HG$K$O$J$$!#$^$?!"0lIt$N4A;z$N;z7A$,
\e(B
776 1983
\e$BG/HG$G$OJQ99$5$l!"$^$?!"Bh#1?e=`$HBh#2?e=`$,F~$lBX$o$C$F$$$?$j$9
\e(B
777 \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
779 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
780 \e$B$r;X<($9$k>l9g$OA0$K99?7%7!<%1%s%9$rMQ$$$k!#
\e(B
782 <standard abbrev="JIS X0208-1978" org="
\e$BF|K\5,3J6(2q
\e(B (Japanese Standards
783 Association)" title-ja="
\e$B>pJs8r49MQ4A;zId9f7O
\e(B"
784 title-en="Code of the Japanese graphic character set for
785 information interchange" number="JIS C6226" year="1978">
786 <standard abbrev="JIS X0208-1983,1990" org="
\e$BF|K\5,3J6(2q
\e(B (Japanese Standards
787 Association)" title-ja="
\e$B>pJs8r49MQ4A;zId9f7O
\e(B"
788 title-en="Code of the Japanese graphic character set for
789 information interchange" number="JIS X0208" year="1983,1990">
792 \e$B$^$?!"
\e(B1996
\e$BG/$K2~DjHG$,=PHG$5$l$kM=Dj!#!J;z7A$NJQ99$O9T$o$l$J$$$N$GJ8
\e(B
793 \e$B;z=89g$H$7$F$O
\e(B 1990
\e$BG/HG$HF10l$G$"$k!K
\e(B
795 <standard abbrev="JIS X0208-1996?" org="
\e$BF|K\5,3J6(2q
\e(B (Japanese
796 Standards Association)" title-ja="
\e$B#7%S%C%H5Z$S#8%S%C%H$N
\e(B
797 \e$B#2%P%$%H>pJs8r49MQId9f2=4A;z=89g
\e(B" title-en="7-bit and
798 8-bit double byte coded Kanji sets for information
799 interchange" number="JIS X 0208" year="1996? draft">
805 <a node="JIS X0208">JIS X0208</a>
\e$B$K$J$+$C$?J8;z$r=8$a$?
\e(B <a
806 node="94x94 character set">94
\e$B!_
\e(B94
\e$BJ8;z=89g
\e(B</a>
\e$B!#!VJd=u4A;z!W$H$b8F$P$l
\e(B
807 \e$B$k!#F|K\$N9q2HI8=`!#
\e(B<a node="ISO 2022">ISO 2022</a>
\e$B$G$N=*C<J8;z$O
\e(B
814 \e$B%m%7%d8lEy$GMQ$$$i$l$k%-%j%kJ8;z$rI=8=$9$k$?$a$N
\e(B <a node="MIME
815 charset">MIME charset</a>
\e$B$N#1$D!#
\e(B
817 <a node="ISO 2022">ISO 2022</a>
\e$B$K4p$+$J$$
\e(B <a node="8bit">8bit</a>
\e$B$N
\e(B
818 <a node="Coded character set">
\e$BId9f2=J8;z=89g
\e(B</a>
\e$B$G
\e(B de-fact standard
\e$B$G
\e(B
821 RFC 1489
\e$B$GDj5A$5$l$F$$$k!#
\e(B
823 <rfc number="1489" author="A. Chernov" title="Registration of a
824 Cyrillic Character Set" date="July 1993">
830 \e$B4Z9q8l$rI=$9$?$a$N
\e(B <a node="94x94 character set">94
\e$B!_
\e(B94
\e$BJ8;z=89g
\e(B</a>
\e$B!#
\e(B
831 \e$B4Z9q$N9q2HI8=`!#
\e(B<a node="ISO 2022">ISO 2022</a>
\e$B$G$N=*C<J8;z$O
\e(B `C'.
833 <standard abbrev="KS C5601" org="Korea Industrial Standards
834 Association" title-en="Code for Information Interchange
835 (Hangul and Hanja)" number="KS C 5601" year="1987">
841 \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
842 1036</dref>
\e$B$GDj5A$5$l$k
\e(B news
\e$B5-;v$NAm>N$H$7$FMQ$$$k!#
\e(B
846 <node> message/rfc822
848 <concept>message/rfc822</concept> indicates that the body contains an
849 encapsulated message, with the syntax of an <dref>RFC 822</dref>
850 message. It is the replacement of traditional <dref>RFC 934</dref>
851 encapsulation. It is defined in <dref>RFC 2046</dref>.
857 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
858 program. Emacs Lisp
\e$B$G=q$+$l$?
\e(B <concept>internal method</concept>
\e$B$H
\e(B C
859 \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
861 <cf file="tm-view-en" node="method">
867 MIME stands for <concept>Multipurpose Internet Mail
868 Extensions</concept>, it is an extension for <dref>RFC 822</dref>.
870 According to RFC 2045:
872 STD 11, RFC 822, defines a message representation protocol specifying
873 considerable detail about US-ASCII message headers, and leaves the
874 message content, or message body, as flat US-ASCII text. This set of
875 documents, collectively called the Multipurpose Internet Mail
876 Extensions, or MIME, redefines the format of messages to allow for
879 <li>textual message bodies in character sets other than US-ASCII,
881 <li>an extensible set of different formats for non-textual message
884 <li>multi-part message bodies, and
886 <li>textual header information in character sets other than US-ASCII.
890 It is defined in <dref>RFC 2045</dref>, <dref>RFC 2046</dref>, <a
891 node="encoded-word">RFC 2047</a>, <dref>RFC 2048</dref> and <dref>RFC
898 <dref>Coded character set</dref> used in <dref>Content-Type
899 field</dref> or charset parameter of <a
900 node="encoded-word">encoded-word</a>.
902 It is defined in <dref>RFC 2045</dref>.
904 <a node="iso-2022-jp">iso-2022-jp</a>
\e$B$d
\e(B <a node="euc-kr">euc-kr</a>
905 \e$B$O$=$N#1$D!#!J$3$3$G$O!"
\e(BMIME charset
\e$B$O
\e(B<a node="Character set">
\e$BJ8;z=8
\e(B
906 \e$B9g
\e(B</a>
\e$B$H6hJL$7$F>.J8;z$G=q$$$F$$$k!K
\e(B
912 <concept>Message Transfer Agent</concept>
\e$B$NN,$G!"
\e(Bsendmail
\e$B$J$I$N
\e(B mail
913 \e$BG[Aw
\e(B program
\e$B$H
\e(B news server
\e$B$NAm>N!#
\e(B
921 <concept>Message User Agent</concept>
\e$B$NN,$G!"
\e(Bmail reader
\e$B$H
\e(B news
922 reader
\e$B$NAm>N!#
\e(B
930 \e$BH>ED
\e(B
\e$B7u0l;a$i$,:n$C$?!"B?8@8l$5$l$?
\e(B <a node="Emacs">Emacs</a>.
932 [MULE] Nishikimi M., Handa K. and Tomura S., ``Mule: MULtilingual
933 Enhancement to GNU Emacs'', Proc. of INET'93, August, 1993.
935 \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
936 href="ftp://etlport.etl.go.jp/pub/mule/mule-19.33-gamma.taz"> alpha
\e$BHG
\e(B
937 </a>
\e$B$,B8:_$9$k!#
\e(B
939 \e$B$=$NB>!"
\e(BXEmacs
\e$B$K
\e(B merge
\e$B$7$?$b$N$bB8:_$9$k!#
\e(B
941 \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
944 \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
945 \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
946 <concept>Emacs/mule</concept>, mule
\e$B5!G=$r
\e(B merge
\e$B$7$?
\e(B XEmacs
\e$B$r
\e(B
947 <concept>XEmacs/mule</concept>
\e$B$H8F$V$3$H$K$9$k!#
\e(B
953 <concept>multipart</concept> means <dref>media type</dref> to insert
954 multiple <dref>entities</dref> in a single body. Or it also indicates
955 a message consists of multiple entities.
957 There are following subtypes registered in <dref>RFC 2046</dref>:
960 <li><dref>multipart/mixed</dref>
961 <li><dref>multipart/alternative</dref>
962 <li><dref>multipart/digest</dref>
963 <li><dref>multipart/parallel</dref>
967 and registered in <a node="Security multipart">RFC 1847</a>:
970 <li><dref>multipart/signed</dref>
971 <li><dref>multipart/encrypted</dref>
975 <h3> multipart/alternative
976 <node> multipart/alternative
978 <concept>multipart/digest</concept> is one of <dref>multipart</dref>
979 media types. This type is syntactically identical to
980 <dref>multipart/mixed</dref>, but the semantics are different. In
981 particular, each of the body parts is an ``alternative'' version of
982 the same information.
987 <h3> multipart/digest
988 <node> multipart/digest
990 <concept>multipart/digest</concept> is one of <dref>multipart</dref>
991 media types. This type is syntactically identical to
992 <dref>multipart/mixed</dref>, but the semantics are different. In
993 particular, in a digest, the default Content-Type value for a body
994 part is changed from <dref>text/plain</dref> to
995 <dref>message/rfc822</dref>.
997 This is the replacement of traditional <dref>RFC 1153</dref> based
998 <dref>encapsulation</dref>.
1000 <cf node="RFC 2046">
1003 <h3> multipart/encrypted
1004 <node> multipart/encrypted
1006 RFC 1847
\e$B$GDj5A$5$l$?
\e(B <dref>Security multipart</dref>
\e$B$N#1$D$G!"0E9f2=
\e(B
1007 \e$B$5$l$?
\e(B message
\e$B$rI=8=$9$k$N$KMQ$$$k!#
\e(B
1009 <cf node="PGP/MIME">
1012 <h3> multipart/mixed
1013 <node> multipart/mixed
1015 Primary and default subtype of <dref>multipart</dref>, it is used when
1016 the body parts are independent and need to be bundled in a particular
1019 <cf node="RFC 2046">
1022 <h3> multipart/parallel
1023 <node> multipart/parallel
1025 <concept>multipart/parallel</concept> is a subtype of
1026 <dref>multipart</dref>. This type is syntactically identical to
1027 <dref>multipart/mixed</dref>, but the semantics are different. In
1028 particular, in a parallel entity, the order of body parts is not
1031 <cf node="RFC 2046">
1034 <h3> multipart/signed
1035 <node> multipart/signed
1037 RFC 1847
\e$B$GDj5A$5$l$?
\e(B <dref>Security multipart</dref>
\e$B$N#1$D$G!"EE;R=p
\e(B
1038 \e$BL>$rI=8=$9$k$N$KMQ$$$k!#
\e(B
1040 <cf node="PGP/MIME">
1046 Phil Zimmermann
\e$B;a$,:n@.$7$?8x3+800E9f=hM}7O$N#1$D!#
\e(B
1047 <dref>message</dref>
\e$B$N0E9f2=$dEE;R=pL>$r9T$&$3$H$,$G$-$k!#
\e(BPretty Good
1048 Privacy
\e$B$NN,!#
\e(B
1050 \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
1051 \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
1052 <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
1053 encapsulation
\e$B$rMQ$$$kJ}K!
\e(B <cf node="PGP-kazu">
\e$B$bMxMQ$5$l$F$-$?!#$7$+
\e(B
1054 \e$B$7!":#8e$O
\e(B PGP/MIME
\e$B$KE}0l$7$F$$$/J}$,K>$^$7$$!#
\e(B
1056 <rfc name="PGP" number="1991" type="Informational" author="D. Atkins,
1057 W. Stallings and P. Zimmermann" title="PGP Message
1058 Exchange Formats" date="August 1996">
1065 \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
1066 node="PGP">PGP</a>
\e$B$rMxMQ$9$k$?$a$NJ}K!$r$3$3$G$O
\e(B
1067 <concept>PGP-kazu</concept>
\e$B$H8F$V$3$H$K$9$k!#
\e(B
1069 PGP-kazu
\e$B$O
\e(B <concept>application/pgp</concept>
\e$B$H$$$&
\e(B
1070 <dref>content-type</dref>
\e$B$rDj5A$9$k!#
\e(B
1072 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
1073 \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
1074 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
1075 \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
1076 \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
1077 \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
1078 message
\e$B$rFI$`$3$H$,$G$-$k!#
\e(B
1080 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
1081 \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
1082 \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
1084 \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
1085 \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
1088 [draft-kazu-pgp-mime-00.txt] Yamamoto K., ``PGP MIME Integration'',
1095 Michael Elkins
\e$B;a$,Ds0F$7$?
\e(B <a node="MIME">MIME</a>
\e$B$G
\e(B <a
1096 node="PGP">PGP</a>
\e$B$rMxMQ$9$k$?$a$NJ}K!!#
\e(B
1098 <a node="Security multipart">RFC 1847</a>
\e$B$K4p$-!"
\e(BMIME
\e$B$N
\e(B multipart
\e$B$K
\e(B
1099 \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
1100 \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
1102 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
1103 \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
1104 \e$B$&$3$H$,$G$-$k!#
\e(B
1106 Internet
\e$B$G$O:#8e
\e(B <dref>PGP/MIME</dref>
\e$B$NJ}8~$GI8=`2=$7$F$$$3$&$H$$$&
\e(B
1107 \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
1108 \e$B$$$k$N$,K>$^$7$$!#
\e(B
1110 <rfc name="PGP/MIME" number="2015" type="Standards Track"
1111 author="M. Elkins" title="MIME Security with Pretty Good
1112 Privacy (PGP)" date="October 1996">
1115 <h3> Quoted-Printable
1116 <node> Quoted-Printable
1118 <concept>Quoted-Printable</concept> is a transfer encoding method of
1119 <dref>MIME</dref> defined in <dref>RFC 2045</dref>.
1121 If the data being encoded are mostly US-ASCII text, the encoded form
1122 of the data remains largely recognizable by humans.
1130 <concept>SMTP</concept>
\e$B$H8F$P$l$k
\e(B Internet mail
\e$B$NG[AwK!$NI8=`$rDj$a
\e(B
1133 <rfc name="SMTP" number="821" type="STD 10" author="J. Postel"
1134 title="Simple Mail Transfer Protocol" date="August
1141 Internet mail
\e$B$N<g$K
\e(B <concept>message header</concept>
\e$B$K4X$9$k7A<0$K
\e(B
1142 \e$B4X$9$kI8=`$rDj$a$F$$$k
\e(B RFC.
1146 news message
\e$B$b$3$l$K=`$8$F$$$k$N$G!"
\e(B<concept>Internet mail</concept>
1147 \e$B$H=q$/$h$j$b!"
\e(B<concept>Internet message</concept>
\e$B$H=q$$$?J}$,NI$$$+$b
\e(B
1151 <rfc number="822" type="STD 11" author="D. Crocker" title="Standard
1152 for the Format of ARPA Internet Text Messages"
1159 <a node="RFC 822">Internet mail</a>
\e$B$N
\e(B <a node="encapsulation">
1160 <concept>encapsulation</concept></a>
\e$B$NJ}K!$rDj$a$?
\e(B RFC.
1162 <dref>MIME</dref>
\e$B$HL7=b$9$k$N$G!"8=:_$G$O
\e(B <dref>message/rfc822</dref>
1163 \e$B$rMQ$$$k$Y$-$G$"$k!#
\e(B
1166 <rfc number="934" author="Marshall T. Rose and Einar A. Stefferud"
1167 title="Proposed Standard for Message Encapsulation"
1168 date="January 1985">
1174 USENET
\e$B$G$N
\e(B message
\e$B$N7A<0$rDj$a$?
\e(B RFC. <a node="RFC 822">RFC 822</a>
1175 \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
1176 netnews
\e$B$G$b$3$l$K=`$8$F$$$k$b$N$,B?$$!#
\e(B
1178 <rfc name="USENET" number="1036" author="M. Horton and R. Adams"
1179 title="Standard for Interchange of USENET Messages"
1180 date="December 1987" obsolete="850">
1186 \e$BJ#?t$N
\e(B <a node="RFC 822">Internet mail</a>
\e$B$r
\e(B <a node="encapsulation">
1187 <concept>encapsulation</concept></a>
\e$B$9$k$?$a$NJ}K!$rDj$a$?
\e(B
1188 RFC. <dref>RFC 934</dref>
\e$B$rMQ$$$k!#
\e(B
1190 <dref>MIME</dref>
\e$B$HL7=b$9$k$N$G!"8=:_$G$O
\e(B <dref>message/rfc822</dref>
1191 \e$B$rMQ$$$?
\e(B <dref>multipart</dref>
\e$B$rMQ$$$k$Y$-$G$"$k!#
\e(B
1193 <cf node="multipart/digest">
1195 <rfc number="1153" author="F. Wancho" title="Digest Message Format"
1202 <dref>euc-kr</dref>
\e$B$H
\e(B <dref>iso-2022-kr</dref>
\e$B$H$$$&4Z9q8l$N$?$a$N
\e(B
1203 <a node="MIME charset">MIME charset</a>
\e$B$rDj5A$7$F$$$k
\e(B RFC.
1205 <rfc number="1557" type="Informational" author="U. Choi, K. Chon and
1206 H. Park" title="Korean Character Encoding for Internet
1207 Messages" date="December 1993">
1213 <dref>iso-2022-cn</dref>, <dref>iso-2022-cn-ext</dref>,
1214 <dref>cn-gb</dref>, <dref>cn-big5</dref>
\e$B$H$$$C$?Cf9q8l$N$?$a$N
\e(B <a
1215 node="MIME charset">MIME charset</a>
\e$B$rDj5A$7$F$$$k
\e(B RFC.
1217 \e$B$3$l$K2C$($F!"
\e(B<concept>charset-edition</concept>
\e$B$H
\e(B
1218 <concept>charset-extension</concept>
\e$B$H$$$&
\e(B <dref>Content-Type
1219 field</dref>
\e$B$N
\e(B parameter
\e$B$rDj5A$7$F$$$k!#
\e(B
1221 <rfc number="1922" type="Informational" author="Zhu, HF., Hu, DY.,
1222 Wang, ZG., Kao, TC., Chang, WCH. and Crispin, M."
1223 title="Chinese Character Encoding for Internet Messages"
1230 <rfc number="2045" type="Standards Track" author="N. Freed and
1231 N. Borenstein" title="Multipurpose Internet Mail
1232 Extensions (MIME) Part One: Format of Internet Message
1233 Bodies" date="November 1996" obsolete="1521, 1522,
1240 <rfc number="2046" type="Standards Track" author="N. Freed and
1241 N. Borenstein" title="Multipurpose Internet Mail
1242 Extensions (MIME) Part Two: Media Types"
1243 date="November 1996" obsolete="1521, 1522, 1590">
1249 <rfc number="2048" type="Standards Track" author="N. Freed, J. Klensin
1250 and J. Postel" title="Multipurpose Internet Mail
1251 Extensions (MIME) Part Four: Registration Procedures"
1252 date="November 1996" obsolete="1521, 1522, 1590">
1258 <rfc number="2049" type="Standards Track" author="N. Freed and
1259 N. Borenstein" title="Multipurpose Internet Mail
1260 Extensions (MIME) Part Five: Conformance Criteria and
1261 Examples" date="November 1996" obsolete="1521, 1522,
1268 \e$B=qBN$dAHHG$K4X$9$k>pJs$r;}$?$J$$
\e(B <a node="Coded character set">
\e$BJ8;zId
\e(B
1269 \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">
1272 <h3> Security multipart
1273 <node> Security multipart
1275 <a node="MIME">MIME</a>
\e$B$G0E9f$dEE;R=qL>$rMQ$$$k$?$a$N7A<0!#
\e(B<a
1276 node="multipart/signed"><concept>multipart/signed</concept></a>
\e$B$H
\e(B <a
1277 node="multipart/encrypted"><concept>multipart/encrypted</concept></a>
1278 \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
1279 \e$B$3$l$K4p$$$F$$$k!#
\e(B
1281 <rfc name="Security multipart" number="1847" type="Standards Track"
1282 author="James Galvin, Gale Murphy, Steve Crocker and Ned
1283 Freed" title="Security Multiparts for MIME:
1284 Multipart/Signed and Multipart/Encrypted" date="October
1289 <node> text/enriched
1291 RFC 1521
\e$B$GDj5A$5$l$?
\e(B <concept>text/richtext</concept>
\e$B$KBe$o$C$F!"=q
\e(B
1292 \e$BBN$dAHHG$K4X$9$k>pJs$r;}$C$?
\e(B text
\e$B$rI=8=$9$k$?$a$N
\e(B <dref>media
1295 <rfc name="text/enriched" number="1896" author="P. Resnick and
1296 A. Walker" title="The text/enriched MIME Content-type"
1297 date="February 1996" obsolete="1563">
1303 <concept>text/plain</concept> is a <dref>media type</dref> for
1304 <dref>plain text</dref>, defined in <dref>RFC 2046</dref>.
1306 The default media type of ``text/plain; charset=us-ascii'' for
1307 Internet mail describes existing Internet practice. That is, it is
1308 the type of body defined by <dref>RFC 822</dref>.
1310 <cf node="MIME charset"><cf node="us-ascii">
1316 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
1317 \e$B6!$9$k
\e(B library
\e$B72!#
\e(B`tools for MIME'
\e$B$NN,!#
\e(B
1319 <memo title="
\e$B$I$&$G$bNI$$$3$H
\e(B(^-^;">
1322 <li> tm
\e$B$O
\e(B ``tiny-mime''
\e$B$NN,$8$c$J$$$i$7$$$>
\e(B (^-^;
1323 <li> tm
\e$B$O:n<T$N%$%K%7%c%k$8$c$J$$$i$7$$$>
\e(B (^-^;
1324 <li> ``Tools for MIME''
\e$B$NN,$H$$$&$N$O$3$8$D$1$i$7$$$>
\e(B (^-^;
1332 <a node="tm-kernel">tm</a>
\e$B$rMQ$$$?
\e(B <a node="MUA">MUA</a>
\e$B$b$7$/$O
\e(B MUA
1333 \e$B$KBP$9$k
\e(B extender.
1335 <concept>tm
\e$BBg@9$j
\e(B package</concept>
\e$B$K$O
\e(B
1338 <li><a file="mh-e">mh-e</a>
\e$BMQ$N
\e(B <concept>tm-mh-e</concept>
1339 <li>GNUS
\e$BMQ$N
\e(B <concept>tm-gnus</concept>
1340 <li>Gnus
\e$BMQ$N
\e(B <a file="gnus-mime-en"><concept>gnus-mime</concept></a>
1341 <li>VM
\e$BMQ$N
\e(B <concept>tm-vm</concept>
1342 <li>RMAIL
\e$BMQ$N
\e(B <concept>tm-rmail</concept>
1346 \e$B$,4^$^$l$F$$$k!#
\e(B
1348 \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
1354 \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
1355 charset">MIME charset</a>
\e$B$N#1$D!#
\e(B
1357 <a node="ASCII">ASCII</a>
\e$B$N$_$+$i$J$j
\e(B <a node="ISO 2022">ISO 2022</a>
1358 \e$B$K$h$k
\e(B<a node="Code extension">
\e$BId9f3HD%
\e(B</a>
\e$B$O5v$5$l$J$$!#
\e(B
1360 Internet mail
\e$B$K$*$1$kI8=`$N
\e(B<a node="Coded character set">
\e$BId9f2=J8;z=8
\e(B
1361 \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
1362 <concept>us-ascii</concept>
\e$B$,;H$o$l$k!#
\e(B
1364 \e$B$^$?!"
\e(B<a node="RFC 822">RFC 822</a>
\e$B$K$*$1$k
\e(B <concept>ASCII</concept>
1365 \e$B$O
\e(B us-ascii
\e$B$r;X$9$b$N$H2r<a$9$Y$-$G$"$k!#
\e(B
1371 In the tm package, two files, <file>mime-setup.el</file> and
1372 <file>tm-setup.el</file>, are provided to ease the setup.
1374 The <file>mime-setup.el</file> is used for the whole MIME related
1375 setup including MIME encoding using <file>tm-edit.el</file>, while
1376 <file>tm-setup.el</file> is used to set up tm-MUA only.
1382 If you want normal setting, please use <concept>mime-setup</concept>.
1383 For example, please insert following into <file>~/.emacs</file>:
1390 As <file>mime-setup.el</file> loads <file>tm-setup.el</file>, you
1391 don't need to load <file>tm-setup.el</file> when you use
1392 <file>mime-setup.el</file> (Description of old version of Gnus FAQ is
1399 You can set up the <concept>automatic signature selection
1400 tool</concept> using <file>mime-setup</file>. If you want to
1401 automatically select the signature file depending on how the message
1402 headers show, add lines like shown below to your .emacs (Refer to the
1403 reference manual of <file>signature.el</file> for more details).
1406 (setq signature-file-alist
1407 '((("Newsgroups" . "jokes") . "~/.signature-jokes")
1408 (("Newsgroups" . ("zxr" "nzr")) . "~/.signature-sun")
1409 (("To" . ("ishimaru" "z-suzuki")) . "~/.signature-sun")
1410 (("To" . "tea") . "~/.signature-jokes")
1411 (("To" . ("sim" "oku" "takuo")) . "~/.signature-formal")
1416 <defvar name="mime-setup-use-signature">
1418 If it is not <code>nil</code>, <file>mime-setup.el</file> sets up for
1419 <file>signature.el</file>. Its default value is <code>t</code>.
1423 <defvar name="mime-setup-signature-key-alist">
1425 It defines key to bind signature inserting command for each
1426 major-mode. Its default value is following:
1429 ((mail-mode . "\C-c\C-w"))
1433 If you want to change, please rewrite it. For example:
1436 (set-alist 'mime-setup-signature-key-alist
1437 'news-reply-mode "\C-c\C-w")
1443 <defvar name="mime-setup-default-signature-key">
1445 If key to bind signature inserting command for a major-mode is not
1446 found from <code>mime-setup-signature-key-alist</code>, its value is
1447 used as key. Its default value is <code>"\C-c\C-s"</code>.
1451 <h3> Notices for GNUS
1452 <node> Notice about GNUS
1454 When <file>mime-setup.el</file> sets up for <file>signature.el</file>,
1455 it sets variable <code>gnus-signature-file</code> to <code>nil</code>.
1456 Therefore GNUS does not insert signature automatically when it is
1457 sending a message. Reason of this setting is following:
1459 GNUS inserts signature after <file>tm-edit.el</file> composed as MIME
1460 message. Therefore signature inserted by GNUS is not processed as a
1461 valid MIME part. In particular, for multipart message, signature
1462 places in outside of MIME part. So MIME MUA might not display it.
1464 Other notice is key bind. In historical reason, key bind to insert
1465 signature is <kbd>C-c C-s</kbd> (like <a file="mh-e">mh-e</a>) instead
1466 of <kbd>C-c C-w</kbd>. If you change to GNUS's default, please set
1470 (set-alist 'mime-setup-signature-key-alist 'news-reply-mode "\C-c\C-w")
1474 <h2> Setting not to use tm-edit
1477 <concept>tm-setup</concept> only sets up <a node="tm-MUA">tm-MUA</a>s.
1478 In other words, it is a setting to avoid to use tm-edit. If you don't
1479 want to compose MIME message or want to use other MIME composer,
1480 please use it instead of <file>mime-setup.el</file>.
1482 For example, please insert following into <file>~/.emacs</file>:
1492 If you use <file>mime-setup.el</file>, you you don't need to load
1493 <file>tm-setup.el</file>.
1498 <node> setting for VM
1500 If you use <concept>vm</concept>, please insert following in
1508 <memo title="Notice">
1510 If you use <concept>BBDB</concept>, please insert <code>(require
1511 'tm-vm)</code> <bf>after</bf> <code>(bbdb-insinuate-vm)</code>.
1515 <h2> Setting up without loading provided setup files
1516 <node> manual setting
1518 You may find the valuable hints in <file>mime-setup.el</file> or
1519 <file>tm-setup.el</file> if you want to set up MIME environment
1520 without loading the tm-provided setup files.
1524 Current tm provides some convenient features to expect tm-edit, and
1525 they can not use if <file>mime-setup.el</file> is not used. If you
1526 want to set up original setting to use tm-edit, please declare
1530 (provide 'mime-setup)
1536 <h1> How to report bug and about mailing list of tm
1539 If you write bug-reports and/or suggestions for improvement, please
1540 send them to the tm Mailing List:
1543 <li> Japanese <mail>bug-tm-ja@chamonix.jaist.ac.jp</mail>
1544 <li> English <mail>bug-tm-en@chamonix.jaist.ac.jp</mail>
1548 Notice that, we does not welcome bug reports about too old version.
1549 Bugs in old version might be fixed. So please try latest version at
1552 You should write <concept>good bug report</concept>. If you write
1553 only ``tm does not work'', we can not find such situations. At least,
1554 you should write name, type, variants and version of OS, emacs, tm and
1555 MUA, and setting. In addition, if error occurs, to send backtrace is
1556 very important. <cf file="emacs" node="Bugs">
1558 Bug may not appear only your environment, but also in a lot of
1559 environment (otherwise it might not bug). Therefor if you send mail
1560 to author directly, we must write a lot of mails. So please send mail
1561 to address for tm bugs instead of author.
1563 Via the tm ML, you can report tm bugs, obtain the latest release of
1564 tm, and discuss future enhancements to tm. To join the tm ML, send
1568 <li> Japanese <mail>tm-ja-admin@chamonix.jaist.ac.jp</mail>
1569 <li> English <mail>tm-en-admin@chamonix.jaist.ac.jp</mail>
1573 Since the user registration is done manually, please write the mail
1574 body in human-recognizable language (^_^).
1578 <node> Concept Index
1584 <node> Variable Index