\input texinfo.tex
@setfilename tm-en.info
@settitle{tm 7.90 Manual (English Version)}
@titlepage
@title tm 7.90 Manual (English Version)
@author MORIOKA Tomohiko <morioka@@jaist.ac.jp>
@subtitle 1996/10/15
@end titlepage
@node Top, Introduction, (dir), (dir)
@top tm 7.90 Manual (English Version)

@ifinfo

This file documents tm, a MIME package for GNU Emacs.
@end ifinfo

@menu
* Introduction::                What is tm?
* Setting::                     
* Bug report::                  How to report bug and about mailing list of tm
* Concept Index::               
* Variable Index::              
@end menu

@node Introduction, Setting, Top, Top
@chapter What is tm?

The tm package is a set of modules to enjoy MIME on GNU Emacs.  Using
tm, you can

@itemize @bullet
@item
 playback or view the MIME messages using tm-view
@item
 compose MIME message using tm-edit
@item
 use the enhanced MIME features with mh-e, GNUS, Gnus, RMAIL and VM
@end itemize

@noindent
and more.

Please read following about each topics:

@itemize @bullet
@item
tm-MUA for Gnus (@ref{(gnus-mime-en)})
@item
tm-MUA for GNUS (@ref{(tm-gnus-en)})
@item
tm-MUA for mh-e (@ref{(tm-mh-e-en)})
@item
mime/viewer-mode (@ref{(tm-view-en)})
@item
mime/editor-mode (@ref{(tm-edit-en)})
@end itemize



@menu
* Glossary::                    
@end menu

@node Glossary,  , Introduction, Introduction
@section Glossary


@menu
* 7bit::                        
* 8bit::                        
* 94-character set::            
* 96-character set::            
* 94x94-character set::         
* ASCII::                       
* Base64::                      
* binary::                      
* graphic character set::       Graphic Character Set
* cn-gb::                       cn-gb, gb2312
* cn-big5::                     cn-big5, big5
* CNS::                         CNS 11643-1992
* coded character set::         Coded character set, Character code
* code extension::              Code extension
* Content-Disposition::         Content-Disposition field
* media type::                  
* Content-Type field::          
* Emacs::                       
* encoded-word::                
* encapsulation::               
* euc-kr::                      
* FTP::                         FTP 
* GB 2312::                     GB 2312-1980
* GB 8565.2::                   GB 8565.2-1988
* hz-gb2312::                   
* ISO 2022::                    
* iso-2022-cn::                 
* iso-2022-cn-ext::             
* iso-2022-jp::                 
* iso-2022-jp-2::               
* iso-2022-kr::                 
* ISO 646::                     
* ISO 8859-1::                  
* iso-8859-1::                  
* ISO 8859-2::                  
* iso-8859-2::                  
* ISO 8859-3::                  
* ISO 8859-4::                  
* ISO 8859-5::                  
* iso-8859-5::                  
* ISO 8859-6::                  
* ISO 8859-7::                  
* iso-8859-7::                  
* ISO 8859-8::                  
* ISO 8859-9::                  
* ISO-IR-165::                  ISO-IR-165, CCITT Extended GB 
* JIS X0201::                   
* JIS C6226::                   JIS C6226-1978
* JIS X0208::                   
* JIS X0212::                   JIS X0212-1990
* koi8-r::                      
* KS C5601::                    KS C5601-1987
* message::                     
* message/rfc822::              
* method::                      
* MIME::                        
* MIME charset::                
* MTA::                         
* MUA::                         
* MULE::                        
* multipart::                   Multipart
* multipart/alternative::       
* multipart/digest::            
* multipart/encrypted::         
* multipart/mixed::             
* multipart/parallel::          
* multipart/signed::            
* PGP::                         
* PGP-kazu::                    
* PGP/MIME::                    
* Quoted-Printable::            
* RFC 821::                     
* RFC 822::                     
* RFC 934::                     
* RFC 1036::                    
* RFC 1153::                    
* RFC 1557::                    
* RFC 1922::                    
* RFC 2045::                    
* RFC 2046::                    
* RFC 2048::                    
* RFC 2049::                    
* plain text::                  
* Security multipart::          
* text/enriched::               
* text/plain::                  
* tm-kernel::                   tm-kernel, tm
* tm-MUA::                      
* us-ascii::                    
@end menu

@node 7bit, 8bit, Glossary, Glossary
@subsection 7bit

@cindex{7bit}@strong{7bit} means any integer between 0 .. 127.@refill

Any data represented by 7bit integers is called @cindex{7bit
data}@strong{7bit data}.@refill

Textual string consisted of Control characters between 0 .. 31 and 127,
and space represented by 32, and graphic characters between 33 .. 236
are called @cindex{7bit (textual) string}@strong{7bit (textual)
string}.@refill

Traditional Internet MTA (@ref{MTA}) can translate 7bit data, so it is
no need to translate by Quoted-Printable (@ref{Quoted-Printable}) or
Base64 (@ref{Base64}) for 7bit data.@refill

However if there are too long lines, it can not translate by 7bit MTA
even if it is 7bit data.  RFC 821 (@ref{RFC 821}) and RFC 2045 (@ref{RFC
2045}) require lines in 7bit data must be less than 998 bytes.  So if a
``7bit data'' has a line more than 999 bytes, it is regarded as binary
(@ref{binary}).  For example, Postscript file should be encoded by
Quoted-Printable.


@node 8bit, 94-character set, 7bit, Glossary
@subsection 8bit

@cindex{8bit}@strong{8bit} means any integer between 0 .. 255.@refill

Any data represented by 8bit integers is called @cindex{8bit
data}@strong{8bit data}.@refill

Textual string consisted of Control characters between 0 .. 31, 127, and
128 .. 159, and space represented by 32, and graphic characters between
33 .. 236 and 160 .. 255 are called @cindex{8bit (textual)
string}@strong{8bit (textual) string}.@refill

For example, iso-8859-1 (@ref{iso-8859-1}) or euc-kr (@ref{euc-kr}) are
coded-character-set represented by 8bit textual string.@refill

Traditional Internet MTA (@ref{MTA}) can translate only 7bit
(@ref{7bit}) data, so if a 8bit data will be translated such MTA, it
must be encoded by Quoted-Printable (@ref{Quoted-Printable}) or Base64
(@ref{Base64}).@refill

However 8bit MTA are increasing today.@refill

However if there are too long lines, it can not translate by 8bit MTA
even if it is 8bit data.  RFC 2045 (@ref{RFC 2045}) require lines in
8bit data must be less than 998 bytes.  So if a ``8bit data'' has a line
more than 999 bytes, it is regarded as binary (@ref{binary}), so it must
be encoded by Base64 or Quoted-Printable.


@node 94-character set, 96-character set, 8bit, Glossary
@subsection 94-character set

@cindex{94-character set}@strong{94-character set} is a kind of 1 byte
graphic character set (@ref{graphic character set}), each characters are
in positions 02/01 (33) to 07/14 (126) or 10/01 (161) to 15/14 (254).
(ex. ASCII (@ref{ASCII}), JIS X0201-Latin)


@node 96-character set, 94x94-character set, 94-character set, Glossary
@subsection 96-character set

@cindex{96-character set}@strong{96-character set} is a kind of 1 byte
graphic character set (@ref{graphic character set}), each characters are
in positions 02/00 (32) to 07/15 (126) or 10/00 (160) to 15/15
(255). (ex. ISO 8859)


@node 94x94-character set, ASCII, 96-character set, Glossary
@subsection 94x94-character set

@cindex{94x94-character set}@strong{94x94-character set} is a kind of 2
byte graphic character set (@ref{graphic character set}), each bytes are
in positions 02/01 (33) to 07/14 (126) or 10/01 (161) to 15/14 (254).
(ex. JIS X0208 (@ref{JIS X0208}), GB 2312 (@ref{GB 2312}))


@node ASCII, Base64, 94x94-character set, Glossary
@subsection ASCII

$B%"%a%j%+O"K.$G;H$o$l$kJ8;z$rId9f2=$7$?(B 94-character set
(@ref{94-character set}).  A-Z, a-z $B$N(B Latin $BJ8;z$H?t;z!"4v$D$+$N5-9f$+(B
$B$i$J$k!#(BISO 646 (@ref{ISO 646}) $B$N0l$D!#(B

@cindex{ASCII}@cindex{ANSI X3.4:1986}
@noindent
[ASCII]
@quotation
``Coded Character Set -- 7-Bit American Standard Code for Information
Interchange'', ANSI X3.4:1986.
@end quotation



@node Base64, binary, ASCII, Glossary
@subsection Base64

@cindex{Base64}@strong{Base64} is a transfer encoding method of MIME
(@ref{MIME}) defined in RFC 2045 (@ref{RFC 2045}).@refill

The encoding process represents 24-bit groups of input bits as output
strings of 4 encoded characters.  Encoded characters represent integer 0
.. 63 or @cindex{pad}@strong{pad}.  Base64 data must be 4 * n bytes, so
pad is used to adjust size.@refill

These 65 characters are subset of all versions of ISO 646, including
US-ASCII, and all versions of EBCDIC.  So it is safe even if it is
translated by non-Internet gateways.


@node binary, graphic character set, Base64, Glossary
@subsection binary

$BG$0U$N(B byte $BNs$r(B @cindex{binary}@strong{binary} $B$H8F$V$3$H$K$7$^$9!#(B
@refill

8bit (@ref{8bit}) $B$H0[$J$k$N$O(B data $B$K9T$N9=B$$r2>Dj$7$J$$$3$H$G$9!#(B

$B$^$?!"9T$N9=B$$,$"$C$F$b!"(B999 byte $B0J>e$+$i$J$k9T$,$"$k>l9g$b(B binary$B$H8F(B
$B$V$3$H$K$7$^$9!#(B@refill

$B$A$J$_$K!"(B7bit (@ref{7bit}) $B$d(B 8bit $B$GI=8=$G$-$k(B data $B$O(B binary $B$G$bI=8=(B
$B$G$-$^$9!#$h$C$F!"(B@cindex{binary data}@strong{binary data} $B$H8@$C$?>l9g!"(B
$BG$0U$N(B data $B$r;X$9$3$H$,$"$j$^$9!#(B


@node graphic character set, cn-gb, binary, Glossary
@subsection Graphic Character Set

Coded character set (@ref{Coded character set}) for graphic characters.


@node cn-gb, cn-big5, graphic character set, Glossary
@subsection cn-gb, gb2312

$BCf9qBgN&$G$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N(B MIME
charset (@ref{MIME charset}) $B$N#1$D!#(B@refill

ISO 2022 (@ref{ISO 2022}) $B$K4p$$$F(B ASCII (@ref{ASCII}) $B$K(B GB 2312
(@ref{GB 2312}) $B$r(B 8bit (@ref{8bit}) $B$GId9f3HD%(B (@ref{Code extension})$B$7(B
$B$F$$$k!#(B@refill

RFC 1922 (@ref{RFC 1922}) $B$GDj5A$5$l$F$$$k!#(B


@node cn-big5, CNS, cn-gb, Glossary
@subsection cn-big5, big5

$BBfOQ$d9a9A$GMQ$$$i$l$F$$$k<g$KHKBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N(B 
MIME charset (@ref{MIME charset}) $B$N#1$D!#(B@refill

ISO 2022 (@ref{ISO 2022}) $B$K4p$+$J$$(B 8bit (@ref{8bit}) $B$N(Bcoded character
set (@ref{coded character set})$B$G(B de-fact standard $B$G$"$k!#(BRFC 1922
(@ref{RFC 1922}) $B$GDj5A$5$l$F$$$k!#(B@refill

cf. @cindex{BIG5}
@noindent
[BIG5]
@quotation
Institute for Information Industry, ``Chinese Coded Character Set in
Computer'', March 1984.
@end quotation

CNS 11643-1986 (@ref{CNS}) $B$HBP1~4X78$,$"$k!#(B


@node CNS, coded character set, cn-big5, Glossary
@subsection CNS 11643-1992

$BBfOQ$d9a9A$GMQ$$$i$l$F$$$k<g$KHKBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N(B 
$BJ8;z=89g(B(@ref{Character set})$B!#BfOQ$NI8=`!#8=:_!"(B94$B!_(B94 (@ref{94x94
character set}) $B$NLL$,Bh#1LL$+$iBh#7LL$^$G$"$k!#(B@refill

ISO 2022 (@ref{ISO 2022}) $B$G$N=*C<J8;z$O!"Bh#1LL$,(B `G', $BBh#2LL$,(B `H', $BBh(B
$B#3LL$,(B `I', $BBh#4LL$,(B `J', $BBh#5LL$,(B `K', $BBh#6LL$,(B `L', $BBh#7LL$,(B `M' $B$G$"(B
$B$k!#(B

@cindex{CNS 11643-1992}@cindex{CNS        11643:1992}
@noindent
[CNS 11643-1992]
@quotation
``Standard Interchange Code for Generally-Used Chinese Characters'', CNS
11643:1992.
@end quotation



@node coded character set, code extension, CNS, Glossary
@subsection Coded character set, Character code

A set of unambiguous rules that establishes a character set and the
one-to-one relationship between the characters of the set and their
bit combinations.


@node code extension, Content-Disposition, coded character set, Glossary
@subsection Code extension

The techniques for the encoding of characters that are not included in
the character set of a given code. (ex. ISO 2022 (@ref{ISO 2022}))


@node Content-Disposition, media type, code extension, Glossary
@subsection Content-Disposition field

Content $B$NI=<($N;EJ}$d(B file $BL>$rI=8=$9$k$?$a$N(B field. MIME (@ref{MIME}) 
$B$N3HD%$N#1$D!#(B@refill

@cindex{Experimental}@cindex{RFC 1806}
@noindent
[RFC 1806]
@quotation
E R. Troost and S. Dorner, ``Communicating Presentation Information in
Internet Messages: The Content-Disposition Header'', June 1995,
Experimental.
@end quotation



@node media type, Content-Type field, Content-Disposition, Glossary
@subsection media type

@cindex{media type}@strong{media type} specifies the nature of the data
in the body of MIME (@ref{MIME}) entity (@ref{entity}).  It consists of
@cindex{type}@strong{type} and @cindex{subtype}@strong{subtype}.  It is
defined in RFC 2046 (@ref{RFC 2046}).@refill

Currently there are following types:

@itemize @bullet
@item
@cindex{text}@strong{text}
@item
@cindex{image}@strong{image}
@item
@cindex{audio}@strong{audio}
@item
@cindex{video}@strong{video}
@item
@cindex{application}@strong{application}
@item
@cindex{multipart}@strong{multipart} (@ref{multipart})
@item
@cindex{message}@strong{message}
@end itemize


And there are various subtypes, for example, application/octet-stream,
audio/basic, image/jpeg, multipart/mixed (@ref{multipart/mixed}),
text/plain (@ref{text/plain}), video/mpeg...@refill

You can refer registered media types at MEDIA TYPES
(ftp://ftp.isi.edu/in-notes/iana/assignments/media-types).@refill

In addition, you can use private type or subtype using
@cindex{x-token}@strong{x-token}, which as the prefix `x-'.  However you
can not use them in public.@refill

(cf. @ref{Content-Type field})



@node Content-Type field, Emacs, media type, Glossary
@subsection Content-Type field

Header field to represent information about body, such as media type
(@ref{media type}), MIME charset (@ref{MIME charset}).  It is defined in
RFC 2045 (@ref{RFC 2045}).

@noindent
@strong{[Memo]}
@quotation

Historically, Content-Type field was proposed in RFC 1049.  In it,
Content-Type did not distinguish type and subtype.  However MIME parser
may be able to accept RFC 1049 based Content-Type as unknown type.
@end quotation


Content-Type field is defined as following:

@quotation
``Content-Type'' ``:'' @cindex{type}@strong{type} ``/''
@cindex{subtype}@strong{subtype} *( ``;'' @cindex{parameter}@strong{parameter} )
@end quotation


For example:

@quotation
@example
Content-Type: image/jpeg
@end example
@end quotation


@quotation
@example
Content-Type: text/plain; charset=iso-2022-jp
@end example
@end quotation


@noindent
@strong{[Memo]}
@quotation

A part does not have content-type field is regarded as

@quotation
@example
Content-Type: text/plain; charset=us-ascii
@end example
@end quotation

@noindent
(cf. @ref{us-ascii})


And a part has unknown type/subtype is regarded as

@quotation
@example
Content-Type: application/octet-stream
@end example
@end quotation

@end quotation



@node Emacs, encoded-word, Content-Type field, Glossary
@subsection Emacs

$B$3$3$G$O(B `Emacs' $B$G(B FSF $B$,G[I[$7$F$$$k(B GNU Emacs $B$r;X$7!"(B`emacs' $B$G(B
GNU Emacs $B$NJQ<o$NAm>N$H$9$k!#(B


@node encoded-word, encapsulation, Emacs, Glossary
@subsection encoded-word

Representation non ASCII (@ref{ASCII}) characters in header.  It is
defined in @cindex{RFC 2047}@strong{RFC 2047}.@refill

@cindex{Standards Track}@cindex{RFC 2047}
@noindent
[RFC 2047]
@quotation
K. Moore, ``MIME (Multipurpose Internet Mail Extensions) Part Three:
Message Header Extensions for Non-ASCII Text'', November 1996, Standards
Track (obsolete RFC 1521,1522,1590).
@end quotation



@node encapsulation, euc-kr, encoded-word, Glossary
@subsection encapsulation

Internet mail (@ref{RFC 822}) $B$rB>$N5-;v$K$^$k$4$HF~$l$kJ}K!!#(B@refill

$BNc$($P!"5-;v$rE>Aw$7$?$j$9$k$N$KMQ$$$k!#(B@refill

(cf. @ref{message/rfc822})



@node euc-kr, FTP, encapsulation, Glossary
@subsection euc-kr

$B4Z9q8l$rI=8=$9$k$?$a$N(B MIME charset (@ref{MIME charset}) $B$N#1$D!#(B

ISO 2022 (@ref{ISO 2022}) $B$K4p$$$F(B ASCII (@ref{ASCII}) $B$K(BKS C5601
(@ref{KS C5601}) $B$r(B 8bit (@ref{8bit}) $B$GId9f3HD%(B (@ref{Code extension})
$B$7$F$$$k!#(B@refill

RFC 1557 (@ref{RFC 1557}) $B$GDj5A$5$l$F$$$k!#(B@refill

cf. @cindex{euc-kr}@cindex{KS C 5861:1992}
@noindent
[euc-kr]
@quotation
Korea Industrial Standards Association, ``Hangul Unix Environment'', KS
C 5861:1992.
@end quotation



@node FTP, GB 2312, euc-kr, Glossary
@subsection FTP 

Internet $B$G(B file $B$rE>Aw$9$k$?$a$N(B protocol $B$N#1$D!#(BRFC 959 $B$GDj5A$5$l$F(B
$B$$$k!#(B@refill

@cindex{FTP}@cindex{STD 9}@cindex{RFC 959}
@noindent
[FTP: RFC 959]
@quotation
Postel, J. and J. Reynolds, ``File Transfer Protocol'', October 1985,
STD 9.
@end quotation



@node GB 2312, GB 8565.2, FTP, Glossary
@subsection GB 2312-1980

$BCf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=$9$?$a$N(B 
94x94-character set (@ref{94x94-character set})$B!#Cf9q$N9q2HI8=`!#(BISO
2022 (@ref{ISO 2022}) $B$G$N=*C<J8;z$O(B `A'.@refill

$B$3$l$O(B GB $B$K$*$1$k4pK\=8$G$"$k!#(B

@cindex{GB 2312}@cindex{GB 2312:1980}
@noindent
[GB 2312]
@quotation
$B!X?.B)8r49MQ4A;zJTb{;zId=8(B -- $B4pK\=8!Y(B, ``Code of Chinese Graphic
Character Set for Information Interchange - Primary Set'', GB 2312:1980.
@end quotation



@node GB 8565.2, hz-gb2312, GB 2312, Glossary
@subsection GB 8565.2-1988

$BCf9q8l$N$?$a$NJd=uJ8;z=89g(B(@ref{Character set})$B!#Cf9q$N9q2HI8=`!#(BGB 2312
(@ref{GB 2312}) $B$N6u$-ItJ,$KJd=<$9$k$h$&$KDj5A$5$l$?$i$7$$!#(B

@cindex{GB 8565.2}@cindex{GB 8565.2:1988}
@noindent
[GB 8565.2]
@quotation
``Information Processing - Coded Character Sets for Text Communication -
Part 2: Graphic Characters used with Primary Set'', GB 8565.2:1988.
@end quotation



@node hz-gb2312, ISO 2022, GB 8565.2, Glossary
@subsection hz-gb2312

$BCf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N(B MIME
charset (@ref{MIME charset}) $B$N#1$D!#(B@refill

ASCII (@ref{ASCII}) $B$K(B GB 2312 (@ref{GB 2312}) $B$r(B 7bit $B$GId9f3HD%(B
(@ref{Code extension})$B$7$?$b$N$r(B ASCII printable $B$K$J$k$h$&$K9)IW$7$F$$(B
$B$k!#(B@refill

RFC 1842, 1843 $B$GDj5A$5$l$F$$$k!#(B

@cindex{Informational}@cindex{RFC 1842}
@noindent
[RFC 1842]
@quotation
Y. Wei, Y. Zhang, J. Li, J. Ding and Y. Jiang, ``ASCII Printable
Characters-Based Chinese Character Encoding for Internet Messages'',
August 1995, Informational.
@end quotation

@cindex{Informational}@cindex{RFC 1843}
@noindent
[RFC 1843]
@quotation
F. Lee, ``HZ - A Data Format for Exchanging Files of Arbitrarily Mixed
Chinese and ASCII characters'', August 1995, Informational.
@end quotation



@node ISO 2022, iso-2022-cn, hz-gb2312, Glossary
@subsection ISO 2022

$BId9f3HD%(B(@ref{Code extension})$B$N$?$a$N9q:]I8=`!#(B@refill

$B$3$l$rMQ$$$FJ#?t$NJ8;z=89g(B(@ref{Character set})$B$rAH9g$;$F(B 7bit
(@ref{7bit}) $B$J$$$7(B 8bit (@ref{8bit}) $B$N(B $BId9f2=J8;z=89g(B(@ref{Coded
character set}) $B$r:n$k$3$H$,$G$-$k!#(B

@cindex{ISO 2022}@cindex{ISO/IEC 2022:1994}
@noindent
[ISO 2022]
@quotation
International Organization for Standardization (ISO), ``Information
Processing: ISO 7-bit and 8-bit coded character sets: Code extension
techniques'', ISO/IEC 2022:1994.
@end quotation



@node iso-2022-cn, iso-2022-cn-ext, ISO 2022, Glossary
@subsection iso-2022-cn

$BCf9q8l$rI=8=$9$k$?$a$N(B MIME charset (@ref{MIME charset}) $B$N#1$D!#(B

ISO 2022 (@ref{ISO 2022}) $B$K4p$$$F(B ASCII (@ref{ASCII}) $B$K(B GB 2312
(@ref{GB 2312}), CNS 11643 plain 1, plain 2 (@ref{CNS}) $B$r(B 7bit
(@ref{7bit}) $B$GId9f3HD%(B (@ref{Code extension})$B$7$F$$$k!#(B@refill

RFC 1922 (@ref{RFC 1922}) $B$GDj5A$5$l$F$$$k!#(B


@node iso-2022-cn-ext, iso-2022-jp, iso-2022-cn, Glossary
@subsection iso-2022-cn-ext

$BCf9q8l$rI=8=$9$k$?$a$N(B MIME charset (@ref{MIME charset}) $B$N#1$D!#(B

ISO 2022 (@ref{ISO 2022}) $B$K4p$$$F(B ASCII (@ref{ASCII}) $B$K(B GB 2312
(@ref{GB 2312}), CNS 11643 plain 1 .. 7 (@ref{CNS}), ISO-IR-165
(@ref{ISO-IR-165}) $BEy$r(B 7bit (@ref{7bit}) $B$GId9f3HD%(B (@ref{Code
extension})$B$7$F$$$k!#(B@refill

RFC 1922 (@ref{RFC 1922}) $B$GDj5A$5$l$F$$$k!#(B@refill

@noindent
@strong{[Memo]}
@quotation
MULE 2.3 $B$*$h$S!"8=:_$N(B XEmacs/mule $B$G$O@5$7$/07$&$3$H$O$G$-$J$$!#(B

Emacs/mule $B$G$OMxMQ2DG=$G$"$k!#(B
@end quotation



@node iso-2022-jp, iso-2022-jp-2, iso-2022-cn-ext, Glossary
@subsection iso-2022-jp

$BF|K\8l$rI=8=$9$k$?$a$N(B MIME charset (@ref{MIME charset}) $B$N0l$D!#(B

$B8E$$(B ISO 2022 (@ref{ISO 2022}) $B$K4p$$$F(B ASCII (@ref{ASCII}), JIS
X0201-Latin, JIS X0208-1978 (@ref{JIS C6226-1978}), JIS X0208-1983
(@ref{JIS X0208}) $B$r@Z$jBX$($k(B 7bit (@ref{7bit}) $BJ8;zId9f!#(B@refill

RFC 1468 $B$GDj5A$5$l$F$$$k!#(B@refill

@noindent
@strong{[Memo]}
@quotation
JIS X0208-1996? $B$G$O(B ISO 2022 (@ref{ISO 2022}) $B$HFHN)$KDj5A$5$l$kM=Dj!#(B
@end quotation


@cindex{iso-2022-jp}@cindex{RFC 1468}
@noindent
[iso-2022-jp: RFC 1468]
@quotation
Murai J., M. Crispin, and E. van der Poel, ``Japanese Character Encoding
for Internet Messages'', June 1993.
@end quotation



@node iso-2022-jp-2, iso-2022-kr, iso-2022-jp, Glossary
@subsection iso-2022-jp-2

A MIME charset (@ref{MIME charset}), which is a multilingual extension
of iso-2022-jp (@ref{iso-2022-jp}).@refill

It is defined in RFC 1554.

@cindex{iso-2022-jp-2}@cindex{Informational}@cindex{RFC 1554}
@noindent
[iso-2022-jp-2: RFC 1554]
@quotation
Ohta M. and Handa K., ``ISO-2022-JP-2: Multilingual Extension of
ISO-2022-JP'', December 1993, Informational.
@end quotation



@node iso-2022-kr, ISO 646, iso-2022-jp-2, Glossary
@subsection iso-2022-kr

A MIME charset (@ref{MIME charset}) for Korean language (Hangul
script).@refill

It is based on ISO 2022 (@ref{ISO 2022}) code extension (@ref{code
extension}) technique to extends ASCII (@ref{ASCII}) to use KS C5601
(@ref{KS C5601}) as 7bit (@ref{7bit}) text.@refill

It is defined in RFC 1557 (@ref{RFC 1557}).


@node ISO 646, ISO 8859-1, iso-2022-kr, Glossary
@subsection ISO 646

$B3F9q$G6&DL$K;H$($k:G>.8BEY$NJ8;z=89g(B(@ref{Character set})$B$rDj$a$?$b$N!#(B
94 $BJ8;z=89g(B (@ref{94 character set})$B$N#1$D!#(BISO 646 IRV$B!J9q:]4p=`HG!K$r(B
$B85$K4v$D$+$NJ8;z$O3F9q$G0c$&J8;z$r3dEv$k$3$H$r5v$7$F$$$F!"4v$D$+$NJQ<o$,(B
$BB8:_$9$k!#(BASCII (@ref{ASCII}) $B$d(B JIS X0201-Latin $B$O$=$N0l<o!#(B

@cindex{ISO 646}@cindex{ISO/IEC 646:1991}
@noindent
[ISO 646]
@quotation
International Organization for Standardization (ISO), ``Information
technology: ISO 7-bit coded character set for information interchange'',
ISO/IEC 646:1991.
@end quotation



@node ISO 8859-1, iso-8859-1, ISO 646, Glossary
@subsection ISO 8859-1

@cindex{ISO 8859-1}@cindex{ISO 8859-1:1987}
@noindent
[ISO 8859-1]
@quotation
International Organization for Standardization (ISO), ``Information
Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 1:
Latin Alphabet No.1'', ISO 8859-1:1987.
@end quotation



@node iso-8859-1, ISO 8859-2, ISO 8859-1, Glossary
@subsection iso-8859-1

@cindex{iso-8859-1}@strong{iso-8859-1} is a MIME charset (@ref{MIME
charset}) for west-European languages written by Latin script.@refill

ISO 2022 (@ref{ISO 2022}) $B$K4p$$$F!"(BASCII (@ref{ASCII}) $B$K(B ISO 8859-1
(@ref{ISO 8859-1}) $B$r(B 8bit (@ref{8bit}) $B$GId9f3HD%(B (@ref{Code
extension})$B$7$F$$$k!#(B@refill

It is defined in RFC 2046 (@ref{RFC 2046}).


@node ISO 8859-2, iso-8859-2, iso-8859-1, Glossary
@subsection ISO 8859-2

@cindex{ISO 8859-2}@cindex{ISO 8859-2:1987}
@noindent
[ISO 8859-2]
@quotation
International Organization for Standardization (ISO), ``Information
Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 2:
Latin alphabet No.2'', ISO 8859-2:1987.
@end quotation



@node iso-8859-2, ISO 8859-3, ISO 8859-2, Glossary
@subsection iso-8859-2

@cindex{iso-8859-2}@strong{iso-8859-2} is a MIME charset (@ref{MIME
charset}) for east-European languages written by Latin script.@refill

ISO 2022 (@ref{ISO 2022}) $B$K4p$$$F!"(BASCII (@ref{ASCII}) $B$K(B ISO 8859-2
(@ref{ISO 8859-2}) $B$r(B 8bit (@ref{8bit}) $B$GId9f3HD%(B (@ref{Code
extension})$B$7$F$$$k!#(B@refill

It is defined in RFC 2046 (@ref{RFC 2046}).


@node ISO 8859-3, ISO 8859-4, iso-8859-2, Glossary
@subsection ISO 8859-3

@cindex{ISO 8859-3}@cindex{ISO 8859-3:1988}
@noindent
[ISO 8859-3]
@quotation
International Organization for Standardization (ISO), ``Information
Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 3:
Latin alphabet No.3'', ISO 8859-3:1988.
@end quotation



@node ISO 8859-4, ISO 8859-5, ISO 8859-3, Glossary
@subsection ISO 8859-4

@cindex{ISO 8859-4}@cindex{ISO 8859-4:1988}
@noindent
[ISO 8859-4]
@quotation
International Organization for Standardization (ISO), ``Information
Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 4:
Latin alphabet No.4'', ISO 8859-4:1988.
@end quotation



@node ISO 8859-5, iso-8859-5, ISO 8859-4, Glossary
@subsection ISO 8859-5

@cindex{ISO 8859-5}@cindex{ISO 8859-5:1988}
@noindent
[ISO 8859-5]
@quotation
International Organization for Standardization (ISO), ``Information
Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 5:
Latin/Cyrillic alphabet'', ISO 8859-5:1988.
@end quotation



@node iso-8859-5, ISO 8859-6, ISO 8859-5, Glossary
@subsection iso-8859-5

@cindex{iso-8859-5}@strong{iso-8859-5} is a MIME charset (@ref{MIME
charset}) for Cyrillic script.@refill

ISO 2022 (@ref{ISO 2022}) $B$K4p$$$F!"(BASCII (@ref{ASCII}) $B$K(B ISO 8859-5
(@ref{ISO 8859-5}) $B$r(B 8bit (@ref{8bit}) $B$GId9f3HD%(B (@ref{Code
extension})$B$7$F$$$k!#(B@refill

It is defined in RFC 2046 (@ref{RFC 2046}).


@node ISO 8859-6, ISO 8859-7, iso-8859-5, Glossary
@subsection ISO 8859-6

@cindex{ISO 8859-6}@cindex{ISO 8859-6:1987}
@noindent
[ISO 8859-6]
@quotation
International Organization for Standardization (ISO), ``Information
Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 6:
Latin/Arabic alphabet'', ISO 8859-6:1987.
@end quotation



@node ISO 8859-7, iso-8859-7, ISO 8859-6, Glossary
@subsection ISO 8859-7

@cindex{ISO 8859-7}@cindex{ISO 8859-7:1987}
@noindent
[ISO 8859-7]
@quotation
International Organization for Standardization (ISO), ``Information
Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 7:
Latin/Greek alphabet'', ISO 8859-7:1987.
@end quotation



@node iso-8859-7, ISO 8859-8, ISO 8859-7, Glossary
@subsection iso-8859-7

@cindex{iso-8859-7}@strong{iso-8859-7} is a MIME charset (@ref{MIME
charset}) for Greek script.@refill

ISO 2022 (@ref{ISO 2022}) $B$K4p$$$F!"(BASCII (@ref{ASCII}) $B$K(B ISO 8859-7
(@ref{ISO 8859-7}) $B$r(B 8bit (@ref{8bit}) $B$GId9f3HD%(B (@ref{Code
extension})$B$7$F$$$k!#(B@refill

It is defined in RFC 1947.

@cindex{iso-8859-7}@cindex{Informational}@cindex{RFC 1947}
@noindent
[iso-8859-7: RFC 1947]
@quotation
D. Spinellis, ``Greek Character Encoding for Electronic Mail Messages'',
May 1996, Informational.
@end quotation



@node ISO 8859-8, ISO 8859-9, iso-8859-7, Glossary
@subsection ISO 8859-8

@cindex{ISO 8859-8}@cindex{ISO 8859-8:1988}
@noindent
[ISO 8859-8]
@quotation
International Organization for Standardization (ISO), ``Information
Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 8:
Latin/Hebrew alphabet'', ISO 8859-8:1988.
@end quotation



@node ISO 8859-9, ISO-IR-165, ISO 8859-8, Glossary
@subsection ISO 8859-9

@cindex{ISO 8859-9}@cindex{ISO 8859-9:1990}
@noindent
[ISO 8859-9]
@quotation
International Organization for Standardization (ISO), ``Information
Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 9:
Latin alphabet No.5'', ISO 8859-9:1990.
@end quotation



@node ISO-IR-165, JIS X0201, ISO 8859-9, Glossary
@subsection ISO-IR-165, CCITT Extended GB 

CCITT $B$,EPO?$7$?!"Cf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=(B
$B$9$k$?$a$N(B 94x94-character set (@ref{94x94-character set})$B!#(B@refill

GB 2312 (@ref{GB 2312}) $B$H(B GB 8565 $BI=#2(B (@ref{GB 8865.2}) $B$K(B 150 $BJ8;z$[(B
$B$I$rDI2C$7$?$b$N$i$7$$!#(B@refill

ISO 2022 (@ref{ISO 2022}) $B$G$N=*C<J8;z$O(B `E' $B$G$"$k!#(B


@node JIS X0201, JIS C6226, ISO-IR-165, Glossary
@subsection JIS X0201

ISO 646 (@ref{ISO 646}) $B$NJQ<o$N#1$D$G$"$k(B Latin $BJ8;z=89g$H(B 1 byte $B$N%+(B
$B%?%+%JJ8;z=89g$+$i$J$k!#(B@refill

$B85$O(B @cindex{JIS C6220-1976}@strong{JIS C6220-1976} $B$H8@$C$?$,(B @cindex{JIS
X0201}@strong{JIS
X0201} $B$KHV9f$,JQ99$5$l$?!#(B

@cindex{JIS X0201-1976}@cindex{JIS        X 0201-1976:}
@noindent
[JIS X0201-1976]
@quotation
$BF|K\5,3J6(2q(B (Japanese Standards Association),$B!X>pJs8r49MQId9f!Y(B, ``Code
for Information Interchange'', JIS X 0201-1976:.
@end quotation


$B$^$?!"(B1996 $BG/$K2~DjHG$,=P$kM=Dj!#(B

@cindex{JIS X0201-1996?}@cindex{JIS X 0201:1996?        draft}
@noindent
[JIS X0201-1996?]
@quotation
$BF|K\5,3J6(2q(B (Japanese Standards Association),$B!X#7%S%C%H5Z$S#8%S%C%H$N>p(B
$BJs8r49MQId9f2=J8;z=89g!Y(B, ``7-bit and 8-bit coded character sets for
information interchange'', JIS X 0201:1996?  draft.
@end quotation



@node JIS C6226, JIS X0208, JIS X0201, Glossary
@subsection JIS C6226-1978

$BF|K\8l$rI=$9$?$a$K:n$i$l$?(B 94x94-character set (@ref{94x94-character
set})$B!#F|K\$N9q2HI8=`!#(BJIS X0208-1978 $B$H$b$$$&!#(B@refill

(cf. @ref{JIS X0208})



@node JIS X0208, JIS X0212, JIS C6226, Glossary
@subsection JIS X0208

$BF|K\8l$rI=$9$?$a$K:n$i$l$?(B 94x94-character set (@ref{94x94-character
set})$B!#F|K\$N9q2HI8=`!#(B1978 $BG/HG!"(B1983 $BG/HG!"(B1990 $BG/HG$,$"$k$,!"(BInternet 
$B$G$O(B 1983 $BG/HG$,$b$C$H$bNI$/;H$o$l$F$$$k!#(B@refill

JIS X0208 $B$O5-9f!"?t;z!"%m!<%^;z!"$R$i$,$J!"%+%?%+%J!"%.%j%7%cJ8;z!"%-%j(B
$B%kJ8;z!"7S@~AG!"Bh#1?e=`!"Bh#2?e=`$N4A;z$,4^$^$l$k!#C"$7!"(B1983 $BG/HG$N0l(B
$BIt$N5-9f$H7S@~AG$O(B 1978 $BG/HG$K$O$J$$!#$^$?!"0lIt$N4A;z$N;z7A$,(B 1983 $BG/HG(B
$B$G$OJQ99$5$l!"$^$?!"Bh#1?e=`$HBh#2?e=`$,F~$lBX$o$C$F$$$?$j$9$k!#$3$N$?$a!"(B
1978 $BG/HG$H(B 1983 $BG/HG$O0[$J$kJ8;z=89g$H$7$F07$o$l$k!#(B@refill

1990 $BG/$N2~Dj$G$O(B 1983 $BG/HG$KBP$9$kDI2C$,9T$o$l$?!#$3$N$?$a!"(B1990 $BG/HG(B
$B$r;X<($9$k>l9g$OA0$K99?7%7!<%1%s%9$rMQ$$$k!#(B

@cindex{JIS X0208-1978}@cindex{JIS C6226:1978}
@noindent
[JIS X0208-1978]
@quotation
$BF|K\5,3J6(2q(B (Japanese Standards Association),$B!X>pJs8r49MQ4A;zId9f7O!Y(B,
``Code of the Japanese graphic character set for information
interchange'', JIS C6226:1978.
@end quotation

@cindex{JIS X0208-1983,1990}@cindex{JIS X0208:1983,1990}
@noindent
[JIS X0208-1983,1990]
@quotation
$BF|K\5,3J6(2q(B (Japanese Standards Association),$B!X>pJs8r49MQ4A;zId9f7O!Y(B,
``Code of the Japanese graphic character set for information
interchange'', JIS X0208:1983,1990.
@end quotation


$B$^$?!"(B1996 $BG/$K2~DjHG$,=PHG$5$l$kM=Dj!#!J;z7A$NJQ99$O9T$o$l$J$$$N$GJ8(B
$B;z=89g$H$7$F$O(B 1990 $BG/HG$HF10l$G$"$k!K(B

@cindex{JIS X0208-1996?}@cindex{JIS X 0208:1996? draft}
@noindent
[JIS X0208-1996?]
@quotation
$BF|K\5,3J6(2q(B (Japanese Standards Association),$B!X#7%S%C%H5Z$S#8%S%C%H$N(B 
$B#2%P%$%H>pJs8r49MQId9f2=4A;z=89g!Y(B, ``7-bit and 8-bit double byte coded
Kanji sets for information interchange'', JIS X 0208:1996? draft.
@end quotation



@node JIS X0212, koi8-r, JIS X0208, Glossary
@subsection JIS X0212-1990

JIS X0208 (@ref{JIS X0208}) $B$K$J$+$C$?J8;z$r=8$a$?(B 94x94-character set
(@ref{94x94-character set})$B!#!VJd=u4A;z!W$H$b8F$P$l$k!#F|K\$N9q2HI8=`!#(B
ISO 2022 (@ref{ISO 2022}) $B$G$N=*C<J8;z$O(B `D'.


@node koi8-r, KS C5601, JIS X0212, Glossary
@subsection koi8-r

A MIME charset (@ref{MIME charset}) for Cyrillic script for Russian or
other languages.@refill

It is a 1 byte 8bit (@ref{8bit}) coded character set (@ref{coded
character set}), not based on ISO 2022 (@ref{ISO 2022}).  It is a
de-fact standard.@refill

It is defined in RFC 1489.@refill

@cindex{RFC 1489}
@noindent
[RFC 1489]
@quotation
A. Chernov, ``Registration of a Cyrillic Character Set'', July 1993.
@end quotation



@node KS C5601, message, koi8-r, Glossary
@subsection KS C5601-1987

A 94x94-character set (@ref{94x94-character set}) for Korean language
(Hangul script).  Korean Standard.  Final byte of ISO 2022 (@ref{ISO
2022}) is `C'.

@cindex{KS C5601}@cindex{KS C 5601:1987}
@noindent
[KS C5601]
@quotation
Korea Industrial Standards Association, ``Code for Information
Interchange (Hangul and Hanja)'', KS C 5601:1987.
@end quotation



@node message, message/rfc822, KS C5601, Glossary
@subsection message

$B$3$3$G$O(B RFC 822 (@ref{RFC 822}) $B$GDj5A$5$l$k(B mail $B$H(B RFC 1036 (@ref{RFC
1036}) $B$GDj5A$5$l$k(B news $B5-;v$NAm>N$H$7$FMQ$$$k!#(B


@node message/rfc822, method, message, Glossary
@subsection message/rfc822

@cindex{message/rfc822}@strong{message/rfc822} indicates that the body
contains an encapsulated message, with the syntax of an RFC 822
(@ref{RFC 822}) message.  It is the replacement of traditional RFC 934
(@ref{RFC 934}) encapsulation.  It is defined in RFC 2046 (@ref{RFC
2046}).


@node method, MIME, message/rfc822, Glossary
@subsection method

tm $B$GFCDj$N<oN`$N(B data $B$r:F@8$7$?$H$-<B:]$K$=$N=hM}$r9T$J$&(B
program. Emacs Lisp $B$G=q$+$l$?(B @cindex{internal method}@strong{internal
method} $B$H(B C $B$d(B script $B8@8l$J$I$G=q$+$l$?(B @cindex{external
method}@strong{external method} $B$,$"$k!#(B@refill

(cf. @ref{(tm-view-en)method})



@node MIME, MIME charset, method, Glossary
@subsection MIME

MIME stands for @cindex{Multipurpose Internet Mail
Extensions}@strong{Multipurpose Internet Mail Extensions}, it is an
extension for RFC 822 (@ref{RFC 822}).@refill

According to RFC 2045:@refill

STD 11, RFC 822, defines a message representation protocol specifying
considerable detail about US-ASCII message headers, and leaves the
message content, or message body, as flat US-ASCII text.  This set of
documents, collectively called the Multipurpose Internet Mail
Extensions, or MIME, redefines the format of messages to allow
for@refill

@enumerate
@item
textual message bodies in character sets other than US-ASCII,
@item
an extensible set of different formats for non-textual message
bodies,
@item
multi-part message bodies, and
@item
textual header information in character sets other than US-ASCII.
@end enumerate


It is defined in RFC 2045 (@ref{RFC 2045}), RFC 2046 (@ref{RFC 2046}),
RFC 2047 (@ref{encoded-word}), RFC 2048 (@ref{RFC 2048}) and RFC 2049
(@ref{RFC 2049}).


@node MIME charset, MTA, MIME, Glossary
@subsection MIME charset

Coded character set (@ref{Coded character set}) used in Content-Type
field (@ref{Content-Type field}) or charset parameter of encoded-word
(@ref{encoded-word}).@refill

It is defined in RFC 2045 (@ref{RFC 2045}).@refill

iso-2022-jp (@ref{iso-2022-jp}) $B$d(B euc-kr (@ref{euc-kr}) $B$O$=$N#1$D!#(B
$B!J$3$3$G$O!"(BMIME charset $B$OJ8;z=89g(B (@ref{Character set})$B$H6hJL$7$F>.J8(B
$B;z$G=q$$$F$$$k!K(B


@node MTA, MUA, MIME charset, Glossary
@subsection MTA

@cindex{Message Transfer Agent}@strong{Message Transfer Agent} $B$NN,$G!"(B
sendmail $B$J$I$N(B mail $BG[Aw(B program $B$H(B news server $B$NAm>N!#(B@refill

(cf. @ref{MUA})



@node MUA, MULE, MTA, Glossary
@subsection MUA

@cindex{Message User Agent}@strong{Message User Agent} $B$NN,$G!"(Bmail
reader $B$H(B news reader $B$NAm>N!#(B@refill

(cf. @ref{MTA})



@node MULE, multipart, MUA, Glossary
@subsection MULE

$BH>ED(B $B7u0l;a$i$,:n$C$?!"B?8@8l$5$l$?(B Emacs (@ref{Emacs}).@refill

[MULE] Nishikimi M., Handa K. and Tomura S., ``Mule: MULtilingual
Enhancement to GNU Emacs'', Proc. of INET'93, August, 1993.@refill

$B8=:_!"(BMULE $B$N5!G=$r(B Emacs $B$K(B merge $B$9$k:n6H$,9T$o$l$F$*$j!"(Balpha $BHG(B
(ftp://etlport.etl.go.jp/pub/mule/mule-19.33-gamma.taz) $B$,B8:_$9$k!#(B

$B$=$NB>!"(BXEmacs $B$K(B merge $B$7$?$b$N$bB8:_$9$k!#(B@refill

$B$3$N$?$a!"8=:_$G$OB?8@8l(B Emacs $B$O!"85!9$N(B MULE $B$r4^$a$F#3<oN`$"$k$3$H$K(B
$B$J$k!#(B@refill

$B$=$3$G!"$3$3$G$O!"B?8@8l(B Emacs $B$NAm>N$r(B @cindex{mule}@strong{mule}, $B85!9(B
$B$N(B MULE $B$r(B @cindex{MULE}@strong{MULE}, mule $B5!G=$r(B merge $B$7$?(B Emacs $B$r(B
@cindex{Emacs/mule}@strong{Emacs/mule}, mule $B5!G=$r(B merge $B$7$?(B XEmacs $B$r(B 
@cindex{XEmacs/mule}@strong{XEmacs/mule} $B$H8F$V$3$H$K$9$k!#(B


@node multipart, multipart/alternative, MULE, Glossary
@subsection Multipart

@cindex{multipart}@strong{multipart} means media type (@ref{media type})
to insert multiple entities (@ref{entities}) in a single body.  Or it
also indicates a message consists of multiple entities.@refill

There are following subtypes registered in RFC 2046 (@ref{RFC 2046}):

@itemize @bullet
@item
multipart/mixed (@ref{multipart/mixed})
@item
multipart/alternative (@ref{multipart/alternative})
@item
multipart/digest (@ref{multipart/digest})
@item
multipart/parallel (@ref{multipart/parallel})
@end itemize

@noindent
and registered in RFC 1847 (@ref{Security multipart}):

@itemize @bullet
@item
multipart/signed (@ref{multipart/signed})
@item
multipart/encrypted (@ref{multipart/encrypted})
@end itemize



@node multipart/alternative, multipart/digest, multipart, Glossary
@subsection multipart/alternative

@cindex{multipart/digest}@strong{multipart/digest} is one of multipart
(@ref{multipart}) media types.  This type is syntactically identical to
multipart/mixed (@ref{multipart/mixed}), but the semantics are
different.  In particular, each of the body parts is an ``alternative''
version of the same information.@refill

(cf. @ref{RFC 2046})



@node multipart/digest, multipart/encrypted, multipart/alternative, Glossary
@subsection multipart/digest

@cindex{multipart/digest}@strong{multipart/digest} is one of multipart
(@ref{multipart}) media types.  This type is syntactically identical to
multipart/mixed (@ref{multipart/mixed}), but the semantics are
different.  In particular, in a digest, the default Content-Type value
for a body part is changed from text/plain (@ref{text/plain}) to
message/rfc822 (@ref{message/rfc822}).@refill

This is the replacement of traditional RFC 1153 (@ref{RFC 1153}) based
encapsulation (@ref{encapsulation}).@refill

(cf. @ref{RFC 2046})



@node multipart/encrypted, multipart/mixed, multipart/digest, Glossary
@subsection multipart/encrypted

RFC 1847 $B$GDj5A$5$l$?(B Security multipart (@ref{Security multipart}) $B$N#1(B
$B$D$G!"0E9f2=$5$l$?(B message $B$rI=8=$9$k$N$KMQ$$$k!#(B@refill

(cf. @ref{PGP/MIME})



@node multipart/mixed, multipart/parallel, multipart/encrypted, Glossary
@subsection multipart/mixed

Primary and default subtype of multipart (@ref{multipart}), it is used
when the body parts are independent and need to be bundled in a
particular order.@refill

(cf. @ref{RFC 2046})



@node multipart/parallel, multipart/signed, multipart/mixed, Glossary
@subsection multipart/parallel

@cindex{multipart/parallel}@strong{multipart/parallel} is a subtype of
multipart (@ref{multipart}).  This type is syntactically identical to
multipart/mixed (@ref{multipart/mixed}), but the semantics are
different.  In particular, in a parallel entity, the order of body parts
is not significant.@refill

(cf. @ref{RFC 2046})



@node multipart/signed, PGP, multipart/parallel, Glossary
@subsection multipart/signed

RFC 1847 $B$GDj5A$5$l$?(B Security multipart (@ref{Security multipart}) $B$N#1(B
$B$D$G!"EE;R=pL>$rI=8=$9$k$N$KMQ$$$k!#(B@refill

(cf. @ref{PGP/MIME})



@node PGP, PGP-kazu, multipart/signed, Glossary
@subsection PGP

Phil Zimmermann $B;a$,:n@.$7$?8x3+800E9f=hM}7O$N#1$D!#(Bmessage
(@ref{message}) $B$N0E9f2=$dEE;R=pL>$r9T$&$3$H$,$G$-$k!#(BPretty Good
Privacy $B$NN,!#(B@refill

$BEAE}E*$J(B PGP $B$G$O(B encapsulation (@ref{encapsulation}) $B$K(B RFC 934
(@ref{RFC 934})$B$K=`$8$?J}K!$rMQ$$$k!#$3$l$O(B MIME (@ref{MIME}) $B$HL7=b$9$k(B
$B$N$G(B PGP/MIME (@ref{PGP/MIME}) $B$,Ds0F$5$l$F$$$k!#0lJ}!"(BMIME $B$K$*$$$F(B PGP 
$B$N(Bencapsulation $B$rMQ$$$kJ}K!(B (cf. @ref{PGP-kazu})
 $B$bMxMQ$5$l$F$-$?!#$7$+$7!":#8e$O(B PGP/MIME $B$KE}0l$7$F$$$/J}$,K>$^$7$$!#(B
@refill

@cindex{PGP}@cindex{Informational}@cindex{RFC 1991}
@noindent
[PGP: RFC 1991]
@quotation
D. Atkins, W. Stallings and P. Zimmermann, ``PGP Message Exchange
Formats'', August 1996, Informational.
@end quotation




@node PGP-kazu, PGP/MIME, PGP, Glossary
@subsection PGP-kazu

$B;3K\(B $BOBI'(B $B;a$,Ds0F$7$?(B MIME (@ref{MIME}) $B$G(B PGP (@ref{PGP}) $B$rMxMQ$9$k$?(B
$B$a$NJ}K!$r$3$3$G$O(B @cindex{PGP-kazu}@strong{PGP-kazu} $B$H8F$V$3$H$K$9$k!#(B

PGP-kazu $B$O(B @cindex{application/pgp}@strong{application/pgp} $B$H$$$&(B 
content-type (@ref{content-type}) $B$rDj5A$9$k!#(B@refill

application/pgp $B$N(B part $B$G$O(B PGP $B$N(B encapsulation (@ref{encapsulation}) 
$B$,MQ$$$i$l$k!#(BPGP $B$N(B encapsulation (cf. @ref{RFC 934})
 $B$H(B MIME $B$N(B encapsulation $B$OL7=b$9$k$N$G!"(BPGP $B$N(B encapsulation $B$r2r$+$J(B
$B$$8B$j!"Cf$K4^$^$l$?(B MIME message $B$rFI$`$3$H$,$G$-$J$/$J$k!#B($A!"(B
PGP-kazu $B$KBP1~$7$F$$$J$$(B MIME $B$KBP1~$7$?(B MUA (@ref{MUA}) $B$O$=$N(B part $B$,(B
$BFI$a$J$/$J$k!#$=$NBe$o$j!"(BMIME $B$KBP1~$7$F$$$J$$(B PGP $BBP1~$N(B MUA
(@ref{MUA}) $B$G$b(B message $B$rFI$`$3$H$,$G$-$k!#(B@refill

PGP-kazu $B$G$O(B MUA $B$O(B PGP $B$N$H(B MIME $B$N$H$$$&#2$D$N(B encapsulation $B$rCN$i$J(B
$B$1$l$P$J$i$J$$!#$^$?!"(Bapplication/pgp part $B$r(B parse $B$9$k$?$a$K$O!"$^$:!"(B
pgp $B$N=hM}$r9T$o$J$1$l$P$J$i$J$$$N$G!"(Bparse $B=hM}$,J#;($K$J$k!#(B@refill

$B$^$?!"(BInternet $B$G$O:#8e(B PGP/MIME (@ref{PGP/MIME}) $B$NJ}8~$GI8=`2=$7$F$$$3(B
$B$&$H$$$&$3$H$G9g0U$,<h$l$F$$$k!#$h$C$F!":#8e$O(B PGP-kazu $B$OMQ$$$J$$$N$,K>(B
$B$^$7$$!#(B@refill

[draft-kazu-pgp-mime-00.txt] Yamamoto K., ``PGP MIME Integration'',
October, 1995


@node PGP/MIME, Quoted-Printable, PGP-kazu, Glossary
@subsection PGP/MIME

Michael Elkins $B;a$,Ds0F$7$?(B MIME (@ref{MIME}) $B$G(B PGP (@ref{PGP}) $B$rMxMQ(B
$B$9$k$?$a$NJ}K!!#(B@refill

RFC 1847 (@ref{Security multipart}) $B$K4p$-!"(BMIME $B$N(B multipart $B$K$h$k(B 
encapsulation (@ref{encapsulation}) $B$r9T$&!#$3$N$?$a!"(BMIME $B$N<+A3$J3HD%(B
$B$K$J$C$F$$$k!#$7$+$7!"EAE}E*$J(B PGP$B$H$N8_49@-$,<:$o$l$F$$$k!#(B@refill

PGP/MIME $B$G$O(B PGP-kazu (@ref{PGP-kazu}) $B$H0[$J$j!"(BMIME $B$N(B encapsulation 
$B$N$_$rMQ$$$k!#$^$?!"$3$N$?$a!"(BPGP $B$N=hM}$r9T$&A0$K(B message $B$N(B parse $B$r9T(B
$B$&$3$H$,$G$-$k!#(B@refill

Internet $B$G$O:#8e(B PGP/MIME (@ref{PGP/MIME}) $B$NJ}8~$GI8=`2=$7$F$$$3$&$H$$(B
$B$&$3$H$G9g0U$,<h$l$F$$$k!#$h$C$F!":#8e$O(B PGP $B$rMQ$$$k>l9g$O(B PGP/MIME$B$rMQ(B
$B$$$k$N$,K>$^$7$$!#(B

@cindex{PGP/MIME}@cindex{Standards Track}@cindex{RFC 2015}
@noindent
[PGP/MIME: RFC 2015]
@quotation
M. Elkins, ``MIME Security with Pretty Good Privacy (PGP)'', October
1996, Standards Track.
@end quotation



@node Quoted-Printable, RFC 821, PGP/MIME, Glossary
@subsection Quoted-Printable

@cindex{Quoted-Printable}@strong{Quoted-Printable} is a transfer
encoding method of MIME (@ref{MIME}) defined in RFC 2045 (@ref{RFC
2045}).@refill

If the data being encoded are mostly US-ASCII text, the encoded form of
the data remains largely recognizable by humans.@refill

(cf. @ref{Base64})



@node RFC 821, RFC 822, Quoted-Printable, Glossary
@subsection RFC 821

@cindex{SMTP}@strong{SMTP} $B$H8F$P$l$k(B Internet mail $B$NG[AwK!$NI8=`$rDj$a(B
$B$F$$$k(B RFC.

@cindex{SMTP}@cindex{STD 10}@cindex{RFC 821}
@noindent
[SMTP: RFC 821]
@quotation
J. Postel, ``Simple Mail Transfer Protocol'', August 1982, STD 10.
@end quotation



@node RFC 822, RFC 934, RFC 821, Glossary
@subsection RFC 822

Internet mail $B$N<g$K(B @cindex{message header}@strong{message header} $B$K4X$9$k7A<0$K(B
$B4X$9$kI8=`$rDj$a$F$$$k(B RFC.

@noindent
@strong{[Memo]}
@quotation

news message $B$b$3$l$K=`$8$F$$$k$N$G!"(B@cindex{Internet
mail}@strong{Internet mail} $B$H=q$/$h$j$b!"(B@cindex{Internet
message}@strong{Internet message} $B$H=q$$$?J}$,NI$$$+$b$7$l$J$$!#(B
@end quotation


@cindex{STD 11}@cindex{RFC 822}
@noindent
[RFC 822]
@quotation
D. Crocker, ``Standard for the Format of ARPA Internet Text Messages'',
August 1982, STD 11.
@end quotation



@node RFC 934, RFC 1036, RFC 822, Glossary
@subsection RFC 934

Internet mail (@ref{RFC 822}) $B$N(B 
@cindex{encapsulation}@strong{encapsulation} (@ref{encapsulation}) $B$NJ}(B
$BK!$rDj$a$?(B RFC.@refill

MIME (@ref{MIME}) $B$HL7=b$9$k$N$G!"8=:_$G$O(B message/rfc822
(@ref{message/rfc822}) $B$rMQ$$$k$Y$-$G$"$k!#(B


@cindex{RFC 934}
@noindent
[RFC 934]
@quotation
Marshall T. Rose and Einar A. Stefferud, ``Proposed Standard for Message
Encapsulation'', January 1985.
@end quotation



@node RFC 1036, RFC 1153, RFC 934, Glossary
@subsection RFC 1036

USENET $B$G$N(B message $B$N7A<0$rDj$a$?(B RFC. RFC 822 (@ref{RFC 822})$B$N(B subset 
$B$K$J$C$F$$$k!#(BInternet $B$NI8=`$G$O$J$$$,!"(BUSENET $B0J30$N(B netnews $B$G$b$3$l(B
$B$K=`$8$F$$$k$b$N$,B?$$!#(B

@cindex{USENET}@cindex{RFC 1036}
@noindent
[USENET: RFC 1036]
@quotation
M. Horton and R. Adams, ``Standard for Interchange of USENET Messages'',
December 1987, (obsolete RFC 850).
@end quotation



@node RFC 1153, RFC 1557, RFC 1036, Glossary
@subsection RFC 1153

$BJ#?t$N(B Internet mail (@ref{RFC 822}) $B$r(B 
@cindex{encapsulation}@strong{encapsulation} (@ref{encapsulation}) $B$9$k(B
$B$?$a$NJ}K!$rDj$a$?(B RFC. RFC 934 (@ref{RFC 934}) $B$rMQ$$$k!#(B@refill

MIME (@ref{MIME}) $B$HL7=b$9$k$N$G!"8=:_$G$O(B message/rfc822
(@ref{message/rfc822}) $B$rMQ$$$?(B multipart (@ref{multipart}) $B$rMQ$$$k$Y$-(B
$B$G$"$k!#(B@refill

(cf. @ref{multipart/digest})


@cindex{RFC 1153}
@noindent
[RFC 1153]
@quotation
F. Wancho, ``Digest Message Format'', April 1990.
@end quotation



@node RFC 1557, RFC 1922, RFC 1153, Glossary
@subsection RFC 1557

euc-kr (@ref{euc-kr}) $B$H(B iso-2022-kr (@ref{iso-2022-kr}) $B$H$$$&4Z9q8l$N(B
$B$?$a$N(B MIME charset (@ref{MIME charset}) $B$rDj5A$7$F$$$k(B RFC.

@cindex{Informational}@cindex{RFC 1557}
@noindent
[RFC 1557]
@quotation
U. Choi, K. Chon and H. Park, ``Korean Character Encoding for Internet
Messages'', December 1993, Informational.
@end quotation



@node RFC 1922, RFC 2045, RFC 1557, Glossary
@subsection RFC 1922

iso-2022-cn (@ref{iso-2022-cn}), iso-2022-cn-ext
(@ref{iso-2022-cn-ext}), cn-gb (@ref{cn-gb}), cn-big5 (@ref{cn-big5}) $B$H(B
$B$$$C$?Cf9q8l$N$?$a$N(B MIME charset (@ref{MIME charset}) $B$rDj5A$7$F$$$k(B 
RFC.@refill

$B$3$l$K2C$($F!"(B@cindex{charset-edition}@strong{charset-edition} $B$H(B 
@cindex{charset-extension}@strong{charset-extension} $B$H$$$&(B Content-Type
field (@ref{Content-Type field}) $B$N(B parameter $B$rDj5A$7$F$$$k!#(B

@cindex{Informational}@cindex{RFC 1922}
@noindent
[RFC 1922]
@quotation
Zhu, HF., Hu, DY., Wang, ZG., Kao, TC., Chang, WCH. and Crispin, M.,
``Chinese Character Encoding for Internet Messages'', March 1996,
Informational.
@end quotation



@node RFC 2045, RFC 2046, RFC 1922, Glossary
@subsection RFC 2045

@cindex{Standards Track}@cindex{RFC 2045}
@noindent
[RFC 2045]
@quotation
N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
(MIME) Part One: Format of Internet Message Bodies'', November 1996,
Standards Track (obsolete RFC 1521, 1522, 1590).
@end quotation



@node RFC 2046, RFC 2048, RFC 2045, Glossary
@subsection RFC 2046

@cindex{Standards Track}@cindex{RFC 2046}
@noindent
[RFC 2046]
@quotation
N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
(MIME) Part Two: Media Types'', November 1996, Standards Track (obsolete
RFC 1521, 1522, 1590).
@end quotation



@node RFC 2048, RFC 2049, RFC 2046, Glossary
@subsection RFC 2048

@cindex{Standards Track}@cindex{RFC 2048}
@noindent
[RFC 2048]
@quotation
N. Freed, J. Klensin and J. Postel, ``Multipurpose Internet Mail
Extensions (MIME) Part Four: Registration Procedures'', November 1996,
Standards Track (obsolete RFC 1521, 1522, 1590).
@end quotation



@node RFC 2049, plain text, RFC 2048, Glossary
@subsection RFC 2049

@cindex{Standards Track}@cindex{RFC 2049}
@noindent
[RFC 2049]
@quotation
N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
(MIME) Part Five: Conformance Criteria and Examples'', November 1996,
Standards Track (obsolete RFC 1521, 1522, 1590).
@end quotation



@node plain text, Security multipart, RFC 2049, Glossary
@subsection plain text

$B=qBN$dAHHG$K4X$9$k>pJs$r;}$?$J$$(B $BJ8;zId9f(B(@ref{Coded character set})$B$N$_(B
$B$GI=8=$5$l$k(B text $B>pJs!#(B(cf. @ref{text/plain})



@node Security multipart, text/enriched, plain text, Glossary
@subsection Security multipart

MIME (@ref{MIME}) $B$G0E9f$dEE;R=qL>$rMQ$$$k$?$a$N7A<0!#(B
@cindex{multipart/signed}@strong{multipart/signed}
(@ref{multipart/signed}) $B$H(B 
@cindex{multipart/encrypted}@strong{multipart/encrypted}
(@ref{multipart/encrypted}) $B$H$$$&(B multipart $B$rMQ$$$k!#(BMOSS $B$d(B PGP/MIME
(@ref{PGP/MIME}) $B$O$3$l$K4p$$$F$$$k!#(B

@cindex{Security multipart}@cindex{Standards Track}@cindex{RFC 1847}
@noindent
[Security multipart: RFC 1847]
@quotation
James Galvin, Gale Murphy, Steve Crocker and Ned Freed, ``Security
Multiparts for MIME: Multipart/Signed and Multipart/Encrypted'', October
1995, Standards Track.
@end quotation



@node text/enriched, text/plain, Security multipart, Glossary
@subsection text/enriched

RFC 1521 $B$GDj5A$5$l$?(B @cindex{text/richtext}@strong{text/richtext} $B$KBe(B
$B$o$C$F!"=qBN$dAHHG$K4X$9$k>pJs$r;}$C$?(B text$B$rI=8=$9$k$?$a$N(B media type
(@ref{media type}).

@cindex{text/enriched}@cindex{RFC 1896}
@noindent
[text/enriched: RFC 1896]
@quotation
P. Resnick and A. Walker, ``The text/enriched MIME Content-type'',
February 1996, (obsolete RFC 1563).
@end quotation



@node text/plain, tm-kernel, text/enriched, Glossary
@subsection text/plain

@cindex{text/plain}@strong{text/plain} is a media type (@ref{media
type}) for plain text (@ref{plain text}), defined in RFC 2046 (@ref{RFC
2046}).@refill

The default media type of ``text/plain; charset=us-ascii'' for Internet
mail describes existing Internet practice.  That is, it is the type of
body defined by RFC 822 (@ref{RFC 822}).@refill

(cf. @ref{MIME charset}) (cf. @ref{us-ascii})



@node tm-kernel, tm-MUA, text/plain, Glossary
@subsection tm-kernel, tm

Emacs $B$G(B MIME (@ref{MIME}) $B$rMxMQ$9$k$?$a$N(B user interface $B$rDs6!$9$k(B 
library $B72!#(B`tools for MIME' $B$NN,!#(B

@noindent
@strong{[$B$I$&$G$bNI$$$3$H(B(^-^;]}
@quotation

@itemize @bullet
@item
 tm $B$O(B ``tiny-mime'' $B$NN,$8$c$J$$$i$7$$$>(B (^-^;
  
@item
 tm $B$O:n<T$N%$%K%7%c%k$8$c$J$$$i$7$$$>(B (^-^;
  
@item
 ``Tools for MIME'' $B$NN,$H$$$&$N$O$3$8$D$1$i$7$$$>(B (^-^;
@end itemize
@end quotation



@node tm-MUA, us-ascii, tm-kernel, Glossary
@subsection tm-MUA

tm (@ref{tm-kernel}) $B$rMQ$$$?(B MUA (@ref{MUA}) $B$b$7$/$O(B MUA $B$KBP$9$k(B 
extender.@refill

@cindex{tm $BBg@9$j(B package}@strong{tm $BBg@9$j(B package} $B$K$O(B

@itemize @bullet
@item
mh-e (@ref{(mh-e)}) $BMQ$N(B @cindex{tm-mh-e}@strong{tm-mh-e}
@item
GNUS $BMQ$N(B @cindex{tm-gnus}@strong{tm-gnus}
@item
Gnus $BMQ$N(B @cindex{gnus-mime}@strong{gnus-mime} (@ref{(gnus-mime-en)})
@item
VM $BMQ$N(B @cindex{tm-vm}@strong{tm-vm}
@item
RMAIL $BMQ$N(B @cindex{tm-rmail}@strong{tm-rmail}
@end itemize

@noindent
$B$,4^$^$l$F$$$k!#(B

$BFHN)$7$?(B MUA $B$H$7$F$O(B cmail (@ref{(cmail)}) $B$,(B tm $B$rMxMQ2DG=$G$"$k!#(B


@node us-ascii,  , tm-MUA, Glossary
@subsection us-ascii

$B%"%a%j%+O"K.$J$I$G;H$o$l$k1Q8l$J$I$rI=8=$9$k$?$a$N(B MIME charset
(@ref{MIME charset}) $B$N#1$D!#(B@refill

ASCII (@ref{ASCII}) $B$N$_$+$i$J$j(B ISO 2022 (@ref{ISO 2022}) $B$K$h$kId9f3H(B
$BD%(B (@ref{Code extension})$B$O5v$5$l$J$$!#(B@refill

Internet mail $B$K$*$1$kI8=`$NId9f2=J8;z=89g(B(@ref{Coded character set})$B$G(B
$B$"$j!"L@<(E*$K(B MIME charset $B$,<($5$l$J$$>l9g$O86B'$H$7$F(B 
@cindex{us-ascii}@strong{us-ascii} $B$,;H$o$l$k!#(B@refill

$B$^$?!"(BRFC 822 (@ref{RFC 822}) $B$K$*$1$k(B @cindex{ASCII}@strong{ASCII} $B$O(B 
us-ascii $B$r;X$9$b$N$H2r<a$9$Y$-$G$"$k!#(B


@node Setting, Bug report, Introduction, Top
@chapter Setting

In the tm package, two files, @file{mime-setup.el} and
@file{tm-setup.el}, are provided to ease the setup.@refill

The @file{mime-setup.el} is used for the whole MIME related
setup including MIME encoding using @file{tm-edit.el}, while
@file{tm-setup.el} is used to set up tm-MUA only.


@menu
* mime-setup::                  Normal setting
* tm-setup::                    Setting not to use tm-edit
* setting for VM::              Setting for VM
* manual setting::              Setting up without loading provided setup files
@end menu

@node mime-setup, tm-setup, Setting, Setting
@section Normal setting

If you want normal setting, please use @cindex{mime-setup}@strong{mime-setup}.
For example, please insert following into @file{~/.emacs}:

@lisp
(load "mime-setup")
@end lisp


As @file{mime-setup.el} loads @file{tm-setup.el}, you
don't need to load @file{tm-setup.el} when you use
@file{mime-setup.el} (Description of old version of Gnus FAQ is
wrong!)


@menu
* signature::                   
* Notice about GNUS::           Notices for GNUS
@end menu

@node signature, Notice about GNUS, mime-setup, mime-setup
@subsection signature

You can set up the @cindex{automatic signature selection
tool}@strong{automatic signature selection
tool} using @file{mime-setup}. If you want to
automatically select the signature file depending on how the message
headers show, add lines like shown below to your .emacs (Refer to the
reference manual of @file{signature.el} for more details).

@lisp
(setq signature-file-alist
      '((("Newsgroups" . "jokes")       . "~/.signature-jokes")
        (("Newsgroups" . ("zxr" "nzr")) . "~/.signature-sun")
        (("To" . ("ishimaru" "z-suzuki")) . "~/.signature-sun")
        (("To" . "tea")                 . "~/.signature-jokes")
        (("To" . ("sim" "oku" "takuo")) . "~/.signature-formal")
        ))
@end lisp



@defvar mime-setup-use-signature

If it is not @code{nil}, @file{mime-setup.el} sets up for
@file{signature.el}.  Its default value is @code{t}.
@end defvar



@defvar mime-setup-signature-key-alist

It defines key to bind signature inserting command for each
major-mode.  Its default value is following:

@lisp
	((mail-mode . "\C-c\C-w"))
@end lisp


If you want to change, please rewrite it.  For example:

@lisp
(set-alist 'mime-setup-signature-key-alist
	   'news-reply-mode "\C-c\C-w")
@end lisp

@end defvar



@defvar mime-setup-default-signature-key

If key to bind signature inserting command for a major-mode is not found
from @code{mime-setup-signature-key-alist}, its value is used as key.
Its default value is @code{"\C-c\C-s"}.
@end defvar



@node Notice about GNUS,  , signature, mime-setup
@subsection Notices for GNUS

When @file{mime-setup.el} sets up for @file{signature.el}, it sets
variable @code{gnus-signature-file} to @code{nil}.  Therefore GNUS does
not insert signature automatically when it is sending a message.  Reason
of this setting is following:@refill

GNUS inserts signature after @file{tm-edit.el} composed as MIME message.
Therefore signature inserted by GNUS is not processed as a valid MIME
part.  In particular, for multipart message, signature places in outside
of MIME part.  So MIME MUA might not display it.@refill

Other notice is key bind.  In historical reason, key bind to insert
signature is @kbd{C-c C-s} (like mh-e (@ref{(mh-e)})) instead of
@kbd{C-c C-w}. If you change to GNUS's default, please set following:

@lisp
(set-alist 'mime-setup-signature-key-alist 'news-reply-mode "\C-c\C-w")
@end lisp



@node tm-setup, setting for VM, mime-setup, Setting
@section Setting not to use tm-edit

@cindex{tm-setup}@strong{tm-setup} only sets up tm-MUA (@ref{tm-MUA})s.
In other words, it is a setting to avoid to use tm-edit.  If you don't
want to compose MIME message or want to use other MIME composer, please
use it instead of @file{mime-setup.el}.@refill

For example, please insert following into @file{~/.emacs}:

@lisp
(load "tm-setup")
@end lisp



@noindent
@strong{[Memo]}
@quotation

If you use @file{mime-setup.el}, you you don't need to load
@file{tm-setup.el}.
@end quotation



@node setting for VM, manual setting, tm-setup, Setting
@section Setting for VM

If you use @cindex{vm}@strong{vm}, please insert following in
@file{~/.vm}:

@lisp
(require 'tm-vm)
@end lisp



@noindent
@strong{[Notice]}
@quotation

If you use @cindex{BBDB}@strong{BBDB}, please insert @code{(require
'tm-vm)} @strong{after} @code{(bbdb-insinuate-vm)}.
@end quotation



@node manual setting,  , setting for VM, Setting
@section Setting up without loading provided setup files

You may find the valuable hints in @file{mime-setup.el} or
@file{tm-setup.el} if you want to set up MIME environment
without loading the tm-provided setup files.

@noindent
@strong{[Memo]}
@quotation

Current tm provides some convenient features to expect tm-edit, and
they can not use if @file{mime-setup.el} is not used.  If you
want to set up original setting to use tm-edit, please declare
following setting:

@lisp
(provide 'mime-setup)
@end lisp

@end quotation



@node Bug report, Concept Index, Setting, Top
@chapter How to report bug and about mailing list of tm

If you write bug-reports and/or suggestions for improvement, please
send them to the tm Mailing List:

@itemize @bullet
@item
 Japanese <bug-tm-ja@@chamonix.jaist.ac.jp>
@item
 English <bug-tm-en@@chamonix.jaist.ac.jp>
@end itemize


Notice that, we does not welcome bug reports about too old version.
Bugs in old version might be fixed.  So please try latest version at
first.@refill

You should write @cindex{good bug report}@strong{good bug report}.  If
you write only ``tm does not work'', we can not find such situations.
At least, you should write name, type, variants and version of OS,
emacs, tm and MUA, and setting.  In addition, if error occurs, to send
backtrace is very important. (cf. @ref{(emacs)Bugs}) @refill

Bug may not appear only your environment, but also in a lot of
environment (otherwise it might not bug).  Therefor if you send mail to
author directly, we must write a lot of mails.  So please send mail to
address for tm bugs instead of author.@refill

Via the tm ML, you can report tm bugs, obtain the latest release of
tm, and discuss future enhancements to tm.  To join the tm ML, send
e-mail to:

@itemize @bullet
@item
 Japanese <tm-ja-admin@@chamonix.jaist.ac.jp>
@item
 English  <tm-en-admin@@chamonix.jaist.ac.jp>
@end itemize

@noindent
Since the user registration is done manually, please write the mail
body in human-recognizable language (^_^).


@node Concept Index, Variable Index, Bug report, Top
@chapter Concept Index

@printindex cp

@node Variable Index,  , Concept Index, Top
@chapter Variable Index

@printindex vr
@bye