2 @setfilename tm-en.info
3 @settitle tm 7.100 Manual (English Version)
5 * Tm-En:: MIME package for GNU Emacs
8 @title tm 7.100 Manual (English Version)
9 @author MORIOKA Tomohiko <morioka@@jaist.ac.jp>
12 @node Top, Introduction, (dir), (dir)
13 @top tm 7.100 Manual (English Version)
17 This file documents tm, a MIME package for GNU Emacs.
21 * Introduction:: What is tm?
23 * Bug report:: How to report bug and about mailing list of tm
29 @node Introduction, Setting, Top, Top
32 The tm package is a set of modules to enjoy MIME on GNU Emacs. Using
37 playback or view the MIME messages using tm-view
39 compose MIME message using tm-edit
41 use the enhanced MIME features with mh-e, GNUS, Gnus, RMAIL and VM
47 Please read following about each topics:
51 tm-MUA for Gnus (@ref{(gnus-mime-en)})
53 tm-MUA for GNUS (@ref{(tm-gnus-en)})
55 tm-MUA for mh-e (@ref{(tm-mh-e-en)})
57 tm-MUA for VM (@ref{(tm-vm-en)})
59 mime/viewer-mode (@ref{(tm-view-en)})
61 mime/editor-mode (@ref{(tm-edit-en)})
70 @node Glossary, , Introduction, Introduction
79 * 94x94-character set::
83 * cn-gb:: cn-gb, gb2312
84 * cn-big5:: cn-big5, big5
85 * CNS 11643:: CNS 11643-1992
86 * coded character set:: Coded character set, Character code
87 * code extension:: Code extension
88 * Content-Disposition:: Content-Disposition field
89 * Content-Type field::
96 * GB 2312:: GB 2312-1980
97 * GB 8565.2:: GB 8565.2-1988
98 * graphic character set:: Graphic Character Set
120 * ISO-IR-165:: ISO-IR-165, CCITT Extended GB
122 * JIS C6226:: JIS C6226-1978
124 * JIS X0212:: JIS X0212-1990
126 * KS C5601:: KS C5601-1987
136 * multipart:: Multipart
137 * multipart/alternative::
139 * multipart/encrypted::
141 * multipart/parallel::
159 * Security multipart::
162 * tm-kernel:: tm-kernel, tm
167 @node 7bit, 8bit, Glossary, Glossary
169 @cindex 7bit (textual) string
173 @strong{7bit} means any integer between 0 .. 127.@refill
175 Any data represented by 7bit integers is called @strong{7bit data}.@refill
177 Textual string consisted of Control characters between 0 .. 31 and 127,
178 and space represented by 32, and graphic characters between 33 .. 236
179 are called @strong{7bit (textual) string}.@refill
181 Traditional Internet MTA (@ref{MTA}) can translate 7bit data, so it is
182 no need to translate by Quoted-Printable (@ref{Quoted-Printable}) or
183 Base64 (@ref{Base64}) for 7bit data.@refill
185 However if there are too long lines, it can not translate by 7bit MTA
186 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
187 ``7bit data'' has a line more than 999 bytes, it is regarded as binary
188 (@ref{binary}). For example, Postscript file should be encoded by
192 @node 8bit, 94-character set, 7bit, Glossary
194 @cindex 8bit (textual) string
198 @strong{8bit} means any integer between 0 .. 255.@refill
200 Any data represented by 8bit integers is called @strong{8bit data}.@refill
202 Textual string consisted of Control characters between 0 .. 31, 127, and
203 128 .. 159, and space represented by 32, and graphic characters between
204 33 .. 236 and 160 .. 255 are called @strong{8bit (textual) string}.@refill
206 For example, iso-8859-1 (@ref{iso-8859-1}) or euc-kr (@ref{euc-kr}) are
207 coded-character-set represented by 8bit textual string.@refill
209 Traditional Internet MTA (@ref{MTA}) can translate only 7bit
210 (@ref{7bit}) data, so if a 8bit data will be translated such MTA, it
211 must be encoded by Quoted-Printable (@ref{Quoted-Printable}) or Base64
212 (@ref{Base64}).@refill
214 However 8bit MTA are increasing today.@refill
216 However if there are too long lines, it can not translate by 8bit MTA
217 even if it is 8bit data. RFC 2045 (@ref{RFC 2045}) require lines in
218 8bit data must be less than 998 bytes. So if a ``8bit data'' has a line
219 more than 999 bytes, it is regarded as binary (@ref{binary}), so it must
220 be encoded by Base64 or Quoted-Printable.
223 @node 94-character set, 96-character set, 8bit, Glossary
224 @subsection 94-character set
225 @cindex 94-character set
227 @strong{94-character set} is a kind of 1 byte graphic character set
228 (@ref{graphic character set}), each characters are in positions 02/01
229 (33) to 07/14 (126) or 10/01 (161) to 15/14 (254). (ex. ASCII
230 (@ref{ASCII}), JIS X0201-Latin)
233 @node 96-character set, 94x94-character set, 94-character set, Glossary
234 @subsection 96-character set
235 @cindex 96-character set
237 @strong{96-character set} is a kind of 1 byte graphic character set
238 (@ref{graphic character set}), each characters are in positions 02/00
239 (32) to 07/15 (126) or 10/00 (160) to 15/15 (255). (ex. ISO 8859)
242 @node 94x94-character set, ASCII, 96-character set, Glossary
243 @subsection 94x94-character set
244 @cindex 94x94-character set
246 @strong{94x94-character set} is a kind of 2 byte graphic character set
247 (@ref{graphic character set}), each bytes are in positions 02/01 (33) to
248 07/14 (126) or 10/01 (161) to 15/14 (254). (ex. JIS X0208 (@ref{JIS X0208}), GB 2312 (@ref{GB 2312}))
251 @node ASCII, Base64, 94x94-character set, Glossary
253 @cindex ANSI X3.4:1986
257 @strong{ASCII} is a 94-character set (@ref{94-character set}) contains
258 primary latin characters (A-Z, a-z), numbers and some characters. It is
259 a standard of the United States of America. It is a variant of ISO 646
266 ``Coded Character Set -- 7-Bit American Standard Code for Information
267 Interchange'', ANSI X3.4:1986.
272 @node Base64, binary, ASCII, Glossary
277 @strong{Base64} is a transfer encoding method of MIME (@ref{MIME})
278 defined in RFC 2045 (@ref{RFC 2045}).@refill
280 The encoding process represents 24-bit groups of input bits as output
281 strings of 4 encoded characters. Encoded characters represent integer 0
282 .. 63 or @strong{pad}. Base64 data must be 4 * n bytes, so pad is used
283 to adjust size.@refill
285 These 65 characters are subset of all versions of ISO 646, including
286 US-ASCII, and all versions of EBCDIC. So it is safe even if it is
287 translated by non-Internet gateways.
290 @node binary, cn-gb, Base64, Glossary
294 Any byte stream is called @strong{binary}.@refill
296 It does not require structureof lines. It differs from from 8bit
299 In addition, if line structured data contain too long line (more than
300 998 bytes), it is regarded as binary.
303 @node cn-gb, cn-big5, binary, Glossary
304 @subsection cn-gb, gb2312
306 A MIME charset (@ref{MIME charset}) for simplified Chinese mainly used
307 in the Chinese mainland.@refill
309 It is a 8bit (@ref{8bit}) coded character set (@ref{coded character set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
310 (@ref{ASCII}) to combine GB 2312 (@ref{GB 2312}).@refill
312 It is defined in RFC 1922 (@ref{RFC 1922}).
315 @node cn-big5, CNS 11643, cn-gb, Glossary
316 @subsection cn-big5, big5
319 A MIME charset (@ref{MIME charset}) for traditional Chinese mainly used
320 in Taiwan and Hon Kong.@refill
322 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
325 It is defined in RFC 1922 (@ref{RFC 1922}).@refill
331 Institute for Information Industry, ``Chinese Coded Character Set in
332 Computer'', March 1984.
335 It corresponds to CNS 11643 (@ref{CNS 11643}).
338 @node CNS 11643, coded character set, cn-big5, Glossary
339 @subsection CNS 11643-1992
340 @cindex CNS 11643:1992
341 @cindex CNS 11643-1992
343 Graphic character sets (@ref{graphic character set}) for Chinese mainly
344 written by traditional Chinese mainly used in Taiwan and Hong Kong. It
345 is a standard of Taiwan. Currently there are seven 94x94-character set
346 (@ref{94x94-character set}).@refill
348 Final byte of ISO 2022 (@ref{ISO 2022}) are following:
379 ``Standard Interchange Code for Generally-Used Chinese Characters'', CNS
385 @node coded character set, code extension, CNS 11643, Glossary
386 @subsection Coded character set, Character code
388 A set of unambiguous rules that establishes a character set and the
389 one-to-one relationship between the characters of the set and their
393 @node code extension, Content-Disposition, coded character set, Glossary
394 @subsection Code extension
396 The techniques for the encoding of characters that are not included in
397 the character set of a given code. (ex. ISO 2022 (@ref{ISO 2022}))
400 @node Content-Disposition, Content-Type field, code extension, Glossary
401 @subsection Content-Disposition field
405 A field to specify presentation of entity or file name. It is an
406 extension for MIME (@ref{MIME}).@refill
412 E R. Troost and S. Dorner, ``Communicating Presentation Information in
413 Internet Messages: The Content-Disposition Header'', June 1995,
419 @node Content-Type field, Emacs, Content-Disposition, Glossary
420 @subsection Content-Type field
425 Header field to represent information about body, such as media type
426 (@ref{media type}), MIME charset (@ref{MIME charset}). It is defined in
427 RFC 2045 (@ref{RFC 2045}).
433 Historically, Content-Type field was proposed in RFC 1049. In it,
434 Content-Type did not distinguish type and subtype. However MIME parser
435 may be able to accept RFC 1049 based Content-Type as unknown type.
439 Content-Type field is defined as following:
442 ``Content-Type'' ``:'' @strong{type} ``/''
443 @strong{subtype} *( ``;'' @strong{parameter} )
451 Content-Type: image/jpeg
458 Content-Type: text/plain; charset=iso-2022-jp
467 A part does not have content-type field is regarded as
471 Content-Type: text/plain; charset=us-ascii
479 And a part has unknown type/subtype is regarded as
483 Content-Type: application/octet-stream
491 @node Emacs, encoded-word, Content-Type field, Glossary
494 In this document, `Emacs' means GNU Emacs released by FSF, and `emacs'
495 means any variants of GNU Emacs.
498 @node encoded-word, encapsulation, Emacs, Glossary
499 @subsection encoded-word
501 @cindex Standards Track
504 Representation non ASCII (@ref{ASCII}) characters in header. It is
505 defined in @strong{RFC 2047}.@refill
511 K. Moore, ``MIME (Multipurpose Internet Mail Extensions) Part Three:
512 Message Header Extensions for Non-ASCII Text'', November 1996, Standards
513 Track (obsolete RFC 1521,1522,1590).
518 @node encapsulation, entity, encoded-word, Glossary
519 @subsection encapsulation
521 Method to insert whole Internet message (@ref{RFC 822}) into another
522 Internet message.@refill
524 For example, it is used to forward a message.@refill
526 (cf. @ref{message/rfc822})
530 @node entity, euc-kr, encapsulation, Glossary
533 Header fields and contents of a message or one of the parts in the body
534 of a multipart (@ref{multipart}) entity.
540 In this document, `entity' might be called ``part''.
545 @node euc-kr, FTP, entity, Glossary
547 @cindex KS C 5861:1992
550 A MIME charset (@ref{MIME charset}) for Korean.@refill
552 It is a 8bit (@ref{8bit}) coded character set (@ref{coded character set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
553 (@ref{ASCII}) to combine KS C5601 (@ref{KS C5601}).@refill
555 It is defined in RFC 1557 (@ref{RFC 1557}).@refill
561 Korea Industrial Standards Association, ``Hangul Unix Environment'', KS
567 @node FTP, GB 2312, euc-kr, Glossary
577 Postel, J. and J. Reynolds, ``File Transfer Protocol'', October 1985,
583 @node GB 2312, GB 8565.2, FTP, Glossary
584 @subsection GB 2312-1980
588 A 94x94-character set (@ref{94x94-character set}) for Chinese mainly
589 written by simplified Chinese mainly used in the Chinese mainland. It
590 is a standard of China.@refill
592 Final byte of ISO 2022 (@ref{ISO 2022}) is 04/01 (`A').
598 ``Code of Chinese Graphic Character Set for Information Interchange -
599 Primary Set'', GB 2312:1980.
604 @node GB 8565.2, graphic character set, GB 2312, Glossary
605 @subsection GB 8565.2-1988
606 @cindex GB 8565.2:1988
609 A 94x94-character set (@ref{94x94-character set}) for Chinese as
610 supplement to GB 2312 (@ref{GB 2312}). It is a standard of China.
616 ``Information Processing - Coded Character Sets for Text Communication -
617 Part 2: Graphic Characters used with Primary Set'', GB 8565.2:1988.
622 @node graphic character set, hz-gb2312, GB 8565.2, Glossary
623 @subsection Graphic Character Set
625 Coded character set (@ref{coded character set}) for graphic characters.
628 @node hz-gb2312, ISO 2022, graphic character set, Glossary
629 @subsection hz-gb2312
631 @cindex Informational
633 @cindex Informational
635 A MIME charset (@ref{MIME charset}) for simplified Chinese mainly used
636 in the Chinese mainland.@refill
638 It extends ASCII (@ref{ASCII}) to combine GB 2312 (@ref{GB 2312}), its
639 technique is like iso-2022-jp (@ref{iso-2022-jp}), but it is designed to
640 be ASCII printable to use special form for ESC sequence to designate GB
643 It is defined in RFC 1842 and 1843.
649 Y. Wei, Y. Zhang, J. Li, J. Ding and Y. Jiang, ``ASCII Printable
650 Characters-Based Chinese Character Encoding for Internet Messages'',
651 August 1995, Informational.
658 F. Lee, ``HZ - A Data Format for Exchanging Files of Arbitrarily Mixed
659 Chinese and ASCII characters'', August 1995, Informational.
664 @node ISO 2022, iso-2022-cn, hz-gb2312, Glossary
666 @cindex ISO/IEC 2022:1994
669 It is a standard for character code structure and code extension
670 (@ref{code extension}) technique.
676 International Organization for Standardization (ISO), ``Information
677 Processing: ISO 7-bit and 8-bit coded character sets: Code extension
678 techniques'', ISO/IEC 2022:1994.
683 @node iso-2022-cn, iso-2022-cn-ext, ISO 2022, Glossary
684 @subsection iso-2022-cn
686 A MIME charset (@ref{MIME charset}) for Chinese.@refill
688 It is a 7bit (@ref{7bit}) coded character set (@ref{coded character set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
689 (@ref{ASCII}) to combine GB 2312 (@ref{GB 2312}) and/or CNS 11643 plain
690 1, plain 2 (@ref{CNS 11643}).@refill
692 It is defined in RFC 1922 (@ref{RFC 1922}).
695 @node iso-2022-cn-ext, iso-2022-jp, iso-2022-cn, Glossary
696 @subsection iso-2022-cn-ext
698 A MIME charset (@ref{MIME charset}) for Chinese.@refill
700 It is a 7bit (@ref{7bit}) coded character set (@ref{coded character set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
701 (@ref{ASCII}) to combine GB 2312 (@ref{GB 2312}), CNS 11643 plain 1 .. 7
702 (@ref{CNS 11643}), ISO-IR-165 (@ref{ISO-IR-165}) and other Chinese
703 graphic character sets.@refill
705 It is defined in RFC 1922 (@ref{RFC 1922}).@refill
710 MULE 2.3 and current XEmacs/mule can not use it correctly.
712 Emacs/mule can use it.
717 @node iso-2022-jp, iso-2022-jp-2, iso-2022-cn-ext, Glossary
718 @subsection iso-2022-jp
722 A MIME charset (@ref{MIME charset}) for Japanese.@refill
724 It is a 7bit (@ref{7bit}) coded character set (@ref{coded character set}) based on old ISO 2022 (@ref{ISO 2022}). It switches ASCII
725 (@ref{ASCII}), JIS X0201-Latin, JIS X0208-1978 (@ref{JIS C6226}) and JIS
726 X0208-1983 (@ref{JIS X0208}).@refill
728 It is defined in RFC 1468.@refill
733 JIS X0208-1997? will define it in annex as non-ISO 2022 (@ref{ISO 2022})
740 [iso-2022-jp: RFC 1468]
742 Murai J., M. Crispin, and E. van der Poel, ``Japanese Character Encoding
743 for Internet Messages'', June 1993.
748 @node iso-2022-jp-2, iso-2022-kr, iso-2022-jp, Glossary
749 @subsection iso-2022-jp-2
751 @cindex Informational
752 @cindex iso-2022-jp-2
754 A MIME charset (@ref{MIME charset}), which is a multilingual extension
755 of iso-2022-jp (@ref{iso-2022-jp}).@refill
757 It is defined in RFC 1554.
761 [iso-2022-jp-2: RFC 1554]
763 Ohta M. and Handa K., ``ISO-2022-JP-2: Multilingual Extension of
764 ISO-2022-JP'', December 1993, Informational.
769 @node iso-2022-kr, ISO 646, iso-2022-jp-2, Glossary
770 @subsection iso-2022-kr
772 A MIME charset (@ref{MIME charset}) for Korean language (Hangul
775 It is based on ISO 2022 (@ref{ISO 2022}) code extension (@ref{code extension}) technique to extend ASCII (@ref{ASCII}) to use KS C5601
776 (@ref{KS C5601}) as 7bit (@ref{7bit}) text.@refill
778 It is defined in RFC 1557 (@ref{RFC 1557}).
781 @node ISO 646, ISO 8859-1, iso-2022-kr, Glossary
783 @cindex ISO/IEC 646:1991
790 International Organization for Standardization (ISO), ``Information
791 technology: ISO 7-bit coded character set for information interchange'',
797 @node ISO 8859-1, iso-8859-1, ISO 646, Glossary
798 @subsection ISO 8859-1
799 @cindex ISO 8859-1:1987
806 International Organization for Standardization (ISO), ``Information
807 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 1:
808 Latin Alphabet No.1'', ISO 8859-1:1987.
813 @node iso-8859-1, ISO 8859-2, ISO 8859-1, Glossary
814 @subsection iso-8859-1
817 @strong{iso-8859-1} is a MIME charset (@ref{MIME charset}) for
818 west-European languages written by Latin script.@refill
820 It is a 8bit (@ref{8bit}) coded character set (@ref{coded character set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
821 (@ref{ASCII}) to combine ISO 8859-1 (@ref{ISO 8859-1}).@refill
823 It is defined in RFC 2046 (@ref{RFC 2046}).
826 @node ISO 8859-2, iso-8859-2, iso-8859-1, Glossary
827 @subsection ISO 8859-2
828 @cindex ISO 8859-2:1987
835 International Organization for Standardization (ISO), ``Information
836 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 2:
837 Latin alphabet No.2'', ISO 8859-2:1987.
842 @node iso-8859-2, ISO 8859-3, ISO 8859-2, Glossary
843 @subsection iso-8859-2
846 @strong{iso-8859-2} is a MIME charset (@ref{MIME charset}) for
847 east-European languages written by Latin script.@refill
849 It is a 8bit (@ref{8bit}) coded character set (@ref{coded character set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
850 (@ref{ASCII}) to combine ISO 8859-2 (@ref{ISO 8859-2}).@refill
852 It is defined in RFC 2046 (@ref{RFC 2046}).
855 @node ISO 8859-3, ISO 8859-4, iso-8859-2, Glossary
856 @subsection ISO 8859-3
857 @cindex ISO 8859-3:1988
864 International Organization for Standardization (ISO), ``Information
865 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 3:
866 Latin alphabet No.3'', ISO 8859-3:1988.
871 @node ISO 8859-4, ISO 8859-5, ISO 8859-3, Glossary
872 @subsection ISO 8859-4
873 @cindex ISO 8859-4:1988
880 International Organization for Standardization (ISO), ``Information
881 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 4:
882 Latin alphabet No.4'', ISO 8859-4:1988.
887 @node ISO 8859-5, iso-8859-5, ISO 8859-4, Glossary
888 @subsection ISO 8859-5
889 @cindex ISO 8859-5:1988
896 International Organization for Standardization (ISO), ``Information
897 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 5:
898 Latin/Cyrillic alphabet'', ISO 8859-5:1988.
903 @node iso-8859-5, ISO 8859-6, ISO 8859-5, Glossary
904 @subsection iso-8859-5
907 @strong{iso-8859-5} is a MIME charset (@ref{MIME charset}) for Cyrillic
910 It is a 8bit (@ref{8bit}) coded character set (@ref{coded character set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
911 (@ref{ASCII}) to combine ISO 8859-5 (@ref{ISO 8859-5}).@refill
913 It is defined in RFC 2046 (@ref{RFC 2046}).
916 @node ISO 8859-6, ISO 8859-7, iso-8859-5, Glossary
917 @subsection ISO 8859-6
918 @cindex ISO 8859-6:1987
925 International Organization for Standardization (ISO), ``Information
926 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 6:
927 Latin/Arabic alphabet'', ISO 8859-6:1987.
932 @node ISO 8859-7, iso-8859-7, ISO 8859-6, Glossary
933 @subsection ISO 8859-7
934 @cindex ISO 8859-7:1987
941 International Organization for Standardization (ISO), ``Information
942 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 7:
943 Latin/Greek alphabet'', ISO 8859-7:1987.
948 @node iso-8859-7, ISO 8859-8, ISO 8859-7, Glossary
949 @subsection iso-8859-7
951 @cindex Informational
955 @strong{iso-8859-7} is a MIME charset (@ref{MIME charset}) for Greek
958 It is a 8bit (@ref{8bit}) coded character set (@ref{coded character set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
959 (@ref{ASCII}) to combine ISO 8859-7 (@ref{ISO 8859-7}).@refill
961 It is defined in RFC 1947.
965 [iso-8859-7: RFC 1947]
967 D. Spinellis, ``Greek Character Encoding for Electronic Mail Messages'',
968 May 1996, Informational.
973 @node ISO 8859-8, ISO 8859-9, iso-8859-7, Glossary
974 @subsection ISO 8859-8
975 @cindex ISO 8859-8:1988
982 International Organization for Standardization (ISO), ``Information
983 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 8:
984 Latin/Hebrew alphabet'', ISO 8859-8:1988.
989 @node ISO 8859-9, ISO-IR-165, ISO 8859-8, Glossary
990 @subsection ISO 8859-9
991 @cindex ISO 8859-9:1990
998 International Organization for Standardization (ISO), ``Information
999 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 9:
1000 Latin alphabet No.5'', ISO 8859-9:1990.
1005 @node ISO-IR-165, JIS X0201, ISO 8859-9, Glossary
1006 @subsection ISO-IR-165, CCITT Extended GB
1008 A 94x94-character set (@ref{94x94-character set}) for Chinese mainly
1009 written by simplified Chinese mainly used in the Chinese mainland
1010 registered by CCITT.@refill
1012 It consists of GB 2312 (@ref{GB 2312}), GB 8565.2 (@ref{GB 8565.2}) and
1013 additional 150 characters.@refill
1015 Final byte of ISO 2022 (@ref{ISO 2022}) is 04/05 (`E').
1018 @node JIS X0201, JIS C6226, ISO-IR-165, Glossary
1019 @subsection JIS X0201
1020 @cindex JIS X 0201:1997? draft
1021 @cindex JIS X0201-1997?
1022 @cindex JIS X 0201-1976:
1023 @cindex JIS X0201-1976
1024 @cindex JIS C6220-1976
1026 It defines two 94-character set (@ref{94-character set}), for Latin
1027 script (a variant of ISO 646 (@ref{ISO 646})) and Katakana script, and
1028 7bit and 8bit coded character set (@ref{coded character set})s.@refill
1030 It was renamed from @strong{JIS C6220-1976}.
1036 Japanese Standards Association, ``Code for Information Interchange'',
1041 In addition, revised version will be published in 1997.
1047 Japanese Standards Association, ``7-bit and 8-bit coded character sets
1048 for information interchange'', JIS X 0201:1997? draft.
1053 @node JIS C6226, JIS X0208, JIS X0201, Glossary
1054 @subsection JIS C6226-1978
1056 A 94x94-character set (@ref{94x94-character set}) for Japanese. It was
1057 renamed to JIS X0208-1978.@refill
1059 (cf. @ref{JIS X0208})
1063 @node JIS X0208, JIS X0212, JIS C6226, Glossary
1064 @subsection JIS X0208
1065 @cindex JIS X 0208:1997? draft
1066 @cindex JIS X0208-1997?
1067 @cindex JIS X0208:1983,1990
1068 @cindex JIS X0208-1983,1990
1069 @cindex JIS C6226:1978
1070 @cindex JIS X0208-1978
1072 A 94x94-character set (@ref{94x94-character set}) for Japanese.
1073 Japanese standard. It was published in 1978, and revised in 1983 and
1074 1990. In the Internet message, 1983 edition is major.@refill
1076 JIS X0208 contains some symbols, numbers, primary Latin script, Hiragana
1077 script, Katakana script, Greek script, Cyrillic script, box drawing
1078 parts, Kanji (Ideographic characters used in Japanese). Notice that
1079 some symbols and box drawing parts were added in 1983 and some Kanjis
1080 were changed or swapped code points. So 1978 edition and 1983 edition
1081 are regarded as different graphic character set.@refill
1083 1990 edition added some characters, so designation of 1990 edition
1084 requires `identify revised registration' sequence, ESC 02/06 4/0 as
1085 prefix of designation sequence.
1091 Japanese Standards Association, ``Code of the Japanese graphic character
1092 set for information interchange'', JIS C6226:1978.
1097 [JIS X0208-1983,1990]
1099 Japanese Standards Association, ``Code of the Japanese graphic character
1100 set for information interchange'', JIS X0208:1983,1990.
1104 In addition, revised version will be published in 1997. (It does not
1105 change graphic character set)
1111 Japanese Standards Association, ``7-bit and 8-bit double byte coded
1112 Kanji sets for information interchange'', JIS X 0208:1997? draft.
1117 @node JIS X0212, koi8-r, JIS X0208, Glossary
1118 @subsection JIS X0212-1990
1120 A 94x94-character set (@ref{94x94-character set}) for Japanese as
1121 supplement to JIS X0208 (@ref{JIS X0208}). It is a standard of
1124 Final byte of ISO 2022 (@ref{ISO 2022}) is 04/04 (`D').
1127 @node koi8-r, KS C5601, JIS X0212, Glossary
1131 A MIME charset (@ref{MIME charset}) for Cyrillic script for Russian or
1132 other languages.@refill
1134 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
1135 de-fact standard.@refill
1137 It is defined in RFC 1489.@refill
1143 A. Chernov, ``Registration of a Cyrillic Character Set'', July 1993.
1148 @node KS C5601, media type, koi8-r, Glossary
1149 @subsection KS C5601-1987
1150 @cindex KS C 5601:1987
1153 A 94x94-character set (@ref{94x94-character set}) for Korean language
1154 (Hangul script). Korean Standard. Final byte of ISO 2022 (@ref{ISO 2022}) is 04/03 (`C').
1160 Korea Industrial Standards Association, ``Code for Information
1161 Interchange (Hangul and Hanja)'', KS C 5601:1987.
1166 @node media type, message, KS C5601, Glossary
1167 @subsection media type
1180 @strong{media type} specifies the nature of the data in the body of MIME
1181 (@ref{MIME}) entity (@ref{entity}). It consists of @strong{type} and
1182 @strong{subtype}. It is defined in RFC 2046 (@ref{RFC 2046}).@refill
1184 Currently there are following types:
1196 @strong{application}
1198 @strong{multipart} (@ref{multipart})
1204 And there are various subtypes, for example, application/octet-stream,
1205 audio/basic, image/jpeg, multipart/mixed (@ref{multipart/mixed}),
1206 text/plain (@ref{text/plain}), video/mpeg...@refill
1208 You can refer registered media types at MEDIA TYPES
1209 (ftp://ftp.isi.edu/in-notes/iana/assignments/media-types).@refill
1211 In addition, you can use private type or subtype using @strong{x-token},
1212 which as the prefix `x-'. However you can not use them in
1215 (cf. @ref{Content-Type field})
1219 @node message, message/rfc822, media type, Glossary
1222 In this document, it means mail defined in RFC 822 (@ref{RFC 822}) and
1223 news message defined in RFC 1036 (@ref{RFC 1036}).
1226 @node message/rfc822, method, message, Glossary
1227 @subsection message/rfc822
1228 @cindex message/rfc822
1230 @strong{message/rfc822} indicates that the body contains an encapsulated
1231 message, with the syntax of an RFC 822 (@ref{RFC 822}) message. It is
1232 the replacement of traditional RFC 934 (@ref{RFC 934}) encapsulation.
1233 It is defined in RFC 2046 (@ref{RFC 2046}).
1236 @node method, MIME, message/rfc822, Glossary
1238 @cindex external method
1239 @cindex internal method
1241 Application program of tm-view to process for specified media type
1242 (@ref{media type}) when user plays an entity.@refill
1244 There are two kinds of methods, @strong{internal method} and
1245 @strong{external method}. Internal method is written by Emacs Lisp.
1246 External method is written by C or script languages and called by
1247 asynchronous process call.@refill
1249 (cf. @ref{(tm-view-en)method})
1253 @node MIME, MIME charset, method, Glossary
1255 @cindex Multipurpose Internet Mail Extensions
1257 MIME stands for @strong{Multipurpose Internet Mail Extensions}, it is an
1258 extension for RFC 822 (@ref{RFC 822}).@refill
1260 According to RFC 2045:@refill
1262 STD 11, RFC 822, defines a message representation protocol specifying
1263 considerable detail about US-ASCII message headers, and leaves the
1264 message content, or message body, as flat US-ASCII text. This set of
1265 documents, collectively called the Multipurpose Internet Mail
1266 Extensions, or MIME, redefines the format of messages to allow
1271 textual message bodies in character sets other than US-ASCII,
1273 an extensible set of different formats for non-textual message
1276 multi-part message bodies, and
1278 textual header information in character sets other than US-ASCII.
1282 It is defined in RFC 2045 (@ref{RFC 2045}), RFC 2046 (@ref{RFC 2046}),
1283 RFC 2047 (@ref{encoded-word}), RFC 2048 (@ref{RFC 2048}) and RFC 2049
1287 @node MIME charset, MTA, MIME, Glossary
1288 @subsection MIME charset
1290 Coded character set (@ref{coded character set}) used in Content-Type
1291 field (@ref{Content-Type field}) or charset parameter of encoded-word
1292 (@ref{encoded-word}).@refill
1294 It is defined in RFC 2045 (@ref{RFC 2045}).@refill
1296 iso-2022-jp (@ref{iso-2022-jp}) or euc-kr (@ref{euc-kr}) are kinds of
1297 it. (In this document, MIME charsets are written by small letters to
1298 distinguish graphic character set (@ref{graphic character set}). For
1299 example, ISO 8859-1 is a graphic character set, and iso-8859-1 is a MIME
1303 @node MTA, MUA, MIME charset, Glossary
1305 @cindex Message Transfer Agent
1307 @strong{Message Transfer Agent}. It means mail transfer programs
1308 (ex. sendmail) and news servers.@refill
1314 @node MUA, MULE, MTA, Glossary
1316 @cindex Message User Agent
1318 @strong{Message User Agent}. It means mail readers and news
1325 @node MULE, multipart, MUA, Glossary
1333 Multilingual extension of GNU Emacs (@ref{Emacs}) by HANDA Ken'ichi et
1340 Nishikimi M., Handa K. and Tomura S., ``Mule: MULtilingual Enhancement
1341 to GNU Emacs'', Proc. of INET'93, August, 1993.
1344 Now, FSF and HANDA Ken'ichi et al. are working to merge MULE feature
1345 into Emacs, there is alpha version of mule merged emacs
1346 (ftp://etlport.etl.go.jp/pub/mule/mule-19.33-delta.taz).@refill
1348 In addition, there is XEmacs with mule feature.@refill
1350 So now, there are 3 kinds of mule variants.@refill
1352 In this document, @strong{mule} means any mule variants,
1353 @strong{MULE} means original MULE (..2.3),
1354 @strong{Emacs/mule} means mule merged Emacs,
1355 @strong{XEmacs/mule} means XEmacs with mule feature.
1358 @node multipart, multipart/alternative, MULE, Glossary
1359 @subsection Multipart
1362 @strong{multipart} means media type (@ref{media type}) to insert
1363 multiple entities (@ref{entity}) in a single body. Or it also indicates
1364 a message consists of multiple entities.@refill
1366 There are following subtypes registered in RFC 2046 (@ref{RFC 2046}):
1370 multipart/mixed (@ref{multipart/mixed})
1372 multipart/alternative (@ref{multipart/alternative})
1374 multipart/digest (@ref{multipart/digest})
1376 multipart/parallel (@ref{multipart/parallel})
1380 and registered in RFC 1847 (@ref{Security multipart}):
1384 multipart/signed (@ref{multipart/signed})
1386 multipart/encrypted (@ref{multipart/encrypted})
1391 @node multipart/alternative, multipart/digest, multipart, Glossary
1392 @subsection multipart/alternative
1393 @cindex multipart/digest
1395 @strong{multipart/digest} is one of multipart (@ref{multipart}) media
1396 types. This type is syntactically identical to multipart/mixed
1397 (@ref{multipart/mixed}), but the semantics are different. In
1398 particular, each of the body parts is an ``alternative'' version of the
1399 same information.@refill
1401 (cf. @ref{RFC 2046})
1405 @node multipart/digest, multipart/encrypted, multipart/alternative, Glossary
1406 @subsection multipart/digest
1407 @cindex multipart/digest
1409 @strong{multipart/digest} is one of multipart (@ref{multipart}) media
1410 types. This type is syntactically identical to multipart/mixed
1411 (@ref{multipart/mixed}), but the semantics are different. In
1412 particular, in a digest, the default Content-Type value for a body part
1413 is changed from text/plain (@ref{text/plain}) to message/rfc822
1414 (@ref{message/rfc822}).@refill
1416 This is the replacement of traditional RFC 1153 (@ref{RFC 1153}) based
1417 encapsulation (@ref{encapsulation}).@refill
1419 (cf. @ref{RFC 2046})
1423 @node multipart/encrypted, multipart/mixed, multipart/digest, Glossary
1424 @subsection multipart/encrypted
1426 It is a Security multipart (@ref{Security multipart}) defined in RFC
1427 1847, used to represent encrypted message.@refill
1429 (cf. @ref{PGP/MIME})
1433 @node multipart/mixed, multipart/parallel, multipart/encrypted, Glossary
1434 @subsection multipart/mixed
1436 Primary and default subtype of multipart (@ref{multipart}), it is used
1437 when the body parts are independent and need to be bundled in a
1438 particular order.@refill
1440 (cf. @ref{RFC 2046})
1444 @node multipart/parallel, multipart/signed, multipart/mixed, Glossary
1445 @subsection multipart/parallel
1446 @cindex multipart/parallel
1448 @strong{multipart/parallel} is a subtype of multipart (@ref{multipart}).
1449 This type is syntactically identical to multipart/mixed
1450 (@ref{multipart/mixed}), but the semantics are different. In
1451 particular, in a parallel entity, the order of body parts is not
1454 (cf. @ref{RFC 2046})
1458 @node multipart/signed, PGP, multipart/parallel, Glossary
1459 @subsection multipart/signed
1461 It is a Security multipart (@ref{Security multipart}) defined in RFC
1462 1847, used to represent signed message.@refill
1464 (cf. @ref{PGP/MIME})
1468 @node PGP, PGP-kazu, multipart/signed, Glossary
1471 @cindex Informational
1473 @cindex Pretty Good Privacy
1475 A public key encryption program by Phil Zimmermann. It provides
1476 encryption and signature for message (@ref{message}). PGP stands for
1477 @strong{Pretty Good Privacy}.@refill
1479 Traditional PGP uses RFC 934 (@ref{RFC 934}) encapsulation
1480 (@ref{encapsulation}). It is conflict with MIME (@ref{MIME}). So
1481 PGP/MIME (@ref{PGP/MIME}) is defined. On the other hand, PGP-kazu
1482 (@ref{PGP-kazu}) was proposed to use PGP encapsulation in MIME. But it
1483 is obsoleted.@refill
1489 D. Atkins, W. Stallings and P. Zimmermann, ``PGP Message Exchange
1490 Formats'', August 1996, Informational.
1496 @node PGP-kazu, PGP/MIME, PGP, Glossary
1497 @subsection PGP-kazu
1498 @cindex application/pgp
1501 In this document, @strong{PGP-kazu} means a method to use traditional
1502 PGP encapsulation in MIME (@ref{MIME}), proposed by YAMAMOTO
1505 PGP-kazu defines a media type (@ref{media type}),
1506 @strong{application/pgp}.@refill
1508 In application/pgp entity, PGP encapsulation (@ref{encapsulation}) is
1509 used. PGP encapsulation conflicts with MIME, so it requires
1510 PGP-processing to read as MIME message.@refill
1512 It was obsoleted, so you should use PGP/MIME (@ref{PGP/MIME}). However
1513 if you want to use traditional PGP message, it might be available.
1516 @node PGP/MIME, Quoted-Printable, PGP-kazu, Glossary
1517 @subsection PGP/MIME
1519 @cindex Standards Track
1522 PGP (@ref{PGP}) and MIME (@ref{MIME}) integration proposed by Michael
1525 It is based on RFC 1847 (@ref{Security multipart}), so it is harmonious
1526 with MIME, but it is not compatible with traditional PGP encapsulation.
1527 However MIME MUA can read PGP/MIME signed message even if it does not
1528 support PGP/MIME.@refill
1530 PGP/MIME (@ref{PGP/MIME}) will be standard of PGP message.
1534 [PGP/MIME: RFC 2015]
1536 M. Elkins, ``MIME Security with Pretty Good Privacy (PGP)'', October
1537 1996, Standards Track.
1542 @node Quoted-Printable, RFC 821, PGP/MIME, Glossary
1543 @subsection Quoted-Printable
1544 @cindex Quoted-Printable
1546 @strong{Quoted-Printable} is a transfer encoding method of MIME
1547 (@ref{MIME}) defined in RFC 2045 (@ref{RFC 2045}).@refill
1549 If the data being encoded are mostly US-ASCII text, the encoded form of
1550 the data remains largely recognizable by humans.@refill
1556 @node RFC 821, RFC 822, Quoted-Printable, Glossary
1566 J. Postel, ``Simple Mail Transfer Protocol'', August 1982, STD 10.
1571 @node RFC 822, RFC 934, RFC 821, Glossary
1575 @cindex Internet mail
1576 @cindex Internet message
1577 @cindex message header
1579 A RFC defines format of Internet mail message, mainly @strong{message header}.
1585 news message is based on RFC 822, so @strong{Internet message} may be
1586 more suitable than @strong{Internet mail} .
1594 D. Crocker, ``Standard for the Format of ARPA Internet Text Messages'',
1595 August 1982, STD 11.
1600 @node RFC 934, RFC 1036, RFC 822, Glossary
1603 @cindex encapsulation
1605 A RFC defines an @strong{encapsulation} (@ref{encapsulation}) method for
1606 Internet mail (@ref{RFC 822}).@refill
1608 It conflicts with MIME (@ref{MIME}), so you should use message/rfc822
1609 (@ref{message/rfc822}).
1615 Marshall T. Rose and Einar A. Stefferud, ``Proposed Standard for Message
1616 Encapsulation'', January 1985.
1621 @node RFC 1036, RFC 1153, RFC 934, Glossary
1622 @subsection RFC 1036
1626 A RFC defines format of USENET message. It is a subset of RFC 822
1627 (@ref{RFC 822}). It is not Internet standard, but a lot of netnews
1628 excepting Usenet uses it.
1634 M. Horton and R. Adams, ``Standard for Interchange of USENET Messages'',
1635 December 1987, (obsolete RFC 850).
1640 @node RFC 1153, RFC 1557, RFC 1036, Glossary
1641 @subsection RFC 1153
1648 F. Wancho, ``Digest Message Format'', April 1990.
1653 @node RFC 1557, RFC 1922, RFC 1153, Glossary
1654 @subsection RFC 1557
1656 @cindex Informational
1658 A RFC defines MIME charset (@ref{MIME charset})s for Korean, euc-kr
1659 (@ref{euc-kr}) and iso-2022-kr (@ref{iso-2022-kr}).
1665 U. Choi, K. Chon and H. Park, ``Korean Character Encoding for Internet
1666 Messages'', December 1993, Informational.
1671 @node RFC 1922, RFC 2045, RFC 1557, Glossary
1672 @subsection RFC 1922
1674 @cindex Informational
1675 @cindex charset-extension
1676 @cindex charset-edition
1678 A RFC defines MIME charset (@ref{MIME charset})s for Chinese,
1679 iso-2022-cn (@ref{iso-2022-cn}), iso-2022-cn-ext
1680 (@ref{iso-2022-cn-ext}), cn-gb (@ref{cn-gb}), cn-big5 (@ref{cn-big5}),
1683 In addition, it defines additional parameters of Content-Type field
1684 (@ref{Content-Type field}) field, @strong{charset-edition} and
1685 @strong{charset-extension}.
1691 Zhu, HF., Hu, DY., Wang, ZG., Kao, TC., Chang, WCH. and Crispin, M.,
1692 ``Chinese Character Encoding for Internet Messages'', March 1996,
1698 @node RFC 2045, RFC 2046, RFC 1922, Glossary
1699 @subsection RFC 2045
1701 @cindex Standards Track
1707 N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
1708 (MIME) Part One: Format of Internet Message Bodies'', November 1996,
1709 Standards Track (obsolete RFC 1521, 1522, 1590).
1714 @node RFC 2046, RFC 2048, RFC 2045, Glossary
1715 @subsection RFC 2046
1717 @cindex Standards Track
1723 N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
1724 (MIME) Part Two: Media Types'', November 1996, Standards Track (obsolete
1725 RFC 1521, 1522, 1590).
1730 @node RFC 2048, RFC 2049, RFC 2046, Glossary
1731 @subsection RFC 2048
1733 @cindex Standards Track
1739 N. Freed, J. Klensin and J. Postel, ``Multipurpose Internet Mail
1740 Extensions (MIME) Part Four: Registration Procedures'', November 1996,
1741 Standards Track (obsolete RFC 1521, 1522, 1590).
1746 @node RFC 2049, plain text, RFC 2048, Glossary
1747 @subsection RFC 2049
1749 @cindex Standards Track
1755 N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
1756 (MIME) Part Five: Conformance Criteria and Examples'', November 1996,
1757 Standards Track (obsolete RFC 1521, 1522, 1590).
1762 @node plain text, Security multipart, RFC 2049, Glossary
1763 @subsection plain text
1765 A textual data represented by only coded character set (@ref{coded character set}). It does not have information about font or
1766 typesetting. (cf. @ref{text/plain})
1770 @node Security multipart, text/enriched, plain text, Glossary
1771 @subsection Security multipart
1773 @cindex Standards Track
1774 @cindex Security multipart
1775 @cindex multipart/encrypted
1776 @cindex multipart/signed
1778 A format to represent signed/encrypted message in MIME
1779 (@ref{MIME}).@refill
1781 It defines two multipart media types, @strong{multipart/signed}
1782 (@ref{multipart/signed}) and @strong{multipart/encrypted}
1783 (@ref{multipart/encrypted}).@refill
1785 MOSS and PGP/MIME (@ref{PGP/MIME}) are based on it.
1789 [Security multipart: RFC 1847]
1791 James Galvin, Gale Murphy, Steve Crocker and Ned Freed, ``Security
1792 Multiparts for MIME: Multipart/Signed and Multipart/Encrypted'', October
1793 1995, Standards Track.
1798 @node text/enriched, text/plain, Security multipart, Glossary
1799 @subsection text/enriched
1801 @cindex text/enriched
1805 [text/enriched: RFC 1896]
1807 P. Resnick and A. Walker, ``The text/enriched MIME Content-type'',
1808 February 1996, (obsolete RFC 1563).
1813 @node text/plain, tm-kernel, text/enriched, Glossary
1814 @subsection text/plain
1817 @strong{text/plain} is a media type (@ref{media type}) for plain text
1818 (@ref{plain text}), defined in RFC 2046 (@ref{RFC 2046}).@refill
1820 The default media type of ``text/plain; charset=us-ascii'' for Internet
1821 mail describes existing Internet practice. That is, it is the type of
1822 body defined by RFC 822 (@ref{RFC 822}).@refill
1824 (cf. @ref{MIME charset}) (cf. @ref{us-ascii})
1828 @node tm-kernel, tm-MUA, text/plain, Glossary
1829 @subsection tm-kernel, tm
1831 A libraries to provide user interface about MIME (@ref{MIME}) for emacs.
1832 tm stands for `tools for MIME'.
1835 @strong{[Unimportant notice(^-^;]}
1840 tm may not stand for ``tiny-mime''(^-^;
1843 tm may not stand for initial of an author (^-^;
1846 ``Tools for MIME'' may be strained (^-^;
1852 @node tm-MUA, us-ascii, tm-kernel, Glossary
1859 @cindex tm oomori package
1861 MUA (@ref{MUA}) or MUA extender using tm (@ref{tm-kernel}).@refill
1863 @strong{tm oomori package} has following extenders:
1867 @strong{tm-mh-e} (@ref{(tm-mh-e-en)})
1868 for mh-e (@ref{(mh-e)})
1870 @strong{tm-gnus} (@ref{(tm-gnus_en)}) for GNUS
1872 @strong{gnus-mime} (@ref{(gnus-mime-en)}) for Gnus
1874 @strong{tm-vm} (@ref{(tm-vm-en)}) for VM
1876 @strong{tm-rmail} for RMAIL
1881 @node us-ascii, , tm-MUA, Glossary
1882 @subsection us-ascii
1886 A MIME charset (@ref{MIME charset}) for primary Latin script mainly
1887 written by English or other languages.@refill
1889 It is a 7bit coded character set (@ref{coded character set}) based on
1890 ISO 2022 (@ref{ISO 2022}), it contains only ASCII (@ref{ASCII}) and code
1891 extension (@ref{code extension}) is not allowed.@refill
1893 It is standard coded character set of Internet mail. If MIME charset is
1894 not specified, @strong{us-ascii} is used as default.@refill
1896 In addition, @strong{ASCII} of RFC 822 (@ref{RFC 822}) should be
1897 interpreted as us-ascii.
1900 @node Setting, Bug report, Introduction, Top
1903 In the tm package, two files, @file{mime-setup.el} and
1904 @file{tm-setup.el}, are provided to ease the setup.@refill
1906 The @file{mime-setup.el} is used for the whole MIME related
1907 setup including MIME encoding using @file{tm-edit.el}, while
1908 @file{tm-setup.el} is used to set up tm-MUA only.
1912 * mime-setup:: Normal setting
1913 * tm-setup:: Setting not to use tm-edit
1914 * setting for VM:: Setting for VM
1915 * manual setting:: Setting up without loading provided setup files
1918 @node mime-setup, tm-setup, Setting, Setting
1919 @section Normal setting
1922 If you want normal setting, please use @strong{mime-setup}.
1923 For example, please insert following into @file{~/.emacs}:
1930 As @file{mime-setup.el} loads @file{tm-setup.el}, you
1931 don't need to load @file{tm-setup.el} when you use
1932 @file{mime-setup.el} (Description of old version of Gnus FAQ is
1938 * Notice about GNUS:: Notices for GNUS
1941 @node signature, Notice about GNUS, mime-setup, mime-setup
1942 @subsection signature
1943 @cindex automatic signature selection tool
1945 You can set up the @strong{automatic signature selection tool} using @file{mime-setup}. If you want to
1946 automatically select the signature file depending on how the message
1947 headers show, add lines like shown below to your .emacs (Refer to the
1948 reference manual of @file{signature.el} for more details).
1951 (setq signature-file-alist
1952 '((("Newsgroups" . "jokes") . "~/.signature-jokes")
1953 (("Newsgroups" . ("zxr" "nzr")) . "~/.signature-sun")
1954 (("To" . ("ishimaru" "z-suzuki")) . "~/.signature-sun")
1955 (("To" . "tea") . "~/.signature-jokes")
1956 (("To" . ("sim" "oku" "takuo")) . "~/.signature-formal")
1962 @defvar mime-setup-use-signature
1964 If it is not @code{nil}, @file{mime-setup.el} sets up for
1965 @file{signature.el}. Its default value is @code{t}.
1970 @defvar mime-setup-signature-key-alist
1972 It defines key to bind signature inserting command for each
1973 major-mode. Its default value is following:
1976 ((mail-mode . "\C-c\C-w"))
1980 If you want to change, please rewrite it. For example:
1983 (set-alist 'mime-setup-signature-key-alist
1984 'news-reply-mode "\C-c\C-w")
1991 @defvar mime-setup-default-signature-key
1993 If key to bind signature inserting command for a major-mode is not found
1994 from @code{mime-setup-signature-key-alist}, its value is used as key.
1995 Its default value is @code{"\C-c\C-s"}.
2000 @node Notice about GNUS, , signature, mime-setup
2001 @subsection Notices for GNUS
2003 When @file{mime-setup.el} sets up for @file{signature.el}, it sets
2004 variable @code{gnus-signature-file} to @code{nil}. Therefore GNUS does
2005 not insert signature automatically when it is sending a message. Reason
2006 of this setting is following:@refill
2008 GNUS inserts signature after @file{tm-edit.el} composed as MIME message.
2009 Therefore signature inserted by GNUS is not processed as a valid MIME
2010 part. In particular, for multipart message, signature places in outside
2011 of MIME part. So MIME MUA might not display it.@refill
2013 Other notice is key bind. In historical reason, key bind to insert
2014 signature is @kbd{C-c C-s} (like mh-e (@ref{(mh-e)})) instead of
2015 @kbd{C-c C-w}. If you change to GNUS's default, please set following:
2018 (set-alist 'mime-setup-signature-key-alist 'news-reply-mode "\C-c\C-w")
2023 @node tm-setup, setting for VM, mime-setup, Setting
2024 @section Setting not to use tm-edit
2027 @strong{tm-setup} only sets up tm-MUA (@ref{tm-MUA})s. In other words,
2028 it is a setting to avoid to use tm-edit. If you don't want to compose
2029 MIME message or want to use other MIME composer, please use it instead
2030 of @file{mime-setup.el}.@refill
2032 For example, please insert following into @file{~/.emacs}:
2044 If you use @file{mime-setup.el}, you don't need to load
2050 @node setting for VM, manual setting, tm-setup, Setting
2051 @section Setting for VM
2055 If you use @strong{vm}, please insert following in
2068 If you use @strong{BBDB}, please insert @code{(require 'tm-vm)}
2069 @strong{after} @code{(bbdb-insinuate-vm)}.
2074 @node manual setting, , setting for VM, Setting
2075 @section Setting up without loading provided setup files
2077 You may find the valuable hints in @file{mime-setup.el} or
2078 @file{tm-setup.el} if you want to set up MIME environment
2079 without loading the tm-provided setup files.
2085 Current tm provides some convenient features to expect tm-edit, and
2086 they can not use if @file{mime-setup.el} is not used. If you
2087 want to set up original setting to use tm-edit, please declare
2091 (provide 'mime-setup)
2098 @node Bug report, Acknowledgments, Setting, Top
2099 @chapter How to report bug and about mailing list of tm
2100 @cindex good bug report
2102 If you write bug-reports and/or suggestions for improvement, please
2103 send them to the tm Mailing List:
2107 Japanese <bug-tm-ja@@chamonix.jaist.ac.jp>
2109 English <bug-tm-en@@chamonix.jaist.ac.jp>
2113 Notice that, we does not welcome bug reports about too old version.
2114 Bugs in old version might be fixed. So please try latest version at
2117 You should write @strong{good bug report}. If you write only ``tm does
2118 not work'', we can not find such situations. At least, you should write
2119 name, type, variants and version of OS, emacs, tm and MUA, and setting.
2120 In addition, if error occurs, to send backtrace is very
2121 important. (cf. @ref{(emacs)Bugs}) @refill
2123 Bug may not appear only your environment, but also in a lot of
2124 environment (otherwise it might not bug). Therefor if you send mail to
2125 author directly, we must write a lot of mails. So please send mail to
2126 address for tm bugs instead of author.@refill
2128 Via the tm ML, you can report tm bugs, obtain the latest release of
2129 tm, and discuss future enhancements to tm. To join the tm ML, send
2134 Japanese <tm-ja-admin@@chamonix.jaist.ac.jp>
2136 English <tm-en-admin@@chamonix.jaist.ac.jp>
2140 Since the user registration is done manually, please write the mail
2141 body in human-recognizable language (^_^).
2144 @node Acknowledgments, Concept Index, Bug report, Top
2145 @chapter Acknowledgments
2147 I thank MASUTANI Yasuhiro. He requested me a lot of important features
2148 and gave me a lot of suggestions when tm-view was born. tm-view is
2149 based on his influence.@refill
2151 I thank ENAMI Tsugutomo for work of @file{mime.el}, which is an origin
2152 of @file{tm-ew-d.el} and @file{mel-b.el}, and permission to rewrite for
2155 I thank OKABE Yasuo for work of internal method for LaTeX and automatic
2156 assembling method for message/partial. I thank UENO Hiroshi for work of
2157 internal method for tar archive.@refill
2159 I thank UMEDA Masanobu for his work of @file{mime.el}, which is the
2160 origin of tm-edit, and permission to rewrite his work as tm-edit.@refill
2162 I thank KOBAYASHI Shuhei for his work as a tm maintainer. In addition,
2163 he often points out or suggests about conformity with RFCs.@refill
2165 I thank Oscar Figueiredo for his work as the maintainer of tm-vm. He
2166 improves tm-vm and wrote a good manual of tm-vm.@refill
2168 Last of all, I thank members of two tm mailing lists, Japanese and
2172 @node Concept Index, Variable Index, Acknowledgments, Top
2173 @chapter Concept Index
2177 @node Variable Index, , Concept Index, Top
2178 @chapter Variable Index