2 @setfilename tm-en.info
3 @settitle{tm 7.100 Manual (English Version)}
5 @title tm 7.100 Manual (English Version)
6 @author MORIOKA Tomohiko <morioka@@jaist.ac.jp>
9 @node Top, Introduction, (dir), (dir)
10 @top tm 7.100 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
26 @node Introduction, Setting, Top, Top
29 The tm package is a set of modules to enjoy MIME on GNU Emacs. Using
34 playback or view the MIME messages using tm-view
36 compose MIME message using tm-edit
38 use the enhanced MIME features with mh-e, GNUS, Gnus, RMAIL and VM
44 Please read following about each topics:
48 tm-MUA for Gnus (@ref{(gnus-mime-en)})
50 tm-MUA for GNUS (@ref{(tm-gnus-en)})
52 tm-MUA for mh-e (@ref{(tm-mh-e-en)})
54 mime/viewer-mode (@ref{(tm-view-en)})
56 mime/editor-mode (@ref{(tm-edit-en)})
65 @node Glossary, , Introduction, Introduction
74 * 94x94-character set::
78 * cn-gb:: cn-gb, gb2312
79 * cn-big5:: cn-big5, big5
80 * CNS 11643:: CNS 11643-1992
81 * coded character set:: Coded character set, Character code
82 * code extension:: Code extension
83 * Content-Disposition:: Content-Disposition field
84 * Content-Type field::
91 * GB 2312:: GB 2312-1980
92 * GB 8565.2:: GB 8565.2-1988
93 * graphic character set:: Graphic Character Set
115 * ISO-IR-165:: ISO-IR-165, CCITT Extended GB
117 * JIS C6226:: JIS C6226-1978
119 * JIS X0212:: JIS X0212-1990
121 * KS C5601:: KS C5601-1987
131 * multipart:: Multipart
132 * multipart/alternative::
134 * multipart/encrypted::
136 * multipart/parallel::
154 * Security multipart::
157 * tm-kernel:: tm-kernel, tm
162 @node 7bit, 8bit, Glossary, Glossary
164 @cindex 7bit (textual) string
168 @strong{7bit} means any integer between 0 .. 127.@refill
170 Any data represented by 7bit integers is called @strong{7bit data}.@refill
172 Textual string consisted of Control characters between 0 .. 31 and 127,
173 and space represented by 32, and graphic characters between 33 .. 236
174 are called @strong{7bit (textual) string}.@refill
176 Traditional Internet MTA (@ref{MTA}) can translate 7bit data, so it is
177 no need to translate by Quoted-Printable (@ref{Quoted-Printable}) or
178 Base64 (@ref{Base64}) for 7bit data.@refill
180 However if there are too long lines, it can not translate by 7bit MTA
181 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
182 ``7bit data'' has a line more than 999 bytes, it is regarded as binary
183 (@ref{binary}). For example, Postscript file should be encoded by
187 @node 8bit, 94-character set, 7bit, Glossary
189 @cindex 8bit (textual) string
193 @strong{8bit} means any integer between 0 .. 255.@refill
195 Any data represented by 8bit integers is called @strong{8bit data}.@refill
197 Textual string consisted of Control characters between 0 .. 31, 127, and
198 128 .. 159, and space represented by 32, and graphic characters between
199 33 .. 236 and 160 .. 255 are called @strong{8bit (textual) string}.@refill
201 For example, iso-8859-1 (@ref{iso-8859-1}) or euc-kr (@ref{euc-kr}) are
202 coded-character-set represented by 8bit textual string.@refill
204 Traditional Internet MTA (@ref{MTA}) can translate only 7bit
205 (@ref{7bit}) data, so if a 8bit data will be translated such MTA, it
206 must be encoded by Quoted-Printable (@ref{Quoted-Printable}) or Base64
207 (@ref{Base64}).@refill
209 However 8bit MTA are increasing today.@refill
211 However if there are too long lines, it can not translate by 8bit MTA
212 even if it is 8bit data. RFC 2045 (@ref{RFC 2045}) require lines in
213 8bit data must be less than 998 bytes. So if a ``8bit data'' has a line
214 more than 999 bytes, it is regarded as binary (@ref{binary}), so it must
215 be encoded by Base64 or Quoted-Printable.
218 @node 94-character set, 96-character set, 8bit, Glossary
219 @subsection 94-character set
220 @cindex 94-character set
222 @strong{94-character set} is a kind of 1 byte graphic character set
223 (@ref{graphic character set}), each characters are in positions 02/01
224 (33) to 07/14 (126) or 10/01 (161) to 15/14 (254). (ex. ASCII
225 (@ref{ASCII}), JIS X0201-Latin)
228 @node 96-character set, 94x94-character set, 94-character set, Glossary
229 @subsection 96-character set
230 @cindex 96-character set
232 @strong{96-character set} is a kind of 1 byte graphic character set
233 (@ref{graphic character set}), each characters are in positions 02/00
234 (32) to 07/15 (126) or 10/00 (160) to 15/15 (255). (ex. ISO 8859)
237 @node 94x94-character set, ASCII, 96-character set, Glossary
238 @subsection 94x94-character set
239 @cindex 94x94-character set
241 @strong{94x94-character set} is a kind of 2 byte graphic character set
242 (@ref{graphic character set}), each bytes are in positions 02/01 (33) to
243 07/14 (126) or 10/01 (161) to 15/14 (254). (ex. JIS X0208 (@ref{JIS X0208}), GB 2312 (@ref{GB 2312}))
246 @node ASCII, Base64, 94x94-character set, Glossary
248 @cindex ANSI X3.4:1986
252 @strong{ASCII} is a 94-character set (@ref{94-character set}) contains
253 primary latin characters (A-Z, a-z), numbers and some characters. It is
254 a standard of the United States of America. It is a variant of ISO 646
261 ``Coded Character Set -- 7-Bit American Standard Code for Information
262 Interchange'', ANSI X3.4:1986.
267 @node Base64, binary, ASCII, Glossary
272 @strong{Base64} is a transfer encoding method of MIME (@ref{MIME})
273 defined in RFC 2045 (@ref{RFC 2045}).@refill
275 The encoding process represents 24-bit groups of input bits as output
276 strings of 4 encoded characters. Encoded characters represent integer 0
277 .. 63 or @strong{pad}. Base64 data must be 4 * n bytes, so pad is used
278 to adjust size.@refill
280 These 65 characters are subset of all versions of ISO 646, including
281 US-ASCII, and all versions of EBCDIC. So it is safe even if it is
282 translated by non-Internet gateways.
285 @node binary, cn-gb, Base64, Glossary
289 Any byte stream is called @strong{binary}.@refill
291 It does not require structureof lines. It differs from from 8bit
294 In addition, if line structured data contain too long line (more than
295 998 bytes), it is regarded as binary.
298 @node cn-gb, cn-big5, binary, Glossary
299 @subsection cn-gb, gb2312
301 A MIME charset (@ref{MIME charset}) for simplified Chinese mainly used
302 in the Chinese mainland.@refill
304 It is a 8bit (@ref{8bit}) coded character set (@ref{coded character set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
305 (@ref{ASCII}) to combine GB 2312 (@ref{GB 2312}).@refill
307 It is defined in RFC 1922 (@ref{RFC 1922}).
310 @node cn-big5, CNS 11643, cn-gb, Glossary
311 @subsection cn-big5, big5
314 A MIME charset (@ref{MIME charset}) for traditional Chinese mainly used
315 in Taiwan and Hon Kong.@refill
317 It is a 8bit (@ref{8bit}) coded character set (@ref{coded character set}) not based on ISO 2022 (@ref{ISO 2022}). It is a de-fact
320 It is defined in RFC 1922 (@ref{RFC 1922}).@refill
326 Institute for Information Industry, ``Chinese Coded Character Set in
327 Computer'', March 1984.
330 It corresponds to CNS 11643 (@ref{CNS 11643}).
333 @node CNS 11643, coded character set, cn-big5, Glossary
334 @subsection CNS 11643-1992
335 @cindex CNS 11643:1992
336 @cindex CNS 11643-1992
338 Graphic character sets (@ref{graphic character set}) for Chinese mainly
339 written by traditional Chinese mainly used in Taiwan and Hong Kong. It
340 is a standard of Taiwan. Currently there are seven 94x94-character set
341 (@ref{94x94-character set}).@refill
343 Final byte of ISO 2022 (@ref{ISO 2022}) are following:
374 ``Standard Interchange Code for Generally-Used Chinese Characters'', CNS
380 @node coded character set, code extension, CNS 11643, Glossary
381 @subsection Coded character set, Character code
383 A set of unambiguous rules that establishes a character set and the
384 one-to-one relationship between the characters of the set and their
388 @node code extension, Content-Disposition, coded character set, Glossary
389 @subsection Code extension
391 The techniques for the encoding of characters that are not included in
392 the character set of a given code. (ex. ISO 2022 (@ref{ISO 2022}))
395 @node Content-Disposition, Content-Type field, code extension, Glossary
396 @subsection Content-Disposition field
400 A field to specify presentation of entity or file name. It is an
401 extension for MIME (@ref{MIME}).@refill
407 E R. Troost and S. Dorner, ``Communicating Presentation Information in
408 Internet Messages: The Content-Disposition Header'', June 1995,
414 @node Content-Type field, Emacs, Content-Disposition, Glossary
415 @subsection Content-Type field
420 Header field to represent information about body, such as media type
421 (@ref{media type}), MIME charset (@ref{MIME charset}). It is defined in
422 RFC 2045 (@ref{RFC 2045}).
428 Historically, Content-Type field was proposed in RFC 1049. In it,
429 Content-Type did not distinguish type and subtype. However MIME parser
430 may be able to accept RFC 1049 based Content-Type as unknown type.
434 Content-Type field is defined as following:
437 ``Content-Type'' ``:'' @strong{type} ``/''
438 @strong{subtype} *( ``;'' @strong{parameter} )
446 Content-Type: image/jpeg
453 Content-Type: text/plain; charset=iso-2022-jp
462 A part does not have content-type field is regarded as
466 Content-Type: text/plain; charset=us-ascii
474 And a part has unknown type/subtype is regarded as
478 Content-Type: application/octet-stream
486 @node Emacs, encoded-word, Content-Type field, Glossary
489 In this document, `Emacs' means GNU Emacs released by FSF, and `emacs'
490 means any variants of GNU Emacs.
493 @node encoded-word, encapsulation, Emacs, Glossary
494 @subsection encoded-word
496 @cindex Standards Track
499 Representation non ASCII (@ref{ASCII}) characters in header. It is
500 defined in @strong{RFC 2047}.@refill
506 K. Moore, ``MIME (Multipurpose Internet Mail Extensions) Part Three:
507 Message Header Extensions for Non-ASCII Text'', November 1996, Standards
508 Track (obsolete RFC 1521,1522,1590).
513 @node encapsulation, entity, encoded-word, Glossary
514 @subsection encapsulation
516 Method to insert whole Internet message (@ref{RFC 822}) into another
517 Internet message.@refill
519 For example, it is used to forward a message.@refill
521 (cf. @ref{message/rfc822})
525 @node entity, euc-kr, encapsulation, Glossary
528 Header fields and contents of a message or one of the parts in the body
529 of a multipart (@ref{multipart}) entity.
535 In this document, `entity' might be called ``part''.
540 @node euc-kr, FTP, entity, Glossary
542 @cindex KS C 5861:1992
545 A MIME charset (@ref{MIME charset}) for Korean.@refill
547 It is a 8bit (@ref{8bit}) coded character set (@ref{coded character set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
548 (@ref{ASCII}) to combine KS C5601 (@ref{KS C5601}).@refill
550 It is defined in RFC 1557 (@ref{RFC 1557}).@refill
556 Korea Industrial Standards Association, ``Hangul Unix Environment'', KS
562 @node FTP, GB 2312, euc-kr, Glossary
572 Postel, J. and J. Reynolds, ``File Transfer Protocol'', October 1985,
578 @node GB 2312, GB 8565.2, FTP, Glossary
579 @subsection GB 2312-1980
583 A 94x94-character set (@ref{94x94-character set}) for Chinese mainly
584 written by simplified Chinese mainly used in the Chinese mainland. It
585 is a standard of China.@refill
587 Final byte of ISO 2022 (@ref{ISO 2022}) is 04/01 (`A').
593 ``Code of Chinese Graphic Character Set for Information Interchange -
594 Primary Set'', GB 2312:1980.
599 @node GB 8565.2, graphic character set, GB 2312, Glossary
600 @subsection GB 8565.2-1988
601 @cindex GB 8565.2:1988
604 A 94x94-character set (@ref{94x94-character set}) for Chinese as
605 supplement to GB 2312 (@ref{GB 2312}). It is a standard of China.
611 ``Information Processing - Coded Character Sets for Text Communication -
612 Part 2: Graphic Characters used with Primary Set'', GB 8565.2:1988.
617 @node graphic character set, hz-gb2312, GB 8565.2, Glossary
618 @subsection Graphic Character Set
620 Coded character set (@ref{coded character set}) for graphic characters.
623 @node hz-gb2312, ISO 2022, graphic character set, Glossary
624 @subsection hz-gb2312
626 @cindex Informational
628 @cindex Informational
630 A MIME charset (@ref{MIME charset}) for simplified Chinese mainly used
631 in the Chinese mainland.@refill
633 It extends ASCII (@ref{ASCII}) to combine GB 2312 (@ref{GB 2312}), its
634 technique is like iso-2022-jp (@ref{iso-2022-jp}), but it is designed to
635 be ASCII printable to use special form for ESC sequence to designate GB
638 It is defined in RFC 1842 and 1843.
644 Y. Wei, Y. Zhang, J. Li, J. Ding and Y. Jiang, ``ASCII Printable
645 Characters-Based Chinese Character Encoding for Internet Messages'',
646 August 1995, Informational.
653 F. Lee, ``HZ - A Data Format for Exchanging Files of Arbitrarily Mixed
654 Chinese and ASCII characters'', August 1995, Informational.
659 @node ISO 2022, iso-2022-cn, hz-gb2312, Glossary
661 @cindex ISO/IEC 2022:1994
664 It is a standard for character code structure and code extension
665 (@ref{code extension}) technique.
671 International Organization for Standardization (ISO), ``Information
672 Processing: ISO 7-bit and 8-bit coded character sets: Code extension
673 techniques'', ISO/IEC 2022:1994.
678 @node iso-2022-cn, iso-2022-cn-ext, ISO 2022, Glossary
679 @subsection iso-2022-cn
681 A MIME charset (@ref{MIME charset}) for Chinese.@refill
683 It is a 7bit (@ref{7bit}) coded character set (@ref{coded character set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
684 (@ref{ASCII}) to combine GB 2312 (@ref{GB 2312}) and/or CNS 11643 plain
685 1, plain 2 (@ref{CNS 11643}).@refill
687 It is defined in RFC 1922 (@ref{RFC 1922}).
690 @node iso-2022-cn-ext, iso-2022-jp, iso-2022-cn, Glossary
691 @subsection iso-2022-cn-ext
693 A MIME charset (@ref{MIME charset}) for Chinese.@refill
695 It is a 7bit (@ref{7bit}) coded character set (@ref{coded character set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
696 (@ref{ASCII}) to combine GB 2312 (@ref{GB 2312}), CNS 11643 plain 1 .. 7
697 (@ref{CNS 11643}), ISO-IR-165 (@ref{ISO-IR-165}) and other Chinese
698 graphic character sets.@refill
700 It is defined in RFC 1922 (@ref{RFC 1922}).@refill
705 MULE 2.3 and current XEmacs/mule can not use it correctly.
707 Emacs/mule can use it.
712 @node iso-2022-jp, iso-2022-jp-2, iso-2022-cn-ext, Glossary
713 @subsection iso-2022-jp
717 A MIME charset (@ref{MIME charset}) for Japanese.@refill
719 It is a 7bit (@ref{7bit}) coded character set (@ref{coded character set}) based on old ISO 2022 (@ref{ISO 2022}). It switches ASCII
720 (@ref{ASCII}), JIS X0201-Latin, JIS X0208-1978 (@ref{JIS C6226}) and JIS
721 X0208-1983 (@ref{JIS X0208}).@refill
723 It is defined in RFC 1468.@refill
728 JIS X0208-1997? will define it in annex as non-ISO 2022 (@ref{ISO 2022})
735 [iso-2022-jp: RFC 1468]
737 Murai J., M. Crispin, and E. van der Poel, ``Japanese Character Encoding
738 for Internet Messages'', June 1993.
743 @node iso-2022-jp-2, iso-2022-kr, iso-2022-jp, Glossary
744 @subsection iso-2022-jp-2
746 @cindex Informational
747 @cindex iso-2022-jp-2
749 A MIME charset (@ref{MIME charset}), which is a multilingual extension
750 of iso-2022-jp (@ref{iso-2022-jp}).@refill
752 It is defined in RFC 1554.
756 [iso-2022-jp-2: RFC 1554]
758 Ohta M. and Handa K., ``ISO-2022-JP-2: Multilingual Extension of
759 ISO-2022-JP'', December 1993, Informational.
764 @node iso-2022-kr, ISO 646, iso-2022-jp-2, Glossary
765 @subsection iso-2022-kr
767 A MIME charset (@ref{MIME charset}) for Korean language (Hangul
770 It is based on ISO 2022 (@ref{ISO 2022}) code extension (@ref{code extension}) technique to extend ASCII (@ref{ASCII}) to use KS C5601
771 (@ref{KS C5601}) as 7bit (@ref{7bit}) text.@refill
773 It is defined in RFC 1557 (@ref{RFC 1557}).
776 @node ISO 646, ISO 8859-1, iso-2022-kr, Glossary
778 @cindex ISO/IEC 646:1991
785 International Organization for Standardization (ISO), ``Information
786 technology: ISO 7-bit coded character set for information interchange'',
792 @node ISO 8859-1, iso-8859-1, ISO 646, Glossary
793 @subsection ISO 8859-1
794 @cindex ISO 8859-1:1987
801 International Organization for Standardization (ISO), ``Information
802 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 1:
803 Latin Alphabet No.1'', ISO 8859-1:1987.
808 @node iso-8859-1, ISO 8859-2, ISO 8859-1, Glossary
809 @subsection iso-8859-1
812 @strong{iso-8859-1} is a MIME charset (@ref{MIME charset}) for
813 west-European languages written by Latin script.@refill
815 It is a 8bit (@ref{8bit}) coded character set (@ref{coded character set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
816 (@ref{ASCII}) to combine ISO 8859-1 (@ref{ISO 8859-1}).@refill
818 It is defined in RFC 2046 (@ref{RFC 2046}).
821 @node ISO 8859-2, iso-8859-2, iso-8859-1, Glossary
822 @subsection ISO 8859-2
823 @cindex ISO 8859-2:1987
830 International Organization for Standardization (ISO), ``Information
831 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 2:
832 Latin alphabet No.2'', ISO 8859-2:1987.
837 @node iso-8859-2, ISO 8859-3, ISO 8859-2, Glossary
838 @subsection iso-8859-2
841 @strong{iso-8859-2} is a MIME charset (@ref{MIME charset}) for
842 east-European languages written by Latin script.@refill
844 It is a 8bit (@ref{8bit}) coded character set (@ref{coded character set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
845 (@ref{ASCII}) to combine ISO 8859-2 (@ref{ISO 8859-2}).@refill
847 It is defined in RFC 2046 (@ref{RFC 2046}).
850 @node ISO 8859-3, ISO 8859-4, iso-8859-2, Glossary
851 @subsection ISO 8859-3
852 @cindex ISO 8859-3:1988
859 International Organization for Standardization (ISO), ``Information
860 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 3:
861 Latin alphabet No.3'', ISO 8859-3:1988.
866 @node ISO 8859-4, ISO 8859-5, ISO 8859-3, Glossary
867 @subsection ISO 8859-4
868 @cindex ISO 8859-4:1988
875 International Organization for Standardization (ISO), ``Information
876 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 4:
877 Latin alphabet No.4'', ISO 8859-4:1988.
882 @node ISO 8859-5, iso-8859-5, ISO 8859-4, Glossary
883 @subsection ISO 8859-5
884 @cindex ISO 8859-5:1988
891 International Organization for Standardization (ISO), ``Information
892 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 5:
893 Latin/Cyrillic alphabet'', ISO 8859-5:1988.
898 @node iso-8859-5, ISO 8859-6, ISO 8859-5, Glossary
899 @subsection iso-8859-5
902 @strong{iso-8859-5} is a MIME charset (@ref{MIME charset}) for Cyrillic
905 It is a 8bit (@ref{8bit}) coded character set (@ref{coded character set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
906 (@ref{ASCII}) to combine ISO 8859-5 (@ref{ISO 8859-5}).@refill
908 It is defined in RFC 2046 (@ref{RFC 2046}).
911 @node ISO 8859-6, ISO 8859-7, iso-8859-5, Glossary
912 @subsection ISO 8859-6
913 @cindex ISO 8859-6:1987
920 International Organization for Standardization (ISO), ``Information
921 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 6:
922 Latin/Arabic alphabet'', ISO 8859-6:1987.
927 @node ISO 8859-7, iso-8859-7, ISO 8859-6, Glossary
928 @subsection ISO 8859-7
929 @cindex ISO 8859-7:1987
936 International Organization for Standardization (ISO), ``Information
937 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 7:
938 Latin/Greek alphabet'', ISO 8859-7:1987.
943 @node iso-8859-7, ISO 8859-8, ISO 8859-7, Glossary
944 @subsection iso-8859-7
946 @cindex Informational
950 @strong{iso-8859-7} is a MIME charset (@ref{MIME charset}) for Greek
953 It is a 8bit (@ref{8bit}) coded character set (@ref{coded character set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
954 (@ref{ASCII}) to combine ISO 8859-7 (@ref{ISO 8859-7}).@refill
956 It is defined in RFC 1947.
960 [iso-8859-7: RFC 1947]
962 D. Spinellis, ``Greek Character Encoding for Electronic Mail Messages'',
963 May 1996, Informational.
968 @node ISO 8859-8, ISO 8859-9, iso-8859-7, Glossary
969 @subsection ISO 8859-8
970 @cindex ISO 8859-8:1988
977 International Organization for Standardization (ISO), ``Information
978 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 8:
979 Latin/Hebrew alphabet'', ISO 8859-8:1988.
984 @node ISO 8859-9, ISO-IR-165, ISO 8859-8, Glossary
985 @subsection ISO 8859-9
986 @cindex ISO 8859-9:1990
993 International Organization for Standardization (ISO), ``Information
994 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 9:
995 Latin alphabet No.5'', ISO 8859-9:1990.
1000 @node ISO-IR-165, JIS X0201, ISO 8859-9, Glossary
1001 @subsection ISO-IR-165, CCITT Extended GB
1003 A 94x94-character set (@ref{94x94-character set}) for Chinese mainly
1004 written by simplified Chinese mainly used in the Chinese mainland
1005 registered by CCITT.@refill
1007 It consists of GB 2312 (@ref{GB 2312}), GB 8565.2 (@ref{GB 8565.2}) and
1008 additional 150 characters.@refill
1010 Final byte of ISO 2022 (@ref{ISO 2022}) is 04/05 (`E').
1013 @node JIS X0201, JIS C6226, ISO-IR-165, Glossary
1014 @subsection JIS X0201
1015 @cindex JIS X 0201:1997? draft
1016 @cindex JIS X0201-1997?
1017 @cindex JIS X 0201-1976:
1018 @cindex JIS X0201-1976
1019 @cindex JIS C6220-1976
1021 It defines two 94-character set (@ref{94-character set}), for Latin
1022 script (a variant of ISO 646 (@ref{ISO 646})) and Katakana script, and
1023 7bit and 8bit coded character set (@ref{coded character set})s.@refill
1025 It was renamed from @strong{JIS C6220-1976}.
1031 Japanese Standards Association, ``Code for Information Interchange'',
1036 In addition, revised version will be published in 1997.
1042 Japanese Standards Association, ``7-bit and 8-bit coded character sets
1043 for information interchange'', JIS X 0201:1997? draft.
1048 @node JIS C6226, JIS X0208, JIS X0201, Glossary
1049 @subsection JIS C6226-1978
1051 A 94x94-character set (@ref{94x94-character set}) for Japanese. It was
1052 renamed to JIS X0208-1978.@refill
1054 (cf. @ref{JIS X0208})
1058 @node JIS X0208, JIS X0212, JIS C6226, Glossary
1059 @subsection JIS X0208
1060 @cindex JIS X 0208:1997? draft
1061 @cindex JIS X0208-1997?
1062 @cindex JIS X0208:1983,1990
1063 @cindex JIS X0208-1983,1990
1064 @cindex JIS C6226:1978
1065 @cindex JIS X0208-1978
1067 A 94x94-character set (@ref{94x94-character set}) for Japanese.
1068 Japanese standard. It was published in 1978, and revised in 1983 and
1069 1990. In the Internet message, 1983 edition is major.@refill
1071 JIS X0208 contains some symbols, numbers, primary Latin script, Hiragana
1072 script, Katakana script, Greek script, Cyrillic script, box drawing
1073 parts, Kanji (Ideographic characters used in Japanese). Notice that
1074 some symbols and box drawing parts were added in 1983 and some Kanjis
1075 were changed or swapped code points. So 1978 edition and 1983 edition
1076 are regarded as different graphic character set.@refill
1078 1990 edition added some characters, so designation of 1990 edition
1079 requires `identify revised registration' sequence, ESC 02/06 4/0 as
1080 prefix of designation sequence.
1086 Japanese Standards Association, ``Code of the Japanese graphic character
1087 set for information interchange'', JIS C6226:1978.
1092 [JIS X0208-1983,1990]
1094 Japanese Standards Association, ``Code of the Japanese graphic character
1095 set for information interchange'', JIS X0208:1983,1990.
1099 In addition, revised version will be published in 1997. (It does not
1100 change graphic character set)
1106 Japanese Standards Association, ``7-bit and 8-bit double byte coded
1107 Kanji sets for information interchange'', JIS X 0208:1997? draft.
1112 @node JIS X0212, koi8-r, JIS X0208, Glossary
1113 @subsection JIS X0212-1990
1115 A 94x94-character set (@ref{94x94-character set}) for Japanese as
1116 supplement to JIS X0208 (@ref{JIS X0208}). It is a standard of
1119 Final byte of ISO 2022 (@ref{ISO 2022}) is 04/04 (`D').
1122 @node koi8-r, KS C5601, JIS X0212, Glossary
1126 A MIME charset (@ref{MIME charset}) for Cyrillic script for Russian or
1127 other languages.@refill
1129 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
1130 de-fact standard.@refill
1132 It is defined in RFC 1489.@refill
1138 A. Chernov, ``Registration of a Cyrillic Character Set'', July 1993.
1143 @node KS C5601, media type, koi8-r, Glossary
1144 @subsection KS C5601-1987
1145 @cindex KS C 5601:1987
1148 A 94x94-character set (@ref{94x94-character set}) for Korean language
1149 (Hangul script). Korean Standard. Final byte of ISO 2022 (@ref{ISO 2022}) is 04/03 (`C').
1155 Korea Industrial Standards Association, ``Code for Information
1156 Interchange (Hangul and Hanja)'', KS C 5601:1987.
1161 @node media type, message, KS C5601, Glossary
1162 @subsection media type
1175 @strong{media type} specifies the nature of the data in the body of MIME
1176 (@ref{MIME}) entity (@ref{entity}). It consists of @strong{type} and
1177 @strong{subtype}. It is defined in RFC 2046 (@ref{RFC 2046}).@refill
1179 Currently there are following types:
1191 @strong{application}
1193 @strong{multipart} (@ref{multipart})
1199 And there are various subtypes, for example, application/octet-stream,
1200 audio/basic, image/jpeg, multipart/mixed (@ref{multipart/mixed}),
1201 text/plain (@ref{text/plain}), video/mpeg...@refill
1203 You can refer registered media types at MEDIA TYPES
1204 (ftp://ftp.isi.edu/in-notes/iana/assignments/media-types).@refill
1206 In addition, you can use private type or subtype using @strong{x-token},
1207 which as the prefix `x-'. However you can not use them in
1210 (cf. @ref{Content-Type field})
1214 @node message, message/rfc822, media type, Glossary
1217 In this document, it means mail defined in RFC 822 (@ref{RFC 822}) and
1218 news message defined in RFC 1036 (@ref{RFC 1036}).
1221 @node message/rfc822, method, message, Glossary
1222 @subsection message/rfc822
1223 @cindex message/rfc822
1225 @strong{message/rfc822} indicates that the body contains an encapsulated
1226 message, with the syntax of an RFC 822 (@ref{RFC 822}) message. It is
1227 the replacement of traditional RFC 934 (@ref{RFC 934}) encapsulation.
1228 It is defined in RFC 2046 (@ref{RFC 2046}).
1231 @node method, MIME, message/rfc822, Glossary
1233 @cindex external method
1234 @cindex internal method
1236 Application program of tm-view to process for specified media type
1237 (@ref{media type}) when user plays an entity.@refill
1239 There are two kinds of methods, @strong{internal method} and
1240 @strong{external method}. Internal method is written by Emacs Lisp.
1241 External method is written by C or script languages and called by
1242 asynchronous process call.@refill
1244 (cf. @ref{(tm-view-en)method})
1248 @node MIME, MIME charset, method, Glossary
1250 @cindex Multipurpose Internet Mail Extensions
1252 MIME stands for @strong{Multipurpose Internet Mail Extensions}, it is an
1253 extension for RFC 822 (@ref{RFC 822}).@refill
1255 According to RFC 2045:@refill
1257 STD 11, RFC 822, defines a message representation protocol specifying
1258 considerable detail about US-ASCII message headers, and leaves the
1259 message content, or message body, as flat US-ASCII text. This set of
1260 documents, collectively called the Multipurpose Internet Mail
1261 Extensions, or MIME, redefines the format of messages to allow
1266 textual message bodies in character sets other than US-ASCII,
1268 an extensible set of different formats for non-textual message
1271 multi-part message bodies, and
1273 textual header information in character sets other than US-ASCII.
1277 It is defined in RFC 2045 (@ref{RFC 2045}), RFC 2046 (@ref{RFC 2046}),
1278 RFC 2047 (@ref{encoded-word}), RFC 2048 (@ref{RFC 2048}) and RFC 2049
1282 @node MIME charset, MTA, MIME, Glossary
1283 @subsection MIME charset
1285 Coded character set (@ref{coded character set}) used in Content-Type
1286 field (@ref{Content-Type field}) or charset parameter of encoded-word
1287 (@ref{encoded-word}).@refill
1289 It is defined in RFC 2045 (@ref{RFC 2045}).@refill
1291 iso-2022-jp (@ref{iso-2022-jp}) or euc-kr (@ref{euc-kr}) are kinds of
1292 it. (In this document, MIME charsets are written by small letters to
1293 distinguish graphic character set (@ref{graphic character set}). For
1294 example, ISO 8859-1 is a graphic character set, and iso-8859-1 is a MIME
1298 @node MTA, MUA, MIME charset, Glossary
1300 @cindex Message Transfer Agent
1302 @strong{Message Transfer Agent}. It means mail transfer programs
1303 (ex. sendmail) and news servers.@refill
1309 @node MUA, MULE, MTA, Glossary
1311 @cindex Message User Agent
1313 @strong{Message User Agent}. It means mail readers and news
1320 @node MULE, multipart, MUA, Glossary
1328 Multilingual extension of GNU Emacs (@ref{Emacs}) by HANDA Ken'ichi et
1335 Nishikimi M., Handa K. and Tomura S., ``Mule: MULtilingual Enhancement
1336 to GNU Emacs'', Proc. of INET'93, August, 1993.
1339 Now, FSF and HANDA Ken'ichi et al. are working to merge MULE feature
1340 into Emacs, there is alpha version of mule merged emacs
1341 (ftp://etlport.etl.go.jp/pub/mule/mule-19.33-delta.taz).@refill
1343 In addition, there is XEmacs with mule feature.@refill
1345 So now, there are 3 kinds of mule variants.@refill
1347 In this document, @strong{mule} means any mule variants,
1348 @strong{MULE} means original MULE (..2.3),
1349 @strong{Emacs/mule} means mule merged Emacs,
1350 @strong{XEmacs/mule} means XEmacs with mule feature.
1353 @node multipart, multipart/alternative, MULE, Glossary
1354 @subsection Multipart
1357 @strong{multipart} means media type (@ref{media type}) to insert
1358 multiple entities (@ref{entity}) in a single body. Or it also indicates
1359 a message consists of multiple entities.@refill
1361 There are following subtypes registered in RFC 2046 (@ref{RFC 2046}):
1365 multipart/mixed (@ref{multipart/mixed})
1367 multipart/alternative (@ref{multipart/alternative})
1369 multipart/digest (@ref{multipart/digest})
1371 multipart/parallel (@ref{multipart/parallel})
1375 and registered in RFC 1847 (@ref{Security multipart}):
1379 multipart/signed (@ref{multipart/signed})
1381 multipart/encrypted (@ref{multipart/encrypted})
1386 @node multipart/alternative, multipart/digest, multipart, Glossary
1387 @subsection multipart/alternative
1388 @cindex multipart/digest
1390 @strong{multipart/digest} is one of multipart (@ref{multipart}) media
1391 types. This type is syntactically identical to multipart/mixed
1392 (@ref{multipart/mixed}), but the semantics are different. In
1393 particular, each of the body parts is an ``alternative'' version of the
1394 same information.@refill
1396 (cf. @ref{RFC 2046})
1400 @node multipart/digest, multipart/encrypted, multipart/alternative, Glossary
1401 @subsection multipart/digest
1402 @cindex multipart/digest
1404 @strong{multipart/digest} is one of multipart (@ref{multipart}) media
1405 types. This type is syntactically identical to multipart/mixed
1406 (@ref{multipart/mixed}), but the semantics are different. In
1407 particular, in a digest, the default Content-Type value for a body part
1408 is changed from text/plain (@ref{text/plain}) to message/rfc822
1409 (@ref{message/rfc822}).@refill
1411 This is the replacement of traditional RFC 1153 (@ref{RFC 1153}) based
1412 encapsulation (@ref{encapsulation}).@refill
1414 (cf. @ref{RFC 2046})
1418 @node multipart/encrypted, multipart/mixed, multipart/digest, Glossary
1419 @subsection multipart/encrypted
1421 It is a Security multipart (@ref{Security multipart}) defined in RFC
1422 1847, used to represent encrypted message.@refill
1424 (cf. @ref{PGP/MIME})
1428 @node multipart/mixed, multipart/parallel, multipart/encrypted, Glossary
1429 @subsection multipart/mixed
1431 Primary and default subtype of multipart (@ref{multipart}), it is used
1432 when the body parts are independent and need to be bundled in a
1433 particular order.@refill
1435 (cf. @ref{RFC 2046})
1439 @node multipart/parallel, multipart/signed, multipart/mixed, Glossary
1440 @subsection multipart/parallel
1441 @cindex multipart/parallel
1443 @strong{multipart/parallel} is a subtype of multipart (@ref{multipart}).
1444 This type is syntactically identical to multipart/mixed
1445 (@ref{multipart/mixed}), but the semantics are different. In
1446 particular, in a parallel entity, the order of body parts is not
1449 (cf. @ref{RFC 2046})
1453 @node multipart/signed, PGP, multipart/parallel, Glossary
1454 @subsection multipart/signed
1456 It is a Security multipart (@ref{Security multipart}) defined in RFC
1457 1847, used to represent signed message.@refill
1459 (cf. @ref{PGP/MIME})
1463 @node PGP, PGP-kazu, multipart/signed, Glossary
1466 @cindex Informational
1468 @cindex Pretty Good Privacy
1470 A public key encryption program by Phil Zimmermann. It provides
1471 encryption and signature for message (@ref{message}). PGP stands for
1472 @strong{Pretty Good Privacy}.@refill
1474 Traditional PGP uses RFC 934 (@ref{RFC 934}) encapsulation
1475 (@ref{encapsulation}). It is conflict with MIME (@ref{MIME}). So
1476 PGP/MIME (@ref{PGP/MIME}) is defined. On the other hand, PGP-kazu
1477 (@ref{PGP-kazu}) was proposed to use PGP encapsulation in MIME. But it
1478 is obsoleted.@refill
1484 D. Atkins, W. Stallings and P. Zimmermann, ``PGP Message Exchange
1485 Formats'', August 1996, Informational.
1491 @node PGP-kazu, PGP/MIME, PGP, Glossary
1492 @subsection PGP-kazu
1493 @cindex application/pgp
1496 In this document, @strong{PGP-kazu} means a method to use traditional
1497 PGP encapsulation in MIME (@ref{MIME}), proposed by YAMAMOTO
1500 PGP-kazu defines a media type (@ref{media type}),
1501 @strong{application/pgp}.@refill
1503 In application/pgp entity, PGP encapsulation (@ref{encapsulation}) is
1504 used. PGP encapsulation conflicts with MIME, so it requires
1505 PGP-processing to read as MIME message.@refill
1507 It was obsoleted, so you should use PGP/MIME (@ref{PGP/MIME}). However
1508 if you want to use traditional PGP message, it might be available.
1511 @node PGP/MIME, Quoted-Printable, PGP-kazu, Glossary
1512 @subsection PGP/MIME
1514 @cindex Standards Track
1517 PGP (@ref{PGP}) and MIME (@ref{MIME}) integration proposed by Michael
1520 It is based on RFC 1847 (@ref{Security multipart}), so it is harmonious
1521 with MIME, but it is not compatible with traditional PGP encapsulation.
1522 However MIME MUA can read PGP/MIME signed message even if it does not
1523 support PGP/MIME.@refill
1525 PGP/MIME (@ref{PGP/MIME}) will be standard of PGP message.
1529 [PGP/MIME: RFC 2015]
1531 M. Elkins, ``MIME Security with Pretty Good Privacy (PGP)'', October
1532 1996, Standards Track.
1537 @node Quoted-Printable, RFC 821, PGP/MIME, Glossary
1538 @subsection Quoted-Printable
1539 @cindex Quoted-Printable
1541 @strong{Quoted-Printable} is a transfer encoding method of MIME
1542 (@ref{MIME}) defined in RFC 2045 (@ref{RFC 2045}).@refill
1544 If the data being encoded are mostly US-ASCII text, the encoded form of
1545 the data remains largely recognizable by humans.@refill
1551 @node RFC 821, RFC 822, Quoted-Printable, Glossary
1561 J. Postel, ``Simple Mail Transfer Protocol'', August 1982, STD 10.
1566 @node RFC 822, RFC 934, RFC 821, Glossary
1570 @cindex Internet mail
1571 @cindex Internet message
1572 @cindex message header
1574 A RFC defines format of Internet mail message, mainly @strong{message header}.
1580 news message is based on RFC 822, so @strong{Internet message} may be
1581 more suitable than @strong{Internet mail} .
1589 D. Crocker, ``Standard for the Format of ARPA Internet Text Messages'',
1590 August 1982, STD 11.
1595 @node RFC 934, RFC 1036, RFC 822, Glossary
1598 @cindex encapsulation
1600 A RFC defines an @strong{encapsulation} (@ref{encapsulation}) method for
1601 Internet mail (@ref{RFC 822}).@refill
1603 It conflicts with MIME (@ref{MIME}), so you should use message/rfc822
1604 (@ref{message/rfc822}).
1610 Marshall T. Rose and Einar A. Stefferud, ``Proposed Standard for Message
1611 Encapsulation'', January 1985.
1616 @node RFC 1036, RFC 1153, RFC 934, Glossary
1617 @subsection RFC 1036
1621 A RFC defines format of USENET message. It is a subset of RFC 822
1622 (@ref{RFC 822}). It is not Internet standard, but a lot of netnews
1623 excepting Usenet uses it.
1629 M. Horton and R. Adams, ``Standard for Interchange of USENET Messages'',
1630 December 1987, (obsolete RFC 850).
1635 @node RFC 1153, RFC 1557, RFC 1036, Glossary
1636 @subsection RFC 1153
1643 F. Wancho, ``Digest Message Format'', April 1990.
1648 @node RFC 1557, RFC 1922, RFC 1153, Glossary
1649 @subsection RFC 1557
1651 @cindex Informational
1653 A RFC defines MIME charset (@ref{MIME charset})s for Korean, euc-kr
1654 (@ref{euc-kr}) and iso-2022-kr (@ref{iso-2022-kr}).
1660 U. Choi, K. Chon and H. Park, ``Korean Character Encoding for Internet
1661 Messages'', December 1993, Informational.
1666 @node RFC 1922, RFC 2045, RFC 1557, Glossary
1667 @subsection RFC 1922
1669 @cindex Informational
1670 @cindex charset-extension
1671 @cindex charset-edition
1673 A RFC defines MIME charset (@ref{MIME charset})s for Chinese,
1674 iso-2022-cn (@ref{iso-2022-cn}), iso-2022-cn-ext
1675 (@ref{iso-2022-cn-ext}), cn-gb (@ref{cn-gb}), cn-big5 (@ref{cn-big5}),
1678 In addition, it defines additional parameters of Content-Type field
1679 (@ref{Content-Type field}) field, @strong{charset-edition} and
1680 @strong{charset-extension}.
1686 Zhu, HF., Hu, DY., Wang, ZG., Kao, TC., Chang, WCH. and Crispin, M.,
1687 ``Chinese Character Encoding for Internet Messages'', March 1996,
1693 @node RFC 2045, RFC 2046, RFC 1922, Glossary
1694 @subsection RFC 2045
1696 @cindex Standards Track
1702 N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
1703 (MIME) Part One: Format of Internet Message Bodies'', November 1996,
1704 Standards Track (obsolete RFC 1521, 1522, 1590).
1709 @node RFC 2046, RFC 2048, RFC 2045, Glossary
1710 @subsection RFC 2046
1712 @cindex Standards Track
1718 N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
1719 (MIME) Part Two: Media Types'', November 1996, Standards Track (obsolete
1720 RFC 1521, 1522, 1590).
1725 @node RFC 2048, RFC 2049, RFC 2046, Glossary
1726 @subsection RFC 2048
1728 @cindex Standards Track
1734 N. Freed, J. Klensin and J. Postel, ``Multipurpose Internet Mail
1735 Extensions (MIME) Part Four: Registration Procedures'', November 1996,
1736 Standards Track (obsolete RFC 1521, 1522, 1590).
1741 @node RFC 2049, plain text, RFC 2048, Glossary
1742 @subsection RFC 2049
1744 @cindex Standards Track
1750 N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
1751 (MIME) Part Five: Conformance Criteria and Examples'', November 1996,
1752 Standards Track (obsolete RFC 1521, 1522, 1590).
1757 @node plain text, Security multipart, RFC 2049, Glossary
1758 @subsection plain text
1760 A textual data represented by only coded character set (@ref{coded character set}). It does not have information about font or
1761 typesetting. (cf. @ref{text/plain})
1765 @node Security multipart, text/enriched, plain text, Glossary
1766 @subsection Security multipart
1768 @cindex Standards Track
1769 @cindex Security multipart
1770 @cindex multipart/encrypted
1771 @cindex multipart/signed
1773 A format to represent signed/encrypted message in MIME
1774 (@ref{MIME}).@refill
1776 It defines two multipart media types, @strong{multipart/signed}
1777 (@ref{multipart/signed}) and @strong{multipart/encrypted}
1778 (@ref{multipart/encrypted}).@refill
1780 MOSS and PGP/MIME (@ref{PGP/MIME}) are based on it.
1784 [Security multipart: RFC 1847]
1786 James Galvin, Gale Murphy, Steve Crocker and Ned Freed, ``Security
1787 Multiparts for MIME: Multipart/Signed and Multipart/Encrypted'', October
1788 1995, Standards Track.
1793 @node text/enriched, text/plain, Security multipart, Glossary
1794 @subsection text/enriched
1796 @cindex text/enriched
1800 [text/enriched: RFC 1896]
1802 P. Resnick and A. Walker, ``The text/enriched MIME Content-type'',
1803 February 1996, (obsolete RFC 1563).
1808 @node text/plain, tm-kernel, text/enriched, Glossary
1809 @subsection text/plain
1812 @strong{text/plain} is a media type (@ref{media type}) for plain text
1813 (@ref{plain text}), defined in RFC 2046 (@ref{RFC 2046}).@refill
1815 The default media type of ``text/plain; charset=us-ascii'' for Internet
1816 mail describes existing Internet practice. That is, it is the type of
1817 body defined by RFC 822 (@ref{RFC 822}).@refill
1819 (cf. @ref{MIME charset}) (cf. @ref{us-ascii})
1823 @node tm-kernel, tm-MUA, text/plain, Glossary
1824 @subsection tm-kernel, tm
1826 A libraries to provide user interface about MIME (@ref{MIME}) for emacs.
1827 tm stands for `tools for MIME'.
1830 @strong{[Unimportant notice(^-^;]}
1835 tm may not stand for ``tiny-mime''(^-^;
1838 tm may not stand for initial of an author (^-^;
1841 ``Tools for MIME'' may be strained (^-^;
1847 @node tm-MUA, us-ascii, tm-kernel, Glossary
1854 @cindex tm oomori package
1856 MUA (@ref{MUA}) or MUA extender using tm (@ref{tm-kernel}).@refill
1858 @strong{tm oomori package} has following extenders:
1862 @strong{tm-mh-e} (@ref{(tm-mh-e-en)})
1863 for mh-e (@ref{(mh-e)})
1865 @strong{tm-gnus} (@ref{(tm-gnus_en)}) for GNUS
1867 @strong{gnus-mime} (@ref{(gnus-mime-en)}) for Gnus
1869 @strong{tm-vm} (@ref{(tm-vm_en)}) for VM
1871 @strong{tm-rmail} for RMAIL
1876 @node us-ascii, , tm-MUA, Glossary
1877 @subsection us-ascii
1881 A MIME charset (@ref{MIME charset}) for primary Latin script mainly
1882 written by English or other languages.@refill
1884 It is a 7bit coded character set (@ref{coded character set}) based on
1885 ISO 2022 (@ref{ISO 2022}), it contains only ASCII (@ref{ASCII}) and code
1886 extension (@ref{code extension}) is not allowed.@refill
1888 It is standard coded character set of Internet mail. If MIME charset is
1889 not specified, @strong{us-ascii} is used as default.@refill
1891 In addition, @strong{ASCII} of RFC 822 (@ref{RFC 822}) should be
1892 interpreted as us-ascii.
1895 @node Setting, Bug report, Introduction, Top
1898 In the tm package, two files, @file{mime-setup.el} and
1899 @file{tm-setup.el}, are provided to ease the setup.@refill
1901 The @file{mime-setup.el} is used for the whole MIME related
1902 setup including MIME encoding using @file{tm-edit.el}, while
1903 @file{tm-setup.el} is used to set up tm-MUA only.
1907 * mime-setup:: Normal setting
1908 * tm-setup:: Setting not to use tm-edit
1909 * setting for VM:: Setting for VM
1910 * manual setting:: Setting up without loading provided setup files
1913 @node mime-setup, tm-setup, Setting, Setting
1914 @section Normal setting
1917 If you want normal setting, please use @strong{mime-setup}.
1918 For example, please insert following into @file{~/.emacs}:
1925 As @file{mime-setup.el} loads @file{tm-setup.el}, you
1926 don't need to load @file{tm-setup.el} when you use
1927 @file{mime-setup.el} (Description of old version of Gnus FAQ is
1933 * Notice about GNUS:: Notices for GNUS
1936 @node signature, Notice about GNUS, mime-setup, mime-setup
1937 @subsection signature
1938 @cindex automatic signature selection tool
1940 You can set up the @strong{automatic signature selection tool} using @file{mime-setup}. If you want to
1941 automatically select the signature file depending on how the message
1942 headers show, add lines like shown below to your .emacs (Refer to the
1943 reference manual of @file{signature.el} for more details).
1946 (setq signature-file-alist
1947 '((("Newsgroups" . "jokes") . "~/.signature-jokes")
1948 (("Newsgroups" . ("zxr" "nzr")) . "~/.signature-sun")
1949 (("To" . ("ishimaru" "z-suzuki")) . "~/.signature-sun")
1950 (("To" . "tea") . "~/.signature-jokes")
1951 (("To" . ("sim" "oku" "takuo")) . "~/.signature-formal")
1957 @defvar mime-setup-use-signature
1959 If it is not @code{nil}, @file{mime-setup.el} sets up for
1960 @file{signature.el}. Its default value is @code{t}.
1965 @defvar mime-setup-signature-key-alist
1967 It defines key to bind signature inserting command for each
1968 major-mode. Its default value is following:
1971 ((mail-mode . "\C-c\C-w"))
1975 If you want to change, please rewrite it. For example:
1978 (set-alist 'mime-setup-signature-key-alist
1979 'news-reply-mode "\C-c\C-w")
1986 @defvar mime-setup-default-signature-key
1988 If key to bind signature inserting command for a major-mode is not found
1989 from @code{mime-setup-signature-key-alist}, its value is used as key.
1990 Its default value is @code{"\C-c\C-s"}.
1995 @node Notice about GNUS, , signature, mime-setup
1996 @subsection Notices for GNUS
1998 When @file{mime-setup.el} sets up for @file{signature.el}, it sets
1999 variable @code{gnus-signature-file} to @code{nil}. Therefore GNUS does
2000 not insert signature automatically when it is sending a message. Reason
2001 of this setting is following:@refill
2003 GNUS inserts signature after @file{tm-edit.el} composed as MIME message.
2004 Therefore signature inserted by GNUS is not processed as a valid MIME
2005 part. In particular, for multipart message, signature places in outside
2006 of MIME part. So MIME MUA might not display it.@refill
2008 Other notice is key bind. In historical reason, key bind to insert
2009 signature is @kbd{C-c C-s} (like mh-e (@ref{(mh-e)})) instead of
2010 @kbd{C-c C-w}. If you change to GNUS's default, please set following:
2013 (set-alist 'mime-setup-signature-key-alist 'news-reply-mode "\C-c\C-w")
2018 @node tm-setup, setting for VM, mime-setup, Setting
2019 @section Setting not to use tm-edit
2022 @strong{tm-setup} only sets up tm-MUA (@ref{tm-MUA})s. In other words,
2023 it is a setting to avoid to use tm-edit. If you don't want to compose
2024 MIME message or want to use other MIME composer, please use it instead
2025 of @file{mime-setup.el}.@refill
2027 For example, please insert following into @file{~/.emacs}:
2039 If you use @file{mime-setup.el}, you you don't need to load
2045 @node setting for VM, manual setting, tm-setup, Setting
2046 @section Setting for VM
2050 If you use @strong{vm}, please insert following in
2063 If you use @strong{BBDB}, please insert @code{(require 'tm-vm)}
2064 @strong{after} @code{(bbdb-insinuate-vm)}.
2069 @node manual setting, , setting for VM, Setting
2070 @section Setting up without loading provided setup files
2072 You may find the valuable hints in @file{mime-setup.el} or
2073 @file{tm-setup.el} if you want to set up MIME environment
2074 without loading the tm-provided setup files.
2080 Current tm provides some convenient features to expect tm-edit, and
2081 they can not use if @file{mime-setup.el} is not used. If you
2082 want to set up original setting to use tm-edit, please declare
2086 (provide 'mime-setup)
2093 @node Bug report, Acknowledgments, Setting, Top
2094 @chapter How to report bug and about mailing list of tm
2095 @cindex good bug report
2097 If you write bug-reports and/or suggestions for improvement, please
2098 send them to the tm Mailing List:
2102 Japanese <bug-tm-ja@@chamonix.jaist.ac.jp>
2104 English <bug-tm-en@@chamonix.jaist.ac.jp>
2108 Notice that, we does not welcome bug reports about too old version.
2109 Bugs in old version might be fixed. So please try latest version at
2112 You should write @strong{good bug report}. If you write only ``tm does
2113 not work'', we can not find such situations. At least, you should write
2114 name, type, variants and version of OS, emacs, tm and MUA, and setting.
2115 In addition, if error occurs, to send backtrace is very
2116 important. (cf. @ref{(emacs)Bugs}) @refill
2118 Bug may not appear only your environment, but also in a lot of
2119 environment (otherwise it might not bug). Therefor if you send mail to
2120 author directly, we must write a lot of mails. So please send mail to
2121 address for tm bugs instead of author.@refill
2123 Via the tm ML, you can report tm bugs, obtain the latest release of
2124 tm, and discuss future enhancements to tm. To join the tm ML, send
2129 Japanese <tm-ja-admin@@chamonix.jaist.ac.jp>
2131 English <tm-en-admin@@chamonix.jaist.ac.jp>
2135 Since the user registration is done manually, please write the mail
2136 body in human-recognizable language (^_^).
2139 @node Acknowledgments, Concept Index, Bug report, Top
2140 @chapter Acknowledgments
2142 I thank MASUTANI Yasuhiro. He requested me a lot of important features
2143 and gave me a lot of suggestions when tm-view was born. tm-view is
2144 based on his influence.@refill
2146 I thank ENAMI Tsugutomo for work of @file{mime.el}, which is an origin
2147 of @file{tm-ew-d.el} and @file{mel-b.el}, and permission to rewrite for
2150 I thank OKABE Yasuo for work of internal method for LaTeX and automatic
2151 assembling method for message/partial. I thank UENO Hiroshi for work of
2152 internal method for tar archive.@refill
2154 I thank UMEDA Masanobu for his work of @file{mime.el}, which is the
2155 origin of tm-edit, and permission to rewrite his work as tm-edit.@refill
2157 I thank KOBAYASHI Shuhei for his work as a tm maintainer. In addition,
2158 he often points out or suggests about conformity with RFCs.@refill
2160 I thank Oscar Figueiredo for his work as the maintainer of tm-vm. He
2161 improves tm-vm and wrote a good manual of tm-vm.@refill
2163 Last of all, I thank members of two tm mailing lists, Japanese and
2167 @node Concept Index, Variable Index, Acknowledgments, Top
2168 @chapter Concept Index
2172 @node Variable Index, , Concept Index, Top
2173 @chapter Variable Index