2 @setfilename tm-en.info
3 @settitle{tm 7.90 Manual (English Version)}
5 @title tm 7.90 Manual (English Version)
6 @author MORIOKA Tomohiko <morioka@@jaist.ac.jp>
9 @node Top, Introduction, (dir), (dir)
10 @top tm 7.90 Manual (English Version)
14 This file documents tm, a MIME package for GNU Emacs.
18 * Introduction:: What is tm?
20 * Bug report:: How to report bug and about mailing list of tm
25 @node Introduction, Setting, Top, Top
28 The tm package is a set of modules to enjoy MIME on GNU Emacs. Using
33 playback or view the MIME messages using tm-view
35 compose MIME message using tm-edit
37 use the enhanced MIME features with mh-e, GNUS, Gnus, RMAIL and VM
43 Please read following about each topics:
47 tm-MUA for Gnus (@ref{(gnus-mime-en)})
49 tm-MUA for GNUS (@ref{(tm-gnus-en)})
51 tm-MUA for mh-e (@ref{(tm-mh-e-en)})
53 mime/viewer-mode (@ref{(tm-view-en)})
55 mime/editor-mode (@ref{(tm-edit-en)})
64 @node Glossary, , Introduction, Introduction
71 * 94 character set:: 94
\e$BJ8;z=89g
\e(B
72 * 96 character set:: 96
\e$BJ8;z=89g
\e(B
73 * 94x94 character set:: 94
\e$B!_
\e(B94
\e$BJ8;z=89g
\e(B
77 * Character Set:: Character Set
\e$B!JJ8;z=89g!K
\e(B
78 * cn-gb:: cn-gb, gb2312
79 * cn-big5:: cn-big5, big5
80 * CNS:: CNS 11643-1992
81 * Coded character set:: Coded character set
\e$B!JId9f2=J8;z=89g!K
\e(B, Character code
\e$B!JJ8;zId9f!K
\e(B
82 * Code extension:: Code extension
\e$B!JId9f3HD%!K
\e(B
83 * Content-Disposition:: Content-Disposition field
85 * Content-Type field::
91 * GB 2312:: GB 2312-1980
92 * GB 8565.2:: GB 8565.2-1988
114 * ISO-IR-165:: ISO-IR-165, CCITT Extended GB
116 * JIS C6226:: JIS C6226-1978
118 * JIS X0212:: JIS X0212-1990
120 * KS C5601:: KS C5601-1987
129 * multipart:: Multipart
130 * multipart/alternative::
132 * multipart/encrypted::
134 * multipart/parallel::
152 * Security multipart::
155 * tm-kernel:: tm-kernel, tm
160 @node 7bit, 8bit, Glossary, Glossary
163 @cindex{7bit}@strong{7bit} means any integer between 0 .. 127.@refill
165 Any data represented by 7bit integers is called @cindex{7bit
166 data}@strong{7bit data}.@refill
168 Textual string consisted of Control characters between 0 .. 31 and 127,
169 and space represented by 32, and graphic characters between 33 .. 236
170 are called @cindex{7bit (textual) string}@strong{7bit (textual)
173 Traditional Internet MTA (@ref{MTA}) can translate 7bit data, so it is
174 no need to translate by Quoted-Printable (@ref{Quoted-Printable}) or
175 Base64 (@ref{Base64}) for 7bit data.@refill
177 However if there are too long lines, it can not translate by 7bit MTA
178 even if it is 7bit data. RFC 821 (@ref{RFC 821}) and RFC 2045 (@ref{RFC
179 2045}) require lines in 7bit data must be less than 998 bytes. So if a
180 ``7bit data'' has a line more than 999 bytes, it is regarded as binary
181 (@ref{binary}). For example, Postscript file should be encoded by
185 @node 8bit, 94 character set, 7bit, Glossary
188 @cindex{8bit}@strong{8bit} means any integer between 0 .. 255.@refill
190 Any data represented by 8bit integers is called @cindex{8bit
191 data}@strong{8bit data}.@refill
193 Textual string consisted of Control characters between 0 .. 31, 127, and
194 128 .. 159, and space represented by 32, and graphic characters between
195 33 .. 236 and 160 .. 255 are called @cindex{8bit (textual)
196 string}@strong{8bit (textual) string}.@refill
198 For example, iso-8859-1 (@ref{iso-8859-1}) or euc-kr (@ref{euc-kr}) are
199 coded-character-set represented by 8bit textual string.@refill
201 Traditional Internet MTA (@ref{MTA}) can translate only 7bit
202 (@ref{7bit}) data, so if a 8bit data will be translated such MTA, it
203 must be encoded by Quoted-Printable (@ref{Quoted-Printable}) or Base64
204 (@ref{Base64}).@refill
206 However 8bit MTA are increasing today.@refill
208 However if there are too long lines, it can not translate by 8bit MTA
209 even if it is 8bit data. RFC 2045 (@ref{RFC 2045}) require lines in
210 8bit data must be less than 998 bytes. So if a ``8bit data'' has a line
211 more than 999 bytes, it is regarded as binary (@ref{binary}), so it must
212 be encoded by Base64 or Quoted-Printable.
215 @node 94 character set, 96 character set, 8bit, Glossary
216 @subsection 94
\e$BJ8;z=89g
\e(B
218 33
\e$B$+$i
\e(B 126
\e$B$NHO0O$N
\e(B 1 byte
\e$B$+$i$J$k
\e(B
\e$BJ8;z=89g
\e(B(@ref{Character set})
\e$B!#
\e(B
219 ASCII (@ref{ASCII})
\e$B$d
\e(B JIS X0201-Latin
\e$B$O$=$N0l<o!#
\e(B
222 @node 96 character set, 94x94 character set, 94 character set, Glossary
223 @subsection 96
\e$BJ8;z=89g
\e(B
225 32
\e$B$+$i
\e(B 127
\e$B$NHO0O$N
\e(B 1 byte
\e$B$+$i$J$k
\e(B
\e$BJ8;z=89g
\e(B(@ref{Character set})
\e$B!#
\e(BISO
226 8859
\e$B%7%j!<%:$O$=$N0l<o!#
\e(B
229 @node 94x94 character set, ASCII, 96 character set, Glossary
230 @subsection 94
\e$B!_
\e(B94
\e$BJ8;z=89g
\e(B
232 33
\e$B$+$i
\e(B 126
\e$B$NHO0O$N
\e(B 2 byte
\e$B$+$i$J$k
\e(B
\e$BJ8;z=89g
\e(B(@ref{Character set})
\e$B!#
\e(BJIS
233 X0208 (@ref{JIS X0208})
\e$B$d
\e(B GB 2312 (@ref{GB 2312})
\e$B$O$=$N0l<o!#
\e(B
236 @node ASCII, Base64, 94x94 character set, Glossary
239 \e$B%"%a%j%+O"K.$G;H$o$l$kJ8;z$rId9f2=$7$?
\e(B 94
\e$BJ8;z=89g
\e(B(@ref{94 character
240 set})
\e$B!#
\e(BA-Z, a-z
\e$B$N
\e(B Latin
\e$BJ8;z$H?t;z!"4v$D$+$N5-9f$+$i$J$k!#
\e(BISO 646
241 (@ref{ISO 646})
\e$B$N0l$D!#
\e(B
243 @cindex{ASCII}@cindex{ANSI X3.4:1986}
247 ``Coded Character Set -- 7-Bit American Standard Code for Information
248 Interchange'', ANSI X3.4:1986.
253 @node Base64, binary, ASCII, Glossary
256 @cindex{Base64}@strong{Base64} is a transfer encoding method of MIME
257 (@ref{MIME}) defined in RFC 2045 (@ref{RFC 2045}).@refill
259 The encoding process represents 24-bit groups of input bits as output
260 strings of 4 encoded characters. Encoded characters represent integer 0
261 .. 63 or @cindex{pad}@strong{pad}. Base64 data must be 4 * n bytes, so
262 pad is used to adjust size.@refill
264 These 65 characters are subset of all versions of ISO 646, including
265 US-ASCII, and all versions of EBCDIC. So it is safe even if it is
266 translated by non-Internet gateways.
269 @node binary, Character Set, Base64, Glossary
272 \e$BG$0U$N
\e(B byte
\e$BNs$r
\e(B @cindex{binary}@strong{binary}
\e$B$H8F$V$3$H$K$7$^$9!#
\e(B
275 8bit (@ref{8bit})
\e$B$H0[$J$k$N$O
\e(B data
\e$B$K9T$N9=B$$r2>Dj$7$J$$$3$H$G$9!#
\e(B
277 \e$B$^$?!"9T$N9=B$$,$"$C$F$b!"
\e(B999 byte
\e$B0J>e$+$i$J$k9T$,$"$k>l9g$b
\e(B binary
\e$B$H8F
\e(B
278 \e$B$V$3$H$K$7$^$9!#
\e(B@refill
280 \e$B$A$J$_$K!"
\e(B7bit (@ref{7bit})
\e$B$d
\e(B 8bit
\e$B$GI=8=$G$-$k
\e(B data
\e$B$O
\e(B binary
\e$B$G$bI=8=
\e(B
281 \e$B$G$-$^$9!#$h$C$F!"
\e(B@cindex{binary data}@strong{binary data}
\e$B$H8@$C$?>l9g!"
\e(B
282 \e$BG$0U$N
\e(B data
\e$B$r;X$9$3$H$,$"$j$^$9!#
\e(B
285 @node Character Set, cn-gb, binary, Glossary
286 @subsection Character Set
\e$B!JJ8;z=89g!K
\e(B
288 \e$BId9f2=J8;z=89g
\e(B(@ref{Coded character set})
\e$B!#C"$7!"$3$3$G$O
\e(B
\e$BId9f3HD%
\e(B
289 (@ref{Code extension})
\e$B$5$l$F$J$$J8;z=89g$H$$$&%K%e%"%s%9$r9~
\e(B
293 @node cn-gb, cn-big5, Character Set, Glossary
294 @subsection cn-gb, gb2312
296 \e$BCf9qBgN&$G$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N
\e(B MIME
297 charset (@ref{MIME charset})
\e$B$N#1$D!#
\e(B@refill
299 ISO 2022 (@ref{ISO 2022})
\e$B$K4p$$$F
\e(B ASCII (@ref{ASCII})
\e$B$K
\e(B GB 2312
300 (@ref{GB 2312})
\e$B$r
\e(B 8bit (@ref{8bit})
\e$B$GId9f3HD%
\e(B (@ref{Code extension})
\e$B$7
\e(B
301 \e$B$F$$$k!#
\e(B@refill
303 RFC 1922 (@ref{RFC 1922})
\e$B$GDj5A$5$l$F$$$k!#
\e(B
306 @node cn-big5, CNS, cn-gb, Glossary
307 @subsection cn-big5, big5
309 \e$BBfOQ$d9a9A$GMQ$$$i$l$F$$$k<g$KHKBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N
\e(B
310 MIME charset (@ref{MIME charset})
\e$B$N#1$D!#
\e(B@refill
312 ISO 2022 (@ref{ISO 2022})
\e$B$K4p$+$J$$
\e(B 8bit (@ref{8bit})
\e$B$NId9f2=J8;z=89g
\e(B
313 (@ref{Coded character set})
\e$B$G
\e(B de-fact standard
\e$B$G$"$k!#
\e(BRFC 1922
314 (@ref{RFC 1922})
\e$B$GDj5A$5$l$F$$$k!#
\e(B@refill
320 Institute for Information Industry, ``Chinese Coded Character Set in
321 Computer'', March 1984.
324 CNS 11643-1986 (@ref{CNS})
\e$B$HBP1~4X78$,$"$k!#
\e(B
327 @node CNS, Coded character set, cn-big5, Glossary
328 @subsection CNS 11643-1992
330 \e$BBfOQ$d9a9A$GMQ$$$i$l$F$$$k<g$KHKBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N
\e(B
331 \e$BJ8;z=89g
\e(B(@ref{Character set})
\e$B!#BfOQ$NI8=`!#8=:_!"
\e(B94
\e$B!_
\e(B94 (@ref{94x94
332 character set})
\e$B$NLL$,Bh#1LL$+$iBh#7LL$^$G$"$k!#
\e(B@refill
334 ISO 2022 (@ref{ISO 2022})
\e$B$G$N=*C<J8;z$O!"Bh#1LL$,
\e(B `G',
\e$BBh#2LL$,
\e(B `H',
\e$BBh
\e(B
335 \e$B#3LL$,
\e(B `I',
\e$BBh#4LL$,
\e(B `J',
\e$BBh#5LL$,
\e(B `K',
\e$BBh#6LL$,
\e(B `L',
\e$BBh#7LL$,
\e(B `M'
\e$B$G$"
\e(B
338 @cindex{CNS 11643-1992}@cindex{CNS 11643:1992}
342 ``Standard Interchange Code for Generally-Used Chinese Characters'', CNS
348 @node Coded character set, Code extension, CNS, Glossary
349 @subsection Coded character set
\e$B!JId9f2=J8;z=89g!K
\e(B, Character code
\e$B!JJ8;zId9f!K
\e(B
351 \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
354 @node Code extension, Content-Disposition, Coded character set, Glossary
355 @subsection Code extension
\e$B!JId9f3HD%!K
\e(B
357 \e$BM?$($i$l$?J8;z=89g
\e(B(@ref{Character set})
\e$B$K4^$^$l$F$$$J$$J8;z$NId9f2=$N$?
\e(B
358 \e$B$a$KMQ$$$k<jK!!#
\e(BISO 2022 (@ref{ISO 2022})
\e$B$O$=$N#1$D!#
\e(B
361 @node Content-Disposition, media type, Code extension, Glossary
362 @subsection Content-Disposition field
364 Content
\e$B$NI=<($N;EJ}$d
\e(B file
\e$BL>$rI=8=$9$k$?$a$N
\e(B field. MIME (@ref{MIME})
365 \e$B$N3HD%$N#1$D!#
\e(B@refill
367 @cindex{Experimental}@cindex{RFC 1806}
371 E R. Troost and S. Dorner, ``Communicating Presentation Information in
372 Internet Messages: The Content-Disposition Header'', June 1995,
378 @node media type, Content-Type field, Content-Disposition, Glossary
379 @subsection media type
381 @cindex{media type}@strong{media type} specifies the nature of the data
382 in the body of MIME (@ref{MIME}) entity (@ref{entity}). It consists of
383 @cindex{type}@strong{type} and @cindex{subtype}@strong{subtype}. It is
384 defined in RFC 2046 (@ref{RFC 2046}).@refill
386 Currently there are following types:
390 @cindex{text}@strong{text}
392 @cindex{image}@strong{image}
394 @cindex{audio}@strong{audio}
396 @cindex{video}@strong{video}
398 @cindex{application}@strong{application}
400 @cindex{multipart}@strong{multipart} (@ref{multipart})
402 @cindex{message}@strong{message}
406 And there are various subtypes, for example, application/octet-stream,
407 audio/basic, image/jpeg, multipart/mixed (@ref{multipart/mixed}),
408 text/plain (@ref{text/plain}), video/mpeg...@refill
410 You can refer registered media types at MEDIA TYPES
411 (ftp://ftp.isi.edu/in-notes/iana/assignments/media-types).@refill
413 In addition, you can use private type or subtype using
414 @cindex{x-token}@strong{x-token}, which as the prefix `x-'. However you
415 can not use them in public.@refill
417 (cf. @ref{Content-Type field})
421 @node Content-Type field, Emacs, media type, Glossary
422 @subsection Content-Type field
424 Header field to represent information about body, such as media type
425 (@ref{media type}), MIME charset (@ref{MIME charset}). It is defined in
426 RFC 2045 (@ref{RFC 2045}).
432 Historically, Content-Type field was proposed in RFC 1049. In it,
433 Content-Type did not distinguish type and subtype. However MIME parser
434 may be able to accept RFC 1049 based Content-Type as unknown type.
438 Content-Type field is defined as following:
441 ``Content-Type'' ``:'' @cindex{type}@strong{type} ``/''
442 @cindex{subtype}@strong{subtype} *( ``;'' @cindex{parameter}@strong{parameter} )
450 Content-Type: image/jpeg
457 Content-Type: text/plain; charset=iso-2022-jp
466 A part does not have content-type field is regarded as
470 Content-Type: text/plain; charset=us-ascii
478 And a part has unknown type/subtype is regarded as
482 Content-Type: application/octet-stream
490 @node Emacs, encoded-word, Content-Type field, Glossary
493 \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
494 GNU Emacs
\e$B$NJQ<o$NAm>N$H$9$k!#
\e(B
497 @node encoded-word, encapsulation, Emacs, Glossary
498 @subsection encoded-word
500 Representation non ASCII (@ref{ASCII}) characters in header. It is
501 defined in @cindex{RFC 2047}@strong{RFC 2047}.@refill
503 @cindex{Standards Track}@cindex{RFC 2047}
507 K. Moore, ``MIME (Multipurpose Internet Mail Extensions) Part Three:
508 Message Header Extensions for Non-ASCII Text'', November 1996, Standards
509 Track (obsolete RFC 1521,1522,1590).
514 @node encapsulation, euc-kr, encoded-word, Glossary
515 @subsection encapsulation
517 Internet mail (@ref{RFC 822})
\e$B$rB>$N5-;v$K$^$k$4$HF~$l$kJ}K!!#
\e(B@refill
519 \e$BNc$($P!"5-;v$rE>Aw$7$?$j$9$k$N$KMQ$$$k!#
\e(B@refill
521 (cf. @ref{message/rfc822})
525 @node euc-kr, FTP, encapsulation, Glossary
528 \e$B4Z9q8l$rI=8=$9$k$?$a$N
\e(B MIME charset (@ref{MIME charset})
\e$B$N#1$D!#
\e(B
530 ISO 2022 (@ref{ISO 2022})
\e$B$K4p$$$F
\e(B ASCII (@ref{ASCII})
\e$B$K
\e(BKS C5601
531 (@ref{KS C5601})
\e$B$r
\e(B 8bit (@ref{8bit})
\e$B$GId9f3HD%
\e(B (@ref{Code extension})
532 \e$B$7$F$$$k!#
\e(B@refill
534 RFC 1557 (@ref{RFC 1557})
\e$B$GDj5A$5$l$F$$$k!#
\e(B@refill
536 cf. @cindex{euc-kr}@cindex{KS C 5861:1992}
540 Korea Industrial Standards Association, ``Hangul Unix Environment'', KS
546 @node FTP, GB 2312, euc-kr, Glossary
549 Internet
\e$B$G
\e(B file
\e$B$rE>Aw$9$k$?$a$N
\e(B protocol
\e$B$N#1$D!#
\e(BRFC 959
\e$B$GDj5A$5$l$F
\e(B
550 \e$B$$$k!#
\e(B@refill
552 @cindex{FTP}@cindex{STD 9}@cindex{RFC 959}
556 Postel, J. and J. Reynolds, ``File Transfer Protocol'', October 1985,
562 @node GB 2312, GB 8565.2, FTP, Glossary
563 @subsection GB 2312-1980
565 \e$BCf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=$9$?$a$N
\e(B 94
\e$B!_
\e(B94
\e$BJ8;z
\e(B
566 \e$B=89g
\e(B(@ref{94x94 character set})
\e$B!#Cf9q$N9q2HI8=`!#
\e(BISO 2022 (@ref{ISO
567 2022})
\e$B$G$N=*C<J8;z$O
\e(B `A'.@refill
569 \e$B$3$l$O
\e(B GB
\e$B$K$*$1$k4pK\=8$G$"$k!#
\e(B
571 @cindex{GB 2312}@cindex{GB 2312:1980}
575 \e$B!X?.B)8r49MQ4A;zJTb{;zId=8
\e(B --
\e$B4pK\=8!Y
\e(B, ``Code of Chinese Graphic
576 Character Set for Information Interchange - Primary Set'', GB 2312:1980.
581 @node GB 8565.2, hz-gb2312, GB 2312, Glossary
582 @subsection GB 8565.2-1988
584 \e$BCf9q8l$N$?$a$NJd=uJ8;z=89g
\e(B(@ref{Character set})
\e$B!#Cf9q$N9q2HI8=`!#
\e(BGB 2312
585 (@ref{GB 2312})
\e$B$N6u$-ItJ,$KJd=<$9$k$h$&$KDj5A$5$l$?$i$7$$!#
\e(B
587 @cindex{GB 8565.2}@cindex{GB 8565.2:1988}
591 ``Information Processing - Coded Character Sets for Text Communication -
592 Part 2: Graphic Characters used with Primary Set'', GB 8565.2:1988.
597 @node hz-gb2312, ISO 2022, GB 8565.2, Glossary
598 @subsection hz-gb2312
600 \e$BCf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N
\e(B MIME
601 charset (@ref{MIME charset})
\e$B$N#1$D!#
\e(B@refill
603 ASCII (@ref{ASCII})
\e$B$K
\e(B GB 2312 (@ref{GB 2312})
\e$B$r
\e(B 7bit
\e$B$GId9f3HD%
\e(B
604 (@ref{Code extension})
\e$B$7$?$b$N$r
\e(B ASCII printable
\e$B$K$J$k$h$&$K9)IW$7$F$$
\e(B
607 RFC 1842, 1843
\e$B$GDj5A$5$l$F$$$k!#
\e(B
609 @cindex{Informational}@cindex{RFC 1842}
613 Y. Wei, Y. Zhang, J. Li, J. Ding and Y. Jiang, ``ASCII Printable
614 Characters-Based Chinese Character Encoding for Internet Messages'',
615 August 1995, Informational.
618 @cindex{Informational}@cindex{RFC 1843}
622 F. Lee, ``HZ - A Data Format for Exchanging Files of Arbitrarily Mixed
623 Chinese and ASCII characters'', August 1995, Informational.
628 @node ISO 2022, iso-2022-cn, hz-gb2312, Glossary
631 \e$BId9f3HD%
\e(B(@ref{Code extension})
\e$B$N$?$a$N9q:]I8=`!#
\e(B@refill
633 \e$B$3$l$rMQ$$$FJ#?t$NJ8;z=89g
\e(B(@ref{Character set})
\e$B$rAH9g$;$F
\e(B 7bit
634 (@ref{7bit})
\e$B$J$$$7
\e(B 8bit (@ref{8bit})
\e$B$N
\e(B
\e$BId9f2=J8;z=89g
\e(B(@ref{Coded
635 character set})
\e$B$r:n$k$3$H$,$G$-$k!#
\e(B
637 @cindex{ISO 2022}@cindex{ISO/IEC 2022:1994}
641 International Organization for Standardization (ISO), ``Information
642 Processing: ISO 7-bit and 8-bit coded character sets: Code extension
643 techniques'', ISO/IEC 2022:1994.
648 @node iso-2022-cn, iso-2022-cn-ext, ISO 2022, Glossary
649 @subsection iso-2022-cn
651 \e$BCf9q8l$rI=8=$9$k$?$a$N
\e(B MIME charset (@ref{MIME charset})
\e$B$N#1$D!#
\e(B
653 ISO 2022 (@ref{ISO 2022})
\e$B$K4p$$$F
\e(B ASCII (@ref{ASCII})
\e$B$K
\e(B GB 2312
654 (@ref{GB 2312}), CNS 11643 plain 1, plain 2 (@ref{CNS})
\e$B$r
\e(B 7bit
655 (@ref{7bit})
\e$B$GId9f3HD%
\e(B (@ref{Code extension})
\e$B$7$F$$$k!#
\e(B@refill
657 RFC 1922 (@ref{RFC 1922})
\e$B$GDj5A$5$l$F$$$k!#
\e(B
660 @node iso-2022-cn-ext, iso-2022-jp, iso-2022-cn, Glossary
661 @subsection iso-2022-cn-ext
663 \e$BCf9q8l$rI=8=$9$k$?$a$N
\e(B MIME charset (@ref{MIME charset})
\e$B$N#1$D!#
\e(B
665 ISO 2022 (@ref{ISO 2022})
\e$B$K4p$$$F
\e(B ASCII (@ref{ASCII})
\e$B$K
\e(B GB 2312
666 (@ref{GB 2312}), CNS 11643 plain 1 .. 7 (@ref{CNS}), ISO-IR-165
667 (@ref{ISO-IR-165})
\e$BEy$r
\e(B 7bit (@ref{7bit})
\e$B$GId9f3HD%
\e(B (@ref{Code
668 extension})
\e$B$7$F$$$k!#
\e(B@refill
670 RFC 1922 (@ref{RFC 1922})
\e$B$GDj5A$5$l$F$$$k!#
\e(B@refill
675 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
677 Emacs/mule
\e$B$G$OMxMQ2DG=$G$"$k!#
\e(B
682 @node iso-2022-jp, iso-2022-jp-2, iso-2022-cn-ext, Glossary
683 @subsection iso-2022-jp
685 \e$BF|K\8l$rI=8=$9$k$?$a$N
\e(B MIME charset (@ref{MIME charset})
\e$B$N0l$D!#
\e(B
687 \e$B8E$$
\e(B ISO 2022 (@ref{ISO 2022})
\e$B$K4p$$$F
\e(B ASCII (@ref{ASCII}), JIS
688 X0201-Latin, JIS X0208-1978 (@ref{JIS C6226-1978}), JIS X0208-1983
689 (@ref{JIS X0208})
\e$B$r@Z$jBX$($k
\e(B 7bit (@ref{7bit})
\e$BJ8;zId9f!#
\e(B@refill
691 RFC 1468
\e$B$GDj5A$5$l$F$$$k!#
\e(B@refill
696 JIS X0208-1996?
\e$B$G$O
\e(B ISO 2022 (@ref{ISO 2022})
\e$B$HFHN)$KDj5A$5$l$kM=Dj!#
\e(B
700 @cindex{iso-2022-jp}@cindex{RFC 1468}
702 [iso-2022-jp: RFC 1468]
704 Murai J., M. Crispin, and E. van der Poel, ``Japanese Character Encoding
705 for Internet Messages'', June 1993.
710 @node iso-2022-jp-2, iso-2022-kr, iso-2022-jp, Glossary
711 @subsection iso-2022-jp-2
713 iso-2022-jp (@ref{iso-2022-jp})
\e$B$r3HD%$7$?
\e(B MIME charset (@ref{MIME
714 charset})
\e$B$N0l$D!#
\e(B@refill
716 RFC 1554
\e$B$GDj5A$5$l$F$$$k!#
\e(B
718 @cindex{iso-2022-jp-2}@cindex{Informational}@cindex{RFC 1554}
720 [iso-2022-jp-2: RFC 1554]
722 Ohta M. and Handa K., ``ISO-2022-JP-2: Multilingual Extension of
723 ISO-2022-JP'', December 1993, Informational.
728 @node iso-2022-kr, ISO 646, iso-2022-jp-2, Glossary
729 @subsection iso-2022-kr
731 \e$B4Z9q8l$rI=8=$9$k$?$a$N
\e(B MIME charset (@ref{MIME charset})
\e$B$N#1$D!#
\e(B
733 ISO 2022 (@ref{ISO 2022})
\e$B$K4p$$$F
\e(B ASCII (@ref{ASCII})
\e$B$K
\e(B KS C5601
734 (@ref{KS C5601})
\e$B$r
\e(B 7bit (@ref{7bit})
\e$B$GId9f3HD%
\e(B (@ref{Code extension})
735 \e$B$7$F$$$k!#
\e(B@refill
737 RFC 1557 (@ref{RFC 1557})
\e$B$GDj5A$5$l$F$$$k!#
\e(B
740 @node ISO 646, ISO 8859-1, iso-2022-kr, Glossary
743 \e$B3F9q$G6&DL$K;H$($k:G>.8BEY$NJ8;z=89g
\e(B(@ref{Character set})
\e$B$rDj$a$?$b$N!#
\e(B
744 94
\e$BJ8;z=89g
\e(B (@ref{94 character set})
\e$B$N#1$D!#
\e(BISO 646 IRV
\e$B!J9q:]4p=`HG!K$r
\e(B
745 \e$B85$K4v$D$+$NJ8;z$O3F9q$G0c$&J8;z$r3dEv$k$3$H$r5v$7$F$$$F!"4v$D$+$NJQ<o$,
\e(B
746 \e$BB8:_$9$k!#
\e(BASCII (@ref{ASCII})
\e$B$d
\e(B JIS X0201-Latin
\e$B$O$=$N0l<o!#
\e(B
748 @cindex{ISO 646}@cindex{ISO/IEC 646:1991}
752 International Organization for Standardization (ISO), ``Information
753 technology: ISO 7-bit coded character set for information interchange'',
759 @node ISO 8859-1, iso-8859-1, ISO 646, Glossary
760 @subsection ISO 8859-1
762 \e$B@>2$=t8l$GMQ$$$i$l$k3HD%
\e(B Latin
\e$BJ8;z$d5-9f$+$i$J$k
\e(B 96
\e$BJ8;z=89g
\e(B(@ref{96
763 character set})
\e$B!#
\e(B
765 @cindex{ISO 8859-1}@cindex{ISO 8859-1:1987}
769 International Organization for Standardization (ISO), ``Information
770 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 1:
771 Latin Alphabet No.1'', ISO 8859-1:1987.
776 @node iso-8859-1, ISO 8859-2, ISO 8859-1, Glossary
777 @subsection iso-8859-1
779 @cindex{iso-8859-1}@strong{iso-8859-1} is a MIME charset (@ref{MIME
780 charset}) for west-European languages written by Latin script.@refill
782 ISO 2022 (@ref{ISO 2022})
\e$B$K4p$$$F!"
\e(BASCII (@ref{ASCII})
\e$B$K
\e(B ISO 8859-1
783 (@ref{ISO 8859-1})
\e$B$r
\e(B 8bit (@ref{8bit})
\e$B$GId9f3HD%
\e(B (@ref{Code
784 extension})
\e$B$7$F$$$k!#
\e(B@refill
786 It is defined in RFC 2046 (@ref{RFC 2046}).
789 @node ISO 8859-2, iso-8859-2, iso-8859-1, Glossary
790 @subsection ISO 8859-2
792 \e$BEl2$=t8l$GMQ$$$i$l$k3HD%
\e(B Latin
\e$BJ8;z$d5-9f$+$i$J$k
\e(B 96
\e$BJ8;z=89g
\e(B(@ref{96
793 character set})
\e$B!#
\e(B
795 @cindex{ISO 8859-2}@cindex{ISO 8859-2:1987}
799 International Organization for Standardization (ISO), ``Information
800 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 2:
801 Latin alphabet No.2'', ISO 8859-2:1987.
806 @node iso-8859-2, ISO 8859-3, ISO 8859-2, Glossary
807 @subsection iso-8859-2
809 @cindex{iso-8859-2}@strong{iso-8859-2} is a MIME charset (@ref{MIME
810 charset}) for east-European languages written by Latin script.@refill
812 ISO 2022 (@ref{ISO 2022})
\e$B$K4p$$$F!"
\e(BASCII (@ref{ASCII})
\e$B$K
\e(B ISO 8859-2
813 (@ref{ISO 8859-2})
\e$B$r
\e(B 8bit (@ref{8bit})
\e$B$GId9f3HD%
\e(B (@ref{Code
814 extension})
\e$B$7$F$$$k!#
\e(B@refill
816 It is defined in RFC 2046 (@ref{RFC 2046}).
819 @node ISO 8859-3, ISO 8859-4, iso-8859-2, Glossary
820 @subsection ISO 8859-3
822 @cindex{ISO 8859-3}@cindex{ISO 8859-3:1988}
826 International Organization for Standardization (ISO), ``Information
827 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 3:
828 Latin alphabet No.3'', ISO 8859-3:1988.
833 @node ISO 8859-4, ISO 8859-5, ISO 8859-3, Glossary
834 @subsection ISO 8859-4
836 @cindex{ISO 8859-4}@cindex{ISO 8859-4:1988}
840 International Organization for Standardization (ISO), ``Information
841 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 4:
842 Latin alphabet No.4'', ISO 8859-4:1988.
847 @node ISO 8859-5, iso-8859-5, ISO 8859-4, Glossary
848 @subsection ISO 8859-5
850 \e$B%-%j%kJ8;z$d5-9f$+$i$J$k
\e(B 96
\e$BJ8;z=89g
\e(B(@ref{96 character set})
\e$B!#
\e(B
852 @cindex{ISO 8859-5}@cindex{ISO 8859-5:1988}
856 International Organization for Standardization (ISO), ``Information
857 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 5:
858 Latin/Cyrillic alphabet'', ISO 8859-5:1988.
863 @node iso-8859-5, ISO 8859-6, ISO 8859-5, Glossary
864 @subsection iso-8859-5
866 @cindex{iso-8859-5}@strong{iso-8859-5} is a MIME charset (@ref{MIME
867 charset}) for Cyrillic script.@refill
869 ISO 2022 (@ref{ISO 2022})
\e$B$K4p$$$F!"
\e(BASCII (@ref{ASCII})
\e$B$K
\e(B ISO 8859-5
870 (@ref{ISO 8859-5})
\e$B$r
\e(B 8bit (@ref{8bit})
\e$B$GId9f3HD%
\e(B (@ref{Code
871 extension})
\e$B$7$F$$$k!#
\e(B@refill
873 It is defined in RFC 2046 (@ref{RFC 2046}).
876 @node ISO 8859-6, ISO 8859-7, iso-8859-5, Glossary
877 @subsection ISO 8859-6
879 @cindex{ISO 8859-6}@cindex{ISO 8859-6:1987}
883 International Organization for Standardization (ISO), ``Information
884 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 6:
885 Latin/Arabic alphabet'', ISO 8859-6:1987.
890 @node ISO 8859-7, iso-8859-7, ISO 8859-6, Glossary
891 @subsection ISO 8859-7
893 \e$B%.%j%7%"J8;z$d5-9f$+$i$J$k
\e(B 96
\e$BJ8;z=89g
\e(B(@ref{96 character set})
\e$B!#
\e(B
895 @cindex{ISO 8859-7}@cindex{ISO 8859-7:1987}
899 International Organization for Standardization (ISO), ``Information
900 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 7:
901 Latin/Greek alphabet'', ISO 8859-7:1987.
906 @node iso-8859-7, ISO 8859-8, ISO 8859-7, Glossary
907 @subsection iso-8859-7
909 @cindex{iso-8859-7}@strong{iso-8859-7} is a MIME charset (@ref{MIME
910 charset}) for Greek script.@refill
912 ISO 2022 (@ref{ISO 2022})
\e$B$K4p$$$F!"
\e(BASCII (@ref{ASCII})
\e$B$K
\e(B ISO 8859-7
913 (@ref{ISO 8859-7})
\e$B$r
\e(B 8bit (@ref{8bit})
\e$B$GId9f3HD%
\e(B (@ref{Code
914 extension})
\e$B$7$F$$$k!#
\e(B@refill
916 It is defined in RFC 1947.
918 @cindex{iso-8859-7}@cindex{Informational}@cindex{RFC 1947}
920 [iso-8859-7: RFC 1947]
922 D. Spinellis, ``Greek Character Encoding for Electronic Mail Messages'',
923 May 1996, Informational.
928 @node ISO 8859-8, ISO 8859-9, iso-8859-7, Glossary
929 @subsection ISO 8859-8
931 @cindex{ISO 8859-8}@cindex{ISO 8859-8:1988}
935 International Organization for Standardization (ISO), ``Information
936 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 8:
937 Latin/Hebrew alphabet'', ISO 8859-8:1988.
942 @node ISO 8859-9, ISO-IR-165, ISO 8859-8, Glossary
943 @subsection ISO 8859-9
945 @cindex{ISO 8859-9}@cindex{ISO 8859-9:1990}
949 International Organization for Standardization (ISO), ``Information
950 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 9:
951 Latin alphabet No.5'', ISO 8859-9:1990.
956 @node ISO-IR-165, JIS X0201, ISO 8859-9, Glossary
957 @subsection ISO-IR-165, CCITT Extended GB
959 CCITT
\e$B$,EPO?$7$?!"Cf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=
\e(B
960 \e$B$9$k$?$a$N
\e(B 94
\e$B!_
\e(B94
\e$BJ8;z=89g
\e(B(@ref{94x94 character set})
\e$B!#
\e(B@refill
962 GB 2312 (@ref{GB 2312})
\e$B$H
\e(B GB 8565
\e$BI=#2
\e(B (@ref{GB 8865.2})
\e$B$K
\e(B 150
\e$BJ8;z$[
\e(B
963 \e$B$I$rDI2C$7$?$b$N$i$7$$!#
\e(B@refill
965 ISO 2022 (@ref{ISO 2022})
\e$B$G$N=*C<J8;z$O
\e(B `E'
\e$B$G$"$k!#
\e(B
968 @node JIS X0201, JIS C6226, ISO-IR-165, Glossary
969 @subsection JIS X0201
971 ISO 646 (@ref{ISO 646})
\e$B$NJQ<o$N#1$D$G$"$k
\e(B Latin
\e$BJ8;z=89g$H
\e(B 1 byte
\e$B$N%+
\e(B
972 \e$B%?%+%JJ8;z=89g$+$i$J$k!#
\e(B@refill
974 \e$B85$O
\e(B @cindex{JIS C6220-1976}@strong{JIS C6220-1976}
\e$B$H8@$C$?$,
\e(B @cindex{JIS
976 X0201}
\e$B$KHV9f$,JQ99$5$l$?!#
\e(B
978 @cindex{JIS X0201-1976}@cindex{JIS X 0201-1976:}
982 \e$BF|K\5,3J6(2q
\e(B (Japanese Standards Association),
\e$B!X>pJs8r49MQId9f!Y
\e(B, ``Code
983 for Information Interchange'', JIS X 0201-1976:.
987 \e$B$^$?!"
\e(B1996
\e$BG/$K2~DjHG$,=P$kM=Dj!#
\e(B
989 @cindex{JIS X0201-1996?}@cindex{JIS X 0201:1996? draft}
993 \e$BF|K\5,3J6(2q
\e(B (Japanese Standards Association),
\e$B!X#7%S%C%H5Z$S#8%S%C%H$N>p
\e(B
994 \e$BJs8r49MQId9f2=J8;z=89g!Y
\e(B, ``7-bit and 8-bit coded character sets for
995 information interchange'', JIS X 0201:1996? draft.
1000 @node JIS C6226, JIS X0208, JIS X0201, Glossary
1001 @subsection JIS C6226-1978
1003 \e$BF|K\8l$rI=$9$?$a$K:n$i$l$?
\e(B 94
\e$B!_
\e(B94
\e$BJ8;z=89g
\e(B(@ref{94x94 character set})
\e$B!#
\e(B
1004 \e$BF|K\$N9q2HI8=`!#
\e(BJIS X0208-1978
\e$B$H$b$$$&!#
\e(B@refill
1006 (cf. @ref{JIS X0208})
1010 @node JIS X0208, JIS X0212, JIS C6226, Glossary
1011 @subsection JIS X0208
1013 \e$BF|K\8l$rI=$9$?$a$K:n$i$l$?
\e(B 94
\e$B!_
\e(B94
\e$BJ8;z=89g
\e(B(@ref{94x94 character set})
\e$B!#
\e(B
1014 \e$BF|K\$N9q2HI8=`!#
\e(B1978
\e$BG/HG!"
\e(B1983
\e$BG/HG!"
\e(B1990
\e$BG/HG$,$"$k$,!"
\e(BInternet
\e$B$G$O
\e(B
1015 1983
\e$BG/HG$,$b$C$H$bNI$/;H$o$l$F$$$k!#
\e(B@refill
1017 JIS X0208
\e$B$O5-9f!"?t;z!"%m!<%^;z!"$R$i$,$J!"%+%?%+%J!"%.%j%7%cJ8;z!"%-%j
\e(B
1018 \e$B%kJ8;z!"7S@~AG!"Bh#1?e=`!"Bh#2?e=`$N4A;z$,4^$^$l$k!#C"$7!"
\e(B1983
\e$BG/HG$N0l
\e(B
1019 \e$BIt$N5-9f$H7S@~AG$O
\e(B 1978
\e$BG/HG$K$O$J$$!#$^$?!"0lIt$N4A;z$N;z7A$,
\e(B 1983
\e$BG/HG
\e(B
1020 \e$B$G$OJQ99$5$l!"$^$?!"Bh#1?e=`$HBh#2?e=`$,F~$lBX$o$C$F$$$?$j$9$k!#$3$N$?$a!"
\e(B
1021 1978
\e$BG/HG$H
\e(B 1983
\e$BG/HG$O0[$J$kJ8;z=89g$H$7$F07$o$l$k!#
\e(B@refill
1023 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
1024 \e$B$r;X<($9$k>l9g$OA0$K99?7%7!<%1%s%9$rMQ$$$k!#
\e(B
1026 @cindex{JIS X0208-1978}@cindex{JIS C6226:1978}
1030 \e$BF|K\5,3J6(2q
\e(B (Japanese Standards Association),
\e$B!X>pJs8r49MQ4A;zId9f7O!Y
\e(B,
1031 ``Code of the Japanese graphic character set for information
1032 interchange'', JIS C6226:1978.
1035 @cindex{JIS X0208-1983,1990}@cindex{JIS X0208:1983,1990}
1037 [JIS X0208-1983,1990]
1039 \e$BF|K\5,3J6(2q
\e(B (Japanese Standards Association),
\e$B!X>pJs8r49MQ4A;zId9f7O!Y
\e(B,
1040 ``Code of the Japanese graphic character set for information
1041 interchange'', JIS X0208:1983,1990.
1045 \e$B$^$?!"
\e(B1996
\e$BG/$K2~DjHG$,=PHG$5$l$kM=Dj!#!J;z7A$NJQ99$O9T$o$l$J$$$N$GJ8
\e(B
1046 \e$B;z=89g$H$7$F$O
\e(B 1990
\e$BG/HG$HF10l$G$"$k!K
\e(B
1048 @cindex{JIS X0208-1996?}@cindex{JIS X 0208:1996? draft}
1052 \e$BF|K\5,3J6(2q
\e(B (Japanese Standards Association),
\e$B!X#7%S%C%H5Z$S#8%S%C%H$N
\e(B
1053 \e$B#2%P%$%H>pJs8r49MQId9f2=4A;z=89g!Y
\e(B, ``7-bit and 8-bit double byte coded
1054 Kanji sets for information interchange'', JIS X 0208:1996? draft.
1059 @node JIS X0212, koi8-r, JIS X0208, Glossary
1060 @subsection JIS X0212-1990
1062 JIS X0208 (@ref{JIS X0208})
\e$B$K$J$+$C$?J8;z$r=8$a$?
\e(B 94
\e$B!_
\e(B94
\e$BJ8;z=89g
\e(B
1063 (@ref{94x94 character set})
\e$B!#!VJd=u4A;z!W$H$b8F$P$l$k!#F|K\$N9q2HI8=`!#
\e(B
1064 ISO 2022 (@ref{ISO 2022})
\e$B$G$N=*C<J8;z$O
\e(B `D'.
1067 @node koi8-r, KS C5601, JIS X0212, Glossary
1070 \e$B%m%7%d8lEy$GMQ$$$i$l$k%-%j%kJ8;z$rI=8=$9$k$?$a$N
\e(B MIME charset (@ref{MIME
1071 charset})
\e$B$N#1$D!#
\e(B@refill
1073 ISO 2022 (@ref{ISO 2022})
\e$B$K4p$+$J$$
\e(B 8bit (@ref{8bit})
\e$B$NId9f2=J8;z=89g
\e(B
1074 (@ref{Coded character set})
\e$B$G
\e(B de-fact standard
\e$B$G$"$k!#
\e(B
1076 RFC 1489
\e$B$GDj5A$5$l$F$$$k!#
\e(B@refill
1082 A. Chernov, ``Registration of a Cyrillic Character Set'', July 1993.
1087 @node KS C5601, message, koi8-r, Glossary
1088 @subsection KS C5601-1987
1090 \e$B4Z9q8l$rI=$9$?$a$N
\e(B 94
\e$B!_
\e(B94
\e$BJ8;z=89g
\e(B(@ref{94x94 character set})
\e$B!#4Z9q$N9q
\e(B
1091 \e$B2HI8=`!#
\e(BISO 2022 (@ref{ISO 2022})
\e$B$G$N=*C<J8;z$O
\e(B `C'.
1093 @cindex{KS C5601}@cindex{KS C 5601:1987}
1097 Korea Industrial Standards Association, ``Code for Information
1098 Interchange (Hangul and Hanja)'', KS C 5601:1987.
1103 @node message, message/rfc822, KS C5601, Glossary
1106 \e$B$3$3$G$O
\e(B RFC 822 (@ref{RFC 822})
\e$B$GDj5A$5$l$k
\e(B mail
\e$B$H
\e(B RFC 1036 (@ref{RFC
1107 1036})
\e$B$GDj5A$5$l$k
\e(B news
\e$B5-;v$NAm>N$H$7$FMQ$$$k!#
\e(B
1110 @node message/rfc822, method, message, Glossary
1111 @subsection message/rfc822
1113 @cindex{message/rfc822}@strong{message/rfc822} indicates that the body
1114 contains an encapsulated message, with the syntax of an RFC 822
1115 (@ref{RFC 822}) message. It is the replacement of traditional RFC 934
1116 (@ref{RFC 934}) encapsulation. It is defined in RFC 2046 (@ref{RFC
1120 @node method, MIME, message/rfc822, Glossary
1123 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
1124 program. Emacs Lisp
\e$B$G=q$+$l$?
\e(B @cindex{internal method}@strong{internal
1125 method}
\e$B$H
\e(B C
\e$B$d
\e(B script
\e$B8@8l$J$I$G=q$+$l$?
\e(B @cindex{external
1126 method}@strong{external method}
\e$B$,$"$k!#
\e(B@refill
1128 (cf. @ref{(tm-view-en)method})
1132 @node MIME, MIME charset, method, Glossary
1135 MIME stands for @cindex{Multipurpose Internet Mail
1136 Extensions}@strong{Multipurpose Internet Mail Extensions}, it is an
1137 extension for RFC 822 (@ref{RFC 822}).@refill
1139 According to RFC 2045:@refill
1141 STD 11, RFC 822, defines a message representation protocol specifying
1142 considerable detail about US-ASCII message headers, and leaves the
1143 message content, or message body, as flat US-ASCII text. This set of
1144 documents, collectively called the Multipurpose Internet Mail
1145 Extensions, or MIME, redefines the format of messages to allow
1150 textual message bodies in character sets other than US-ASCII,
1152 an extensible set of different formats for non-textual message
1155 multi-part message bodies, and
1157 textual header information in character sets other than US-ASCII.
1161 It is defined in RFC 2045 (@ref{RFC 2045}), RFC 2046 (@ref{RFC 2046}),
1162 RFC 2047 (@ref{encoded-word}), RFC 2048 (@ref{RFC 2048}) and RFC 2049
1166 @node MIME charset, MTA, MIME, Glossary
1167 @subsection MIME charset
1169 Coded character set (@ref{Coded character set}) used in Content-Type
1170 field (@ref{Content-Type field}) or charset parameter of encoded-word
1171 (@ref{encoded-word}).@refill
1173 It is defined in RFC 2045 (@ref{RFC 2045}).@refill
1175 iso-2022-jp (@ref{iso-2022-jp})
\e$B$d
\e(B euc-kr (@ref{euc-kr})
\e$B$O$=$N#1$D!#
\e(B
1176 \e$B!J$3$3$G$O!"
\e(BMIME charset
\e$B$OJ8;z=89g
\e(B (@ref{Character set})
\e$B$H6hJL$7$F>.J8
\e(B
1177 \e$B;z$G=q$$$F$$$k!K
\e(B
1180 @node MTA, MUA, MIME charset, Glossary
1183 @cindex{Message Transfer Agent}@strong{Message Transfer Agent}
\e$B$NN,$G!"
\e(B
1184 sendmail
\e$B$J$I$N
\e(B mail
\e$BG[Aw
\e(B program
\e$B$H
\e(B news server
\e$B$NAm>N!#
\e(B@refill
1190 @node MUA, MULE, MTA, Glossary
1193 @cindex{Message User Agent}@strong{Message User Agent}
\e$B$NN,$G!"
\e(Bmail
1194 reader
\e$B$H
\e(B news reader
\e$B$NAm>N!#
\e(B@refill
1200 @node MULE, multipart, MUA, Glossary
1203 \e$BH>ED
\e(B
\e$B7u0l;a$i$,:n$C$?!"B?8@8l$5$l$?
\e(B Emacs (@ref{Emacs}).@refill
1205 [MULE] Nishikimi M., Handa K. and Tomura S., ``Mule: MULtilingual
1206 Enhancement to GNU Emacs'', Proc. of INET'93, August, 1993.@refill
1208 \e$B8=:_!"
\e(BMULE
\e$B$N5!G=$r
\e(B Emacs
\e$B$K
\e(B merge
\e$B$9$k:n6H$,9T$o$l$F$*$j!"
\e(Balpha
\e$BHG
\e(B
1209 (ftp://etlport.etl.go.jp/pub/mule/mule-19.33-gamma.taz)
\e$B$,B8:_$9$k!#
\e(B
1211 \e$B$=$NB>!"
\e(BXEmacs
\e$B$K
\e(B merge
\e$B$7$?$b$N$bB8:_$9$k!#
\e(B@refill
1213 \e$B$3$N$?$a!"8=:_$G$OB?8@8l
\e(B Emacs
\e$B$O!"85!9$N
\e(B MULE
\e$B$r4^$a$F#3<oN`$"$k$3$H$K
\e(B
1214 \e$B$J$k!#
\e(B@refill
1216 \e$B$=$3$G!"$3$3$G$O!"B?8@8l
\e(B Emacs
\e$B$NAm>N$r
\e(B @cindex{mule}@strong{mule},
\e$B85!9
\e(B
1217 \e$B$N
\e(B MULE
\e$B$r
\e(B @cindex{MULE}@strong{MULE}, mule
\e$B5!G=$r
\e(B merge
\e$B$7$?
\e(B Emacs
\e$B$r
\e(B
1218 @cindex{Emacs/mule}@strong{Emacs/mule}, mule
\e$B5!G=$r
\e(B merge
\e$B$7$?
\e(B XEmacs
\e$B$r
\e(B
1219 @cindex{XEmacs/mule}@strong{XEmacs/mule}
\e$B$H8F$V$3$H$K$9$k!#
\e(B
1222 @node multipart, multipart/alternative, MULE, Glossary
1223 @subsection Multipart
1225 @cindex{multipart}@strong{multipart} means media type (@ref{media type})
1226 to insert multiple entities (@ref{entities}) in a single body. Or it
1227 also indicates a message consists of multiple entities.@refill
1229 There are following subtypes registered in RFC 2046 (@ref{RFC 2046}):
1233 multipart/mixed (@ref{multipart/mixed})
1235 multipart/alternative (@ref{multipart/alternative})
1237 multipart/digest (@ref{multipart/digest})
1239 multipart/parallel (@ref{multipart/parallel})
1243 and registered in RFC 1847 (@ref{Security multipart}):
1247 multipart/signed (@ref{multipart/signed})
1249 multipart/encrypted (@ref{multipart/encrypted})
1254 @node multipart/alternative, multipart/digest, multipart, Glossary
1255 @subsection multipart/alternative
1257 @cindex{multipart/digest}@strong{multipart/digest} is one of multipart
1258 (@ref{multipart}) media types. This type is syntactically identical to
1259 multipart/mixed (@ref{multipart/mixed}), but the semantics are
1260 different. In particular, each of the body parts is an ``alternative''
1261 version of the same information.@refill
1263 (cf. @ref{RFC 2046})
1267 @node multipart/digest, multipart/encrypted, multipart/alternative, Glossary
1268 @subsection multipart/digest
1270 @cindex{multipart/digest}@strong{multipart/digest} is one of multipart
1271 (@ref{multipart}) media types. This type is syntactically identical to
1272 multipart/mixed (@ref{multipart/mixed}), but the semantics are
1273 different. In particular, in a digest, the default Content-Type value
1274 for a body part is changed from text/plain (@ref{text/plain}) to
1275 message/rfc822 (@ref{message/rfc822}).@refill
1277 This is the replacement of traditional RFC 1153 (@ref{RFC 1153}) based
1278 encapsulation (@ref{encapsulation}).@refill
1280 (cf. @ref{RFC 2046})
1284 @node multipart/encrypted, multipart/mixed, multipart/digest, Glossary
1285 @subsection multipart/encrypted
1287 RFC 1847
\e$B$GDj5A$5$l$?
\e(B Security multipart (@ref{Security multipart})
\e$B$N#1
\e(B
1288 \e$B$D$G!"0E9f2=$5$l$?
\e(B message
\e$B$rI=8=$9$k$N$KMQ$$$k!#
\e(B@refill
1290 (cf. @ref{PGP/MIME})
1294 @node multipart/mixed, multipart/parallel, multipart/encrypted, Glossary
1295 @subsection multipart/mixed
1297 Primary and default subtype of multipart (@ref{multipart}), it is used
1298 when the body parts are independent and need to be bundled in a
1299 particular order.@refill
1301 (cf. @ref{RFC 2046})
1305 @node multipart/parallel, multipart/signed, multipart/mixed, Glossary
1306 @subsection multipart/parallel
1308 @cindex{multipart/parallel}@strong{multipart/parallel} is a subtype of
1309 multipart (@ref{multipart}). This type is syntactically identical to
1310 multipart/mixed (@ref{multipart/mixed}), but the semantics are
1311 different. In particular, in a parallel entity, the order of body parts
1312 is not significant.@refill
1314 (cf. @ref{RFC 2046})
1318 @node multipart/signed, PGP, multipart/parallel, Glossary
1319 @subsection multipart/signed
1321 RFC 1847
\e$B$GDj5A$5$l$?
\e(B Security multipart (@ref{Security multipart})
\e$B$N#1
\e(B
1322 \e$B$D$G!"EE;R=pL>$rI=8=$9$k$N$KMQ$$$k!#
\e(B@refill
1324 (cf. @ref{PGP/MIME})
1328 @node PGP, PGP-kazu, multipart/signed, Glossary
1331 Phil Zimmermann
\e$B;a$,:n@.$7$?8x3+800E9f=hM}7O$N#1$D!#
\e(Bmessage
1332 (@ref{message})
\e$B$N0E9f2=$dEE;R=pL>$r9T$&$3$H$,$G$-$k!#
\e(BPretty Good
1333 Privacy
\e$B$NN,!#
\e(B@refill
1335 \e$BEAE}E*$J
\e(B PGP
\e$B$G$O
\e(B encapsulation (@ref{encapsulation})
\e$B$K
\e(B RFC 934
1336 (@ref{RFC 934})
\e$B$K=`$8$?J}K!$rMQ$$$k!#$3$l$O
\e(B MIME (@ref{MIME})
\e$B$HL7=b$9$k
\e(B
1337 \e$B$N$G
\e(B PGP/MIME (@ref{PGP/MIME})
\e$B$,Ds0F$5$l$F$$$k!#0lJ}!"
\e(BMIME
\e$B$K$*$$$F
\e(B PGP
1338 \e$B$N
\e(Bencapsulation
\e$B$rMQ$$$kJ}K!
\e(B (cf. @ref{PGP-kazu})
1339 \e$B$bMxMQ$5$l$F$-$?!#$7$+$7!":#8e$O
\e(B PGP/MIME
\e$B$KE}0l$7$F$$$/J}$,K>$^$7$$!#
\e(B
1342 @cindex{PGP}@cindex{Informational}@cindex{RFC 1991}
1346 D. Atkins, W. Stallings and P. Zimmermann, ``PGP Message Exchange
1347 Formats'', August 1996, Informational.
1353 @node PGP-kazu, PGP/MIME, PGP, Glossary
1354 @subsection PGP-kazu
1356 \e$B;3K\
\e(B
\e$BOBI'
\e(B
\e$B;a$,Ds0F$7$?
\e(B MIME (@ref{MIME})
\e$B$G
\e(B PGP (@ref{PGP})
\e$B$rMxMQ$9$k$?
\e(B
1357 \e$B$a$NJ}K!$r$3$3$G$O
\e(B @cindex{PGP-kazu}@strong{PGP-kazu}
\e$B$H8F$V$3$H$K$9$k!#
\e(B
1359 PGP-kazu
\e$B$O
\e(B @cindex{application/pgp}@strong{application/pgp}
\e$B$H$$$&
\e(B
1360 content-type (@ref{content-type})
\e$B$rDj5A$9$k!#
\e(B@refill
1362 application/pgp
\e$B$N
\e(B part
\e$B$G$O
\e(B PGP
\e$B$N
\e(B encapsulation (@ref{encapsulation})
1363 \e$B$,MQ$$$i$l$k!#
\e(BPGP
\e$B$N
\e(B encapsulation (cf. @ref{RFC 934})
1364 \e$B$H
\e(B MIME
\e$B$N
\e(B encapsulation
\e$B$OL7=b$9$k$N$G!"
\e(BPGP
\e$B$N
\e(B encapsulation
\e$B$r2r$+$J
\e(B
1365 \e$B$$8B$j!"Cf$K4^$^$l$?
\e(B MIME message
\e$B$rFI$`$3$H$,$G$-$J$/$J$k!#B($A!"
\e(B
1366 PGP-kazu
\e$B$KBP1~$7$F$$$J$$
\e(B MIME
\e$B$KBP1~$7$?
\e(B MUA (@ref{MUA})
\e$B$O$=$N
\e(B part
\e$B$,
\e(B
1367 \e$BFI$a$J$/$J$k!#$=$NBe$o$j!"
\e(BMIME
\e$B$KBP1~$7$F$$$J$$
\e(B PGP
\e$BBP1~$N
\e(B MUA
1368 (@ref{MUA})
\e$B$G$b
\e(B message
\e$B$rFI$`$3$H$,$G$-$k!#
\e(B@refill
1370 PGP-kazu
\e$B$G$O
\e(B MUA
\e$B$O
\e(B PGP
\e$B$N$H
\e(B MIME
\e$B$N$H$$$$D$N
\e(B encapsulation
\e$B$rCN$i$J
\e(B
1371 \e$B$1$l$P$J$i$J$$!#$^$?!"
\e(Bapplication/pgp part
\e$B$r
\e(B parse
\e$B$9$k$?$a$K$O!"$^$:!"
\e(B
1372 pgp
\e$B$N=hM}$r9T$o$J$1$l$P$J$i$J$$$N$G!"
\e(Bparse
\e$B=hM}$,J#;($K$J$k!#
\e(B@refill
1374 \e$B$^$?!"
\e(BInternet
\e$B$G$O:#8e
\e(B PGP/MIME (@ref{PGP/MIME})
\e$B$NJ}8~$GI8=`2=$7$F$$$3
\e(B
1375 \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
1376 \e$B$^$7$$!#
\e(B@refill
1378 [draft-kazu-pgp-mime-00.txt] Yamamoto K., ``PGP MIME Integration'',
1382 @node PGP/MIME, Quoted-Printable, PGP-kazu, Glossary
1383 @subsection PGP/MIME
1385 Michael Elkins
\e$B;a$,Ds0F$7$?
\e(B MIME (@ref{MIME})
\e$B$G
\e(B PGP (@ref{PGP})
\e$B$rMxMQ
\e(B
1386 \e$B$9$k$?$a$NJ}K!!#
\e(B@refill
1388 RFC 1847 (@ref{Security multipart})
\e$B$K4p$-!"
\e(BMIME
\e$B$N
\e(B multipart
\e$B$K$h$k
\e(B
1389 encapsulation (@ref{encapsulation})
\e$B$r9T$&!#$3$N$?$a!"
\e(BMIME
\e$B$N<+A3$J3HD%
\e(B
1390 \e$B$K$J$C$F$$$k!#$7$+$7!"EAE}E*$J
\e(B PGP
\e$B$H$N8_49@-$,<:$o$l$F$$$k!#
\e(B@refill
1392 PGP/MIME
\e$B$G$O
\e(B PGP-kazu (@ref{PGP-kazu})
\e$B$H0[$J$j!"
\e(BMIME
\e$B$N
\e(B encapsulation
1393 \e$B$N$_$rMQ$$$k!#$^$?!"$3$N$?$a!"
\e(BPGP
\e$B$N=hM}$r9T$&A0$K
\e(B message
\e$B$N
\e(B parse
\e$B$r9T
\e(B
1394 \e$B$&$3$H$,$G$-$k!#
\e(B@refill
1396 Internet
\e$B$G$O:#8e
\e(B PGP/MIME (@ref{PGP/MIME})
\e$B$NJ}8~$GI8=`2=$7$F$$$3$&$H$$
\e(B
1397 \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
1398 \e$B$$$k$N$,K>$^$7$$!#
\e(B
1400 @cindex{PGP/MIME}@cindex{Standards Track}@cindex{RFC 2015}
1402 [PGP/MIME: RFC 2015]
1404 M. Elkins, ``MIME Security with Pretty Good Privacy (PGP)'', October
1405 1996, Standards Track.
1410 @node Quoted-Printable, RFC 821, PGP/MIME, Glossary
1411 @subsection Quoted-Printable
1413 @cindex{Quoted-Printable}@strong{Quoted-Printable} is a transfer
1414 encoding method of MIME (@ref{MIME}) defined in RFC 2045 (@ref{RFC
1417 If the data being encoded are mostly US-ASCII text, the encoded form of
1418 the data remains largely recognizable by humans.@refill
1424 @node RFC 821, RFC 822, Quoted-Printable, Glossary
1427 @cindex{SMTP}@strong{SMTP}
\e$B$H8F$P$l$k
\e(B Internet mail
\e$B$NG[AwK!$NI8=`$rDj$a
\e(B
1430 @cindex{SMTP}@cindex{STD 10}@cindex{RFC 821}
1434 J. Postel, ``Simple Mail Transfer Protocol'', August 1982, STD 10.
1439 @node RFC 822, RFC 934, RFC 821, Glossary
1442 Internet mail
\e$B$N<g$K
\e(B @cindex{message header}@strong{message header}
\e$B$K4X$9$k7A<0$K
\e(B
1443 \e$B4X$9$kI8=`$rDj$a$F$$$k
\e(B RFC.
1449 news message
\e$B$b$3$l$K=`$8$F$$$k$N$G!"
\e(B@cindex{Internet
1450 mail}@strong{Internet mail}
\e$B$H=q$/$h$j$b!"
\e(B@cindex{Internet
1451 message}@strong{Internet message}
\e$B$H=q$$$?J}$,NI$$$+$b$7$l$J$$!#
\e(B
1455 @cindex{STD 11}@cindex{RFC 822}
1459 D. Crocker, ``Standard for the Format of ARPA Internet Text Messages'',
1460 August 1982, STD 11.
1465 @node RFC 934, RFC 1036, RFC 822, Glossary
1468 Internet mail (@ref{RFC 822})
\e$B$N
\e(B
1469 @cindex{encapsulation}@strong{encapsulation} (@ref{encapsulation})
\e$B$NJ}
\e(B
1470 \e$BK!$rDj$a$?
\e(B RFC.@refill
1472 MIME (@ref{MIME})
\e$B$HL7=b$9$k$N$G!"8=:_$G$O
\e(B message/rfc822
1473 (@ref{message/rfc822})
\e$B$rMQ$$$k$Y$-$G$"$k!#
\e(B
1480 Marshall T. Rose and Einar A. Stefferud, ``Proposed Standard for Message
1481 Encapsulation'', January 1985.
1486 @node RFC 1036, RFC 1153, RFC 934, Glossary
1487 @subsection RFC 1036
1489 USENET
\e$B$G$N
\e(B message
\e$B$N7A<0$rDj$a$?
\e(B RFC. RFC 822 (@ref{RFC 822})
\e$B$N
\e(B subset
1490 \e$B$K$J$C$F$$$k!#
\e(BInternet
\e$B$NI8=`$G$O$J$$$,!"
\e(BUSENET
\e$B0J30$N
\e(B netnews
\e$B$G$b$3$l
\e(B
1491 \e$B$K=`$8$F$$$k$b$N$,B?$$!#
\e(B
1493 @cindex{USENET}@cindex{RFC 1036}
1497 M. Horton and R. Adams, ``Standard for Interchange of USENET Messages'',
1498 December 1987, (obsolete RFC 850).
1503 @node RFC 1153, RFC 1557, RFC 1036, Glossary
1504 @subsection RFC 1153
1506 \e$BJ#?t$N
\e(B Internet mail (@ref{RFC 822})
\e$B$r
\e(B
1507 @cindex{encapsulation}@strong{encapsulation} (@ref{encapsulation})
\e$B$9$k
\e(B
1508 \e$B$?$a$NJ}K!$rDj$a$?
\e(B RFC. RFC 934 (@ref{RFC 934})
\e$B$rMQ$$$k!#
\e(B@refill
1510 MIME (@ref{MIME})
\e$B$HL7=b$9$k$N$G!"8=:_$G$O
\e(B message/rfc822
1511 (@ref{message/rfc822})
\e$B$rMQ$$$?
\e(B multipart (@ref{multipart})
\e$B$rMQ$$$k$Y$-
\e(B
1512 \e$B$G$"$k!#
\e(B@refill
1514 (cf. @ref{multipart/digest})
1521 F. Wancho, ``Digest Message Format'', April 1990.
1526 @node RFC 1557, RFC 1922, RFC 1153, Glossary
1527 @subsection RFC 1557
1529 euc-kr (@ref{euc-kr})
\e$B$H
\e(B iso-2022-kr (@ref{iso-2022-kr})
\e$B$H$$$&4Z9q8l$N
\e(B
1530 \e$B$?$a$N
\e(B MIME charset (@ref{MIME charset})
\e$B$rDj5A$7$F$$$k
\e(B RFC.
1532 @cindex{Informational}@cindex{RFC 1557}
1536 U. Choi, K. Chon and H. Park, ``Korean Character Encoding for Internet
1537 Messages'', December 1993, Informational.
1542 @node RFC 1922, RFC 2045, RFC 1557, Glossary
1543 @subsection RFC 1922
1545 iso-2022-cn (@ref{iso-2022-cn}), iso-2022-cn-ext
1546 (@ref{iso-2022-cn-ext}), cn-gb (@ref{cn-gb}), cn-big5 (@ref{cn-big5})
\e$B$H
\e(B
1547 \e$B$$$C$?Cf9q8l$N$?$a$N
\e(B MIME charset (@ref{MIME charset})
\e$B$rDj5A$7$F$$$k
\e(B
1550 \e$B$3$l$K2C$($F!"
\e(B@cindex{charset-edition}@strong{charset-edition}
\e$B$H
\e(B
1551 @cindex{charset-extension}@strong{charset-extension}
\e$B$H$$$&
\e(B Content-Type
1552 field (@ref{Content-Type field})
\e$B$N
\e(B parameter
\e$B$rDj5A$7$F$$$k!#
\e(B
1554 @cindex{Informational}@cindex{RFC 1922}
1558 Zhu, HF., Hu, DY., Wang, ZG., Kao, TC., Chang, WCH. and Crispin, M.,
1559 ``Chinese Character Encoding for Internet Messages'', March 1996,
1565 @node RFC 2045, RFC 2046, RFC 1922, Glossary
1566 @subsection RFC 2045
1568 @cindex{Standards Track}@cindex{RFC 2045}
1572 N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
1573 (MIME) Part One: Format of Internet Message Bodies'', November 1996,
1574 Standards Track (obsolete RFC 1521, 1522, 1590).
1579 @node RFC 2046, RFC 2048, RFC 2045, Glossary
1580 @subsection RFC 2046
1582 @cindex{Standards Track}@cindex{RFC 2046}
1586 N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
1587 (MIME) Part Two: Media Types'', November 1996, Standards Track (obsolete
1588 RFC 1521, 1522, 1590).
1593 @node RFC 2048, RFC 2049, RFC 2046, Glossary
1594 @subsection RFC 2048
1596 @cindex{Standards Track}@cindex{RFC 2048}
1600 N. Freed, J. Klensin and J. Postel, ``Multipurpose Internet Mail
1601 Extensions (MIME) Part Four: Registration Procedures'', November 1996,
1602 Standards Track (obsolete RFC 1521, 1522, 1590).
1607 @node RFC 2049, plain text, RFC 2048, Glossary
1608 @subsection RFC 2049
1610 @cindex{Standards Track}@cindex{RFC 2049}
1614 N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
1615 (MIME) Part Five: Conformance Criteria and Examples'', November 1996,
1616 Standards Track (obsolete RFC 1521, 1522, 1590).
1621 @node plain text, Security multipart, RFC 2049, Glossary
1622 @subsection plain text
1624 \e$B=qBN$dAHHG$K4X$9$k>pJs$r;}$?$J$$
\e(B
\e$BJ8;zId9f
\e(B(@ref{Coded character set})
\e$B$N$_
\e(B
1625 \e$B$GI=8=$5$l$k
\e(B text
\e$B>pJs!#
\e(B(cf. @ref{text/plain})
1629 @node Security multipart, text/enriched, plain text, Glossary
1630 @subsection Security multipart
1632 MIME (@ref{MIME})
\e$B$G0E9f$dEE;R=qL>$rMQ$$$k$?$a$N7A<0!#
\e(B
1633 @cindex{multipart/signed}@strong{multipart/signed}
1634 (@ref{multipart/signed})
\e$B$H
\e(B
1635 @cindex{multipart/encrypted}@strong{multipart/encrypted}
1636 (@ref{multipart/encrypted})
\e$B$H$$$&
\e(B multipart
\e$B$rMQ$$$k!#
\e(BMOSS
\e$B$d
\e(B PGP/MIME
1637 (@ref{PGP/MIME})
\e$B$O$3$l$K4p$$$F$$$k!#
\e(B
1639 @cindex{Security multipart}@cindex{Standards Track}@cindex{RFC 1847}
1641 [Security multipart: RFC 1847]
1643 James Galvin, Gale Murphy, Steve Crocker and Ned Freed, ``Security
1644 Multiparts for MIME: Multipart/Signed and Multipart/Encrypted'', October
1645 1995, Standards Track.
1650 @node text/enriched, text/plain, Security multipart, Glossary
1651 @subsection text/enriched
1653 RFC 1521
\e$B$GDj5A$5$l$?
\e(B @cindex{text/richtext}@strong{text/richtext}
\e$B$KBe
\e(B
1654 \e$B$o$C$F!"=qBN$dAHHG$K4X$9$k>pJs$r;}$C$?
\e(B text
\e$B$rI=8=$9$k$?$a$N
\e(B media type
1657 @cindex{text/enriched}@cindex{RFC 1896}
1659 [text/enriched: RFC 1896]
1661 P. Resnick and A. Walker, ``The text/enriched MIME Content-type'',
1662 February 1996, (obsolete RFC 1563).
1667 @node text/plain, tm-kernel, text/enriched, Glossary
1668 @subsection text/plain
1670 @cindex{text/plain}@strong{text/plain} is a media type (@ref{media
1671 type}) for plain text (@ref{plain text}), defined in RFC 2046 (@ref{RFC
1674 The default media type of ``text/plain; charset=us-ascii'' for Internet
1675 mail describes existing Internet practice. That is, it is the type of
1676 body defined by RFC 822 (@ref{RFC 822}).@refill
1678 (cf. @ref{MIME charset}) (cf. @ref{us-ascii})
1682 @node tm-kernel, tm-MUA, text/plain, Glossary
1683 @subsection tm-kernel, tm
1685 Emacs
\e$B$G
\e(B MIME (@ref{MIME})
\e$B$rMxMQ$9$k$?$a$N
\e(B user interface
\e$B$rDs6!$9$k
\e(B
1686 library
\e$B72!#
\e(B`tools for MIME'
\e$B$NN,!#
\e(B
1689 @strong{[
\e$B$I$&$G$bNI$$$3$H
\e(B(^-^;]}
1694 tm
\e$B$O
\e(B ``tiny-mime''
\e$B$NN,$8$c$J$$$i$7$$$>
\e(B (^-^;
1697 tm
\e$B$O:n<T$N%$%K%7%c%k$8$c$J$$$i$7$$$>
\e(B (^-^;
1700 ``Tools for MIME''
\e$B$NN,$H$$$&$N$O$3$8$D$1$i$7$$$>
\e(B (^-^;
1706 @node tm-MUA, us-ascii, tm-kernel, Glossary
1709 tm (@ref{tm-kernel})
\e$B$rMQ$$$?
\e(B MUA (@ref{MUA})
\e$B$b$7$/$O
\e(B MUA
\e$B$KBP$9$k
\e(B
1712 @cindex{tm
\e$BBg@9$j
\e(B package}@strong{tm
\e$BBg@9$j
\e(B package}
\e$B$K$O
\e(B
1716 mh-e (@ref{(mh-e)})
\e$BMQ$N
\e(B @cindex{tm-mh-e}@strong{tm-mh-e}
1718 GNUS
\e$BMQ$N
\e(B @cindex{tm-gnus}@strong{tm-gnus}
1720 Gnus
\e$BMQ$N
\e(B @cindex{gnus-mime}@strong{gnus-mime} (@ref{(gnus-mime-en)})
1722 VM
\e$BMQ$N
\e(B @cindex{tm-vm}@strong{tm-vm}
1724 RMAIL
\e$BMQ$N
\e(B @cindex{tm-rmail}@strong{tm-rmail}
1728 \e$B$,4^$^$l$F$$$k!#
\e(B
1730 \e$BFHN)$7$?
\e(B MUA
\e$B$H$7$F$O
\e(B cmail (@ref{(cmail)})
\e$B$,
\e(B tm
\e$B$rMxMQ2DG=$G$"$k!#
\e(B
1733 @node us-ascii, , tm-MUA, Glossary
1734 @subsection us-ascii
1736 \e$B%"%a%j%+O"K.$J$I$G;H$o$l$k1Q8l$J$I$rI=8=$9$k$?$a$N
\e(B MIME charset
1737 (@ref{MIME charset})
\e$B$N#1$D!#
\e(B@refill
1739 ASCII (@ref{ASCII})
\e$B$N$_$+$i$J$j
\e(B ISO 2022 (@ref{ISO 2022})
\e$B$K$h$kId9f3H
\e(B
1740 \e$BD%
\e(B (@ref{Code extension})
\e$B$O5v$5$l$J$$!#
\e(B@refill
1742 Internet mail
\e$B$K$*$1$kI8=`$NId9f2=J8;z=89g
\e(B(@ref{Coded character set})
\e$B$G
\e(B
1743 \e$B$"$j!"L@<(E*$K
\e(B MIME charset
\e$B$,<($5$l$J$$>l9g$O86B'$H$7$F
\e(B
1744 @cindex{us-ascii}@strong{us-ascii}
\e$B$,;H$o$l$k!#
\e(B@refill
1746 \e$B$^$?!"
\e(BRFC 822 (@ref{RFC 822})
\e$B$K$*$1$k
\e(B @cindex{ASCII}@strong{ASCII}
\e$B$O
\e(B
1747 us-ascii
\e$B$r;X$9$b$N$H2r<a$9$Y$-$G$"$k!#
\e(B
1750 @node Setting, Bug report, Introduction, Top
1753 In the tm package, two files, @file{mime-setup.el} and
1754 @file{tm-setup.el}, are provided to ease the setup.@refill
1756 The @file{mime-setup.el} is used for the whole MIME related
1757 setup including MIME encoding using @file{tm-edit.el}, while
1758 @file{tm-setup.el} is used to set up tm-MUA only.
1762 * mime-setup:: Normal setting
1763 * tm-setup:: Setting not to use tm-edit
1764 * setting for VM:: Setting for VM
1765 * manual setting:: Setting up without loading provided setup files
1768 @node mime-setup, tm-setup, Setting, Setting
1769 @section Normal setting
1771 If you want normal setting, please use @cindex{mime-setup}@strong{mime-setup}.
1772 For example, please insert following into @file{~/.emacs}:
1779 As @file{mime-setup.el} loads @file{tm-setup.el}, you
1780 don't need to load @file{tm-setup.el} when you use
1781 @file{mime-setup.el} (Description of old version of Gnus FAQ is
1787 * Notice about GNUS:: Notices for GNUS
1790 @node signature, Notice about GNUS, mime-setup, mime-setup
1791 @subsection signature
1793 You can set up the @cindex{automatic signature selection
1794 tool}@strong{automatic signature selection
1795 tool} using @file{mime-setup}. If you want to
1796 automatically select the signature file depending on how the message
1797 headers show, add lines like shown below to your .emacs (Refer to the
1798 reference manual of @file{signature.el} for more details).
1801 (setq signature-file-alist
1802 '((("Newsgroups" . "jokes") . "~/.signature-jokes")
1803 (("Newsgroups" . ("zxr" "nzr")) . "~/.signature-sun")
1804 (("To" . ("ishimaru" "z-suzuki")) . "~/.signature-sun")
1805 (("To" . "tea") . "~/.signature-jokes")
1806 (("To" . ("sim" "oku" "takuo")) . "~/.signature-formal")
1812 @defvar mime-setup-use-signature
1814 If it is not @code{nil}, @file{mime-setup.el} sets up for
1815 @file{signature.el}. Its default value is @code{t}.
1820 @defvar mime-setup-signature-key-alist
1822 It defines key to bind signature inserting command for each
1823 major-mode. Its default value is following:
1826 ((mail-mode . "\C-c\C-w"))
1830 If you want to change, please rewrite it. For example:
1833 (set-alist 'mime-setup-signature-key-alist
1834 'news-reply-mode "\C-c\C-w")
1841 @defvar mime-setup-default-signature-key
1843 If key to bind signature inserting command for a major-mode is not found
1844 from @code{mime-setup-signature-key-alist}, its value is used as key.
1845 Its default value is @code{"\C-c\C-s"}.
1850 @node Notice about GNUS, , signature, mime-setup
1851 @subsection Notices for GNUS
1853 When @file{mime-setup.el} sets up for @file{signature.el}, it sets
1854 variable @code{gnus-signature-file} to @code{nil}. Therefore GNUS does
1855 not insert signature automatically when it is sending a message. Reason
1856 of this setting is following:@refill
1858 GNUS inserts signature after @file{tm-edit.el} composed as MIME message.
1859 Therefore signature inserted by GNUS is not processed as a valid MIME
1860 part. In particular, for multipart message, signature places in outside
1861 of MIME part. So MIME MUA might not display it.@refill
1863 Other notice is key bind. In historical reason, key bind to insert
1864 signature is @kbd{C-c C-s} (like mh-e (@ref{(mh-e)})) instead of
1865 @kbd{C-c C-w}. If you change to GNUS's default, please set following:
1868 (set-alist 'mime-setup-signature-key-alist 'news-reply-mode "\C-c\C-w")
1873 @node tm-setup, setting for VM, mime-setup, Setting
1874 @section Setting not to use tm-edit
1876 @cindex{tm-setup}@strong{tm-setup} only sets up tm-MUA (@ref{tm-MUA})s.
1877 In other words, it is a setting to avoid to use tm-edit. If you don't
1878 want to compose MIME message or want to use other MIME composer, please
1879 use it instead of @file{mime-setup.el}.@refill
1881 For example, please insert following into @file{~/.emacs}:
1893 If you use @file{mime-setup.el}, you you don't need to load
1899 @node setting for VM, manual setting, tm-setup, Setting
1900 @section Setting for VM
1902 If you use @cindex{vm}@strong{vm}, please insert following in
1915 If you use @cindex{BBDB}@strong{BBDB}, please insert @code{(require
1916 'tm-vm)} @strong{after} @code{(bbdb-insinuate-vm)}.
1921 @node manual setting, , setting for VM, Setting
1922 @section Setting up without loading provided setup files
1924 You may find the valuable hints in @file{mime-setup.el} or
1925 @file{tm-setup.el} if you want to set up MIME environment
1926 without loading the tm-provided setup files.
1932 Current tm provides some convenient features to expect tm-edit, and
1933 they can not use if @file{mime-setup.el} is not used. If you
1934 want to set up original setting to use tm-edit, please declare
1938 (provide 'mime-setup)
1945 @node Bug report, Concept Index, Setting, Top
1946 @chapter How to report bug and about mailing list of tm
1948 If you write bug-reports and/or suggestions for improvement, please
1949 send them to the tm Mailing List:
1953 Japanese <bug-tm-ja@@chamonix.jaist.ac.jp>
1955 English <bug-tm-en@@chamonix.jaist.ac.jp>
1959 Notice that, we does not welcome bug reports about too old version.
1960 Bugs in old version might be fixed. So please try latest version at
1963 You should write @cindex{good bug report}@strong{good bug report}. If
1964 you write only ``tm does not work'', we can not find such situations.
1965 At least, you should write name, type, variants and version of OS,
1966 emacs, tm and MUA, and setting. In addition, if error occurs, to send
1967 backtrace is very important. (cf. @ref{(emacs)Bugs}) @refill
1969 Bug may not appear only your environment, but also in a lot of
1970 environment (otherwise it might not bug). Therefor if you send mail to
1971 author directly, we must write a lot of mails. So please send mail to
1972 address for tm bugs instead of author.@refill
1974 Via the tm ML, you can report tm bugs, obtain the latest release of
1975 tm, and discuss future enhancements to tm. To join the tm ML, send
1980 Japanese <tm-ja-admin@@chamonix.jaist.ac.jp>
1982 English <tm-en-admin@@chamonix.jaist.ac.jp>
1986 Since the user registration is done manually, please write the mail
1987 body in human-recognizable language (^_^).
1990 @node Concept Index, Variable Index, Bug report, Top
1991 @chapter Concept Index
1995 @node Variable Index, , Concept Index, Top
1996 @chapter Variable Index