1 Info file: tm-en.info, -*-Text-*-
2 produced by `texinfo-format-buffer'
4 using `texinfmt.el' version 2.32 of 19 November 1993.
8 File: tm-en.info, Node: Top, Next: Introduction, Prev: (dir), Up: (dir)
10 tm 7.98 Manual (English Version)
11 ********************************
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 File: tm-en.info, Node: Introduction, Next: Setting, Prev: Top, Up: Top
31 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
35 * compose MIME message using tm-edit
36 * use the enhanced MIME features with mh-e, GNUS, Gnus, RMAIL and VM
40 Please read following about each topics:
42 * tm-MUA for Gnus (*Note (gnus-mime-en)::)
43 * tm-MUA for GNUS (*Note (tm-gnus-en)::)
44 * tm-MUA for mh-e (*Note (tm-mh-e-en)::)
45 * mime/viewer-mode (*Note (tm-view-en)::)
46 * mime/editor-mode (*Note (tm-edit-en)::)
56 File: tm-en.info, Node: Glossary, Prev: Introduction, Up: Introduction
68 * 94x94-character set::
72 * cn-gb:: cn-gb, gb2312
73 * cn-big5:: cn-big5, big5
74 * CNS 11643:: CNS 11643-1992
75 * coded character set:: Coded character set, Character code
76 * code extension:: Code extension
77 * Content-Disposition:: Content-Disposition field
78 * Content-Type field::
84 * GB 2312:: GB 2312-1980
85 * GB 8565.2:: GB 8565.2-1988
86 * graphic character set:: Graphic Character Set
108 * ISO-IR-165:: ISO-IR-165, CCITT Extended GB
110 * JIS C6226:: JIS C6226-1978
112 * JIS X0212:: JIS X0212-1990
114 * KS C5601:: KS C5601-1987
124 * multipart:: Multipart
125 * multipart/alternative::
127 * multipart/encrypted::
129 * multipart/parallel::
147 * Security multipart::
150 * tm-kernel:: tm-kernel, tm
156 File: tm-en.info, Node: 7bit, Next: 8bit, Prev: Glossary, Up: Glossary
161 *7bit* means any integer between 0 .. 127.
163 Any data represented by 7bit integers is called *7bit data*.
165 Textual string consisted of Control characters between 0 .. 31 and 127,
166 and space represented by 32, and graphic characters between 33 .. 236
167 are called *7bit (textual) string*.
169 Traditional Internet MTA (*Note MTA::) can translate 7bit data, so it is
170 no need to translate by Quoted-Printable (*Note Quoted-Printable::) or
171 Base64 (*Note Base64::) for 7bit data.
173 However if there are too long lines, it can not translate by 7bit MTA
174 even if it is 7bit data. RFC 821 (*Note RFC 821::) and RFC 2045 (*Note
175 RFC 2045::) require lines in 7bit data must be less than 998 bytes. So
176 if a "7bit data" has a line more than 999 bytes, it is regarded as
177 binary (*Note binary::). For example, Postscript file should be encoded
183 File: tm-en.info, Node: 8bit, Next: 94-character set, Prev: 7bit, Up: Glossary
188 *8bit* means any integer between 0 .. 255.
190 Any data represented by 8bit integers is called *8bit data*.
192 Textual string consisted of Control characters between 0 .. 31, 127, and
193 128 .. 159, and space represented by 32, and graphic characters between
194 33 .. 236 and 160 .. 255 are called *8bit (textual) string*.
196 For example, iso-8859-1 (*Note iso-8859-1::) or euc-kr (*Note euc-kr::)
197 are coded-character-set represented by 8bit textual string.
199 Traditional Internet MTA (*Note MTA::) can translate only 7bit (*Note
200 7bit::) data, so if a 8bit data will be translated such MTA, it must be
201 encoded by Quoted-Printable (*Note Quoted-Printable::) or Base64 (*Note
204 However 8bit MTA are increasing today.
206 However if there are too long lines, it can not translate by 8bit MTA
207 even if it is 8bit data. RFC 2045 (*Note RFC 2045::) require lines in
208 8bit data must be less than 998 bytes. So if a "8bit data" has a line
209 more than 999 bytes, it is regarded as binary (*Note binary::), so it
210 must be encoded by Base64 or Quoted-Printable.
215 File: tm-en.info, Node: 94-character set, Next: 96-character set, Prev: 8bit, Up: Glossary
220 *94-character set* is a kind of 1 byte
221 graphic character set (*Note graphic character set::), each characters
222 are in positions 02/01 (33) to 07/14 (126) or 10/01 (161) to 15/14
223 (254). (ex. ASCII (*Note ASCII::), JIS X0201-Latin)
228 File: tm-en.info, Node: 96-character set, Next: 94x94-character set, Prev: 94-character set, Up: Glossary
233 *96-character set* is a kind of 1 byte
234 graphic character set (*Note graphic character set::), each characters
235 are in positions 02/00 (32) to 07/15 (126) or 10/00 (160) to 15/15
236 (255). (ex. ISO 8859)
241 File: tm-en.info, Node: 94x94-character set, Next: ASCII, Prev: 96-character set, Up: Glossary
246 *94x94-character set* is a kind of 2
247 byte graphic character set (*Note graphic character set::), each bytes
248 are in positions 02/01 (33) to 07/14 (126) or 10/01 (161) to 15/14
249 (254). (ex. JIS X0208 (*Note JIS X0208::), GB 2312 (*Note GB 2312::))
254 File: tm-en.info, Node: ASCII, Next: Base64, Prev: 94x94-character set, Up: Glossary
259 *ASCII* is a 94-character set (*Note 94-character set::) contains primary latin characters (A-Z, a-z), numbers and some
260 characters. It is a standard of the United States of America. It is a
261 variant of ISO 646 (*Note ISO 646::).
264 [ASCII] "Coded Character Set -- 7-Bit American Standard Code for
265 Information Interchange", ANSI X3.4:1986.
271 File: tm-en.info, Node: Base64, Next: binary, Prev: ASCII, Up: Glossary
276 *Base64* is a transfer encoding method of MIME
277 (*Note MIME::) defined in RFC 2045 (*Note RFC 2045::).
279 The encoding process represents 24-bit groups of input bits as output
280 strings of 4 encoded characters. Encoded characters represent integer 0
281 .. 63 or *pad*. Base64 data must be 4 * n bytes, so
282 pad is used to adjust size.
284 These 65 characters are subset of all versions of ISO 646, including
285 US-ASCII, and all versions of EBCDIC. So it is safe even if it is
286 translated by non-Internet gateways.
291 File: tm-en.info, Node: binary, Next: cn-gb, Prev: Base64, Up: Glossary
296 Any byte stream is called *binary*.
298 It does not require structureof lines. It differs from from 8bit (*Note
301 In addition, if line structured data contain too long line (more than
302 998 bytes), it is regarded as binary.
307 File: tm-en.info, Node: cn-gb, Next: cn-big5, Prev: binary, Up: Glossary
312 A MIME charset (*Note MIME charset::) for simplified Chinese mainly used
313 in the Chinese mainland.
315 It is a 8bit (*Note 8bit::) coded character set (*Note coded character
316 set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII (*Note
317 ASCII::) to combine GB 2312 (*Note GB 2312::).
319 It is defined in RFC 1922 (*Note RFC 1922::).
324 File: tm-en.info, Node: cn-big5, Next: CNS 11643, Prev: cn-gb, Up: Glossary
329 A MIME charset (*Note MIME charset::) for traditional Chinese mainly
330 used in Taiwan and Hon Kong.
332 It is a 8bit (*Note 8bit::) coded character set (*Note coded character
333 set::) not based on ISO 2022 (*Note ISO 2022::). It is a de-fact
336 It is defined in RFC 1922 (*Note RFC 1922::).
338 cf. [BIG5] Institute for Information Industry, "Chinese Coded
339 Character Set in Computer", March 1984.
341 It corresponds to CNS 11643 (*Note CNS 11643::).
346 File: tm-en.info, Node: CNS 11643, Next: coded character set, Prev: cn-big5, Up: Glossary
351 Graphic character set (*Note Graphic character set::)s for Chinese
352 mainly written by traditional Chinese mainly used in Taiwan and Hong
353 Kong. It is a standard of Taiwan. Currently there are seven 94x94
354 character set (*Note 94x94 character set::).
356 Final byte of ISO 2022 (*Note ISO 2022::) are following:
382 [CNS 11643-1992] "Standard Interchange Code for Generally-Used
383 Chinese Characters", CNS 11643:1992.
389 File: tm-en.info, Node: coded character set, Next: code extension, Prev: CNS 11643, Up: Glossary
391 Coded character set, Character code
392 -----------------------------------
394 A set of unambiguous rules that establishes a character set and the
395 one-to-one relationship between the characters of the set and their bit
401 File: tm-en.info, Node: code extension, Next: Content-Disposition, Prev: coded character set, Up: Glossary
406 The techniques for the encoding of characters that are not included in
407 the character set of a given code. (ex. ISO 2022 (*Note ISO 2022::))
412 File: tm-en.info, Node: Content-Disposition, Next: Content-Type field, Prev: code extension, Up: Glossary
414 Content-Disposition field
415 -------------------------
417 A field to specify presentation of entity or file name. It is an
418 extension for MIME (*Note MIME::).
421 [RFC 1806] E R. Troost and S. Dorner, "Communicating Presentation
422 Information in Internet Messages: The Content-Disposition Header",
423 June 1995, Experimental.
429 File: tm-en.info, Node: Content-Type field, Next: Emacs, Prev: Content-Disposition, Up: Glossary
434 Header field to represent information about body, such as media type
435 (*Note media type::), MIME charset (*Note MIME charset::). It is
436 defined in RFC 2045 (*Note RFC 2045::).
440 Historically, Content-Type field was proposed in RFC 1049. In it,
441 Content-Type did not distinguish type and subtype. However MIME
442 parser may be able to accept RFC 1049 based Content-Type as unknown
446 Content-Type field is defined as following:
448 "Content-Type" ":" *type* "/"
449 *subtype* *( ";" *parameter* )
454 Content-Type: image/jpeg
457 Content-Type: text/plain; charset=iso-2022-jp
462 A part does not have content-type field is regarded as
464 Content-Type: text/plain; charset=us-ascii
466 (cf. *Note us-ascii::)
469 And a part has unknown type/subtype is regarded as
471 Content-Type: application/octet-stream
478 File: tm-en.info, Node: Emacs, Next: encoded-word, Prev: Content-Type field, Up: Glossary
483 In this document, `Emacs' means GNU Emacs released by FSF, and `emacs'
484 means any variants of GNU Emacs.
489 File: tm-en.info, Node: encoded-word, Next: encapsulation, Prev: Emacs, Up: Glossary
494 Representation non ASCII (*Note ASCII::) characters in header. It is
495 defined in *RFC 2047*.
498 [RFC 2047] K. Moore, "MIME (Multipurpose Internet Mail Extensions)
499 Part Three: Message Header Extensions for Non-ASCII Text", November
500 1996, Standards Track (obsolete RFC 1521,1522,1590).
506 File: tm-en.info, Node: encapsulation, Next: euc-kr, Prev: encoded-word, Up: Glossary
511 Method to insert whole Internet message (*Note RFC 822::) into another
514 For example, it is used to forward a message.
516 (cf. *Note message/rfc822::)
522 File: tm-en.info, Node: euc-kr, Next: FTP, Prev: encapsulation, Up: Glossary
527 A MIME charset (*Note MIME charset::) for Korean.
529 It is a 8bit (*Note 8bit::) coded character set (*Note coded character
530 set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII (*Note
531 ASCII::) to combine KS C5601 (*Note KS C5601::).
533 It is defined in RFC 1557 (*Note RFC 1557::).
535 cf. [euc-kr] Korea Industrial Standards Association, "Hangul Unix
536 Environment", KS C 5861:1992.
542 File: tm-en.info, Node: FTP, Next: GB 2312, Prev: euc-kr, Up: Glossary
548 [FTP: RFC 959] Postel, J. and J. Reynolds, "File Transfer
549 Protocol", October 1985, STD 9.
555 File: tm-en.info, Node: GB 2312, Next: GB 8565.2, Prev: FTP, Up: Glossary
560 A 94x94 character set (*Note 94x94 character set::) for Chinese mainly
561 written by simplified Chinese mainly used in the Chinese mainland. It
562 is a standard of China.
564 Final byte of ISO 2022 (*Note ISO 2022::) is 04/01 (`A').
567 [GB 2312] "Code of Chinese Graphic Character Set for Information
568 Interchange - Primary Set", GB 2312:1980.
574 File: tm-en.info, Node: GB 8565.2, Next: graphic character set, Prev: GB 2312, Up: Glossary
579 A 94x94 character set (*Note 94x94 character set::) for Chinese as
580 supplement to GB 2312 (*Note GB 2312::). It is a standard of China.
583 [GB 8565.2] "Information Processing - Coded Character Sets for Text
584 Communication - Part 2: Graphic Characters used with Primary Set",
591 File: tm-en.info, Node: graphic character set, Next: hz-gb2312, Prev: GB 8565.2, Up: Glossary
593 Graphic Character Set
594 ---------------------
596 Coded character set (*Note Coded character set::) for graphic
602 File: tm-en.info, Node: hz-gb2312, Next: ISO 2022, Prev: graphic character set, Up: Glossary
607 A MIME charset (*Note MIME charset::) for simplified Chinese mainly used
608 in the Chinese mainland.
610 It extends ASCII (*Note ASCII::) to combine GB 2312 (*Note GB 2312::),
611 its technique is like iso-2022-jp (*Note iso-2022-jp::), but it is
612 designed to be ASCII printable to use special form for ESC sequence to
613 designate GB 2312 to G0.
615 It is defined in RFC 1842 and 1843.
618 [RFC 1842] Y. Wei, Y. Zhang, J. Li, J. Ding and Y. Jiang, "ASCII
619 Printable Characters-Based Chinese Character Encoding for Internet
620 Messages", August 1995, Informational.
623 [RFC 1843] F. Lee, "HZ - A Data Format for Exchanging Files of
624 Arbitrarily Mixed Chinese and ASCII characters", August 1995,
631 File: tm-en.info, Node: ISO 2022, Next: iso-2022-cn, Prev: hz-gb2312, Up: Glossary
636 It is a standard for character code structure and code extension (*Note
637 code extension::) technique.
640 [ISO 2022] International Organization for Standardization (ISO),
641 "Information Processing: ISO 7-bit and 8-bit coded character sets:
642 Code extension techniques", ISO/IEC 2022:1994.
648 File: tm-en.info, Node: iso-2022-cn, Next: iso-2022-cn-ext, Prev: ISO 2022, Up: Glossary
653 A MIME charset (*Note MIME charset::) for Chinese.
655 It is a 7bit (*Note 7bit::) coded character set (*Note coded character
656 set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII (*Note
657 ASCII::) to combine GB 2312 (*Note GB 2312::) and/or CNS 11643 plain 1,
658 plain 2 (*Note CNS 11643::).
660 It is defined in RFC 1922 (*Note RFC 1922::).
665 File: tm-en.info, Node: iso-2022-cn-ext, Next: iso-2022-jp, Prev: iso-2022-cn, Up: Glossary
670 A MIME charset (*Note MIME charset::) for Chinese.
672 It is a 7bit (*Note 7bit::) coded character set (*Note coded character
673 set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII (*Note
674 ASCII::) to combine GB 2312 (*Note GB 2312::), CNS 11643 plain 1 .. 7
675 (*Note CNS 11643::), ISO-IR-165 (*Note ISO-IR-165::) and other Chinese
676 graphic character sets.
678 It is defined in RFC 1922 (*Note RFC 1922::).
681 MULE 2.3 and current XEmacs/mule can not use it correctly.
683 Emacs/mule can use it.
689 File: tm-en.info, Node: iso-2022-jp, Next: iso-2022-jp-2, Prev: iso-2022-cn-ext, Up: Glossary
694 A MIME charset (*Note MIME charset::) for Japanese.
696 It is a 7bit (*Note 7bit::) coded character set (*Note coded character
697 set::) based on old ISO 2022 (*Note ISO 2022::). It switches ASCII
698 (*Note ASCII::), JIS X0201-Latin, JIS X0208-1978 (*Note JIS
699 C6226-1978::) and JIS X0208-1983 (*Note JIS X0208::).
701 It is defined in RFC 1468.
704 JIS X0208-1997? will define it in annex as non-ISO 2022 (*Note ISO
709 [iso-2022-jp: RFC 1468] Murai J., M. Crispin, and E. van der Poel,
710 "Japanese Character Encoding for Internet Messages", June 1993.
716 File: tm-en.info, Node: iso-2022-jp-2, Next: iso-2022-kr, Prev: iso-2022-jp, Up: Glossary
721 A MIME charset (*Note MIME charset::), which is a multilingual extension
722 of iso-2022-jp (*Note iso-2022-jp::).
724 It is defined in RFC 1554.
727 [iso-2022-jp-2: RFC 1554] Ohta M. and Handa K., "ISO-2022-JP-2:
728 Multilingual Extension of ISO-2022-JP", December 1993,
735 File: tm-en.info, Node: iso-2022-kr, Next: ISO 646, Prev: iso-2022-jp-2, Up: Glossary
740 A MIME charset (*Note MIME charset::) for Korean language (Hangul
743 It is based on ISO 2022 (*Note ISO 2022::) code extension (*Note code
744 extension::) technique to extend ASCII (*Note ASCII::) to use KS C5601
745 (*Note KS C5601::) as 7bit (*Note 7bit::) text.
747 It is defined in RFC 1557 (*Note RFC 1557::).
752 File: tm-en.info, Node: ISO 646, Next: ISO 8859-1, Prev: iso-2022-kr, Up: Glossary
758 [ISO 646] International Organization for Standardization (ISO),
759 "Information technology: ISO 7-bit coded character set for
760 information interchange", ISO/IEC 646:1991.
766 File: tm-en.info, Node: ISO 8859-1, Next: iso-8859-1, Prev: ISO 646, Up: Glossary
772 [ISO 8859-1] International Organization for Standardization (ISO),
773 "Information Processing -- 8-bit Single-Byte Coded Graphic
774 Character Sets -- Part 1: Latin Alphabet No.1", ISO 8859-1:1987.
780 File: tm-en.info, Node: iso-8859-1, Next: ISO 8859-2, Prev: ISO 8859-1, Up: Glossary
785 *iso-8859-1* is a MIME charset (*Note MIME charset::) for west-European languages written by Latin script.
787 It is a 8bit (*Note 8bit::) coded character set (*Note coded character
788 set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII (*Note
789 ASCII::) to combine ISO 8859-1 (*Note ISO 8859-1::).
791 It is defined in RFC 2046 (*Note RFC 2046::).
796 File: tm-en.info, Node: ISO 8859-2, Next: iso-8859-2, Prev: iso-8859-1, Up: Glossary
802 [ISO 8859-2] International Organization for Standardization (ISO),
803 "Information Processing -- 8-bit Single-Byte Coded Graphic
804 Character Sets -- Part 2: Latin alphabet No.2", ISO 8859-2:1987.
810 File: tm-en.info, Node: iso-8859-2, Next: ISO 8859-3, Prev: ISO 8859-2, Up: Glossary
815 *iso-8859-2* is a MIME charset (*Note MIME charset::) for east-European languages written by Latin script.
817 It is a 8bit (*Note 8bit::) coded character set (*Note coded character
818 set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII (*Note
819 ASCII::) to combine ISO 8859-2 (*Note ISO 8859-2::).
821 It is defined in RFC 2046 (*Note RFC 2046::).
826 File: tm-en.info, Node: ISO 8859-3, Next: ISO 8859-4, Prev: iso-8859-2, Up: Glossary
832 [ISO 8859-3] International Organization for Standardization (ISO),
833 "Information Processing -- 8-bit Single-Byte Coded Graphic
834 Character Sets -- Part 3: Latin alphabet No.3", ISO 8859-3:1988.
840 File: tm-en.info, Node: ISO 8859-4, Next: ISO 8859-5, Prev: ISO 8859-3, Up: Glossary
846 [ISO 8859-4] International Organization for Standardization (ISO),
847 "Information Processing -- 8-bit Single-Byte Coded Graphic
848 Character Sets -- Part 4: Latin alphabet No.4", ISO 8859-4:1988.
854 File: tm-en.info, Node: ISO 8859-5, Next: iso-8859-5, Prev: ISO 8859-4, Up: Glossary
860 [ISO 8859-5] International Organization for Standardization (ISO),
861 "Information Processing -- 8-bit Single-Byte Coded Graphic
862 Character Sets -- Part 5: Latin/Cyrillic alphabet", ISO
869 File: tm-en.info, Node: iso-8859-5, Next: ISO 8859-6, Prev: ISO 8859-5, Up: Glossary
874 *iso-8859-5* is a MIME charset (*Note MIME charset::) for Cyrillic script.
876 It is a 8bit (*Note 8bit::) coded character set (*Note coded character
877 set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII (*Note
878 ASCII::) to combine ISO 8859-5 (*Note ISO 8859-5::).
880 It is defined in RFC 2046 (*Note RFC 2046::).
885 File: tm-en.info, Node: ISO 8859-6, Next: ISO 8859-7, Prev: iso-8859-5, Up: Glossary
891 [ISO 8859-6] International Organization for Standardization (ISO),
892 "Information Processing -- 8-bit Single-Byte Coded Graphic
893 Character Sets -- Part 6: Latin/Arabic alphabet", ISO 8859-6:1987.
899 File: tm-en.info, Node: ISO 8859-7, Next: iso-8859-7, Prev: ISO 8859-6, Up: Glossary
905 [ISO 8859-7] International Organization for Standardization (ISO),
906 "Information Processing -- 8-bit Single-Byte Coded Graphic
907 Character Sets -- Part 7: Latin/Greek alphabet", ISO 8859-7:1987.
913 File: tm-en.info, Node: iso-8859-7, Next: ISO 8859-8, Prev: ISO 8859-7, Up: Glossary
918 *iso-8859-7* is a MIME charset (*Note MIME charset::) for Greek script.
920 It is a 8bit (*Note 8bit::) coded character set (*Note coded character
921 set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII (*Note
922 ASCII::) to combine ISO 8859-7 (*Note ISO 8859-7::).
924 It is defined in RFC 1947.
927 [iso-8859-7: RFC 1947] D. Spinellis, "Greek Character Encoding for
928 Electronic Mail Messages", May 1996, Informational.
934 File: tm-en.info, Node: ISO 8859-8, Next: ISO 8859-9, Prev: iso-8859-7, Up: Glossary
940 [ISO 8859-8] International Organization for Standardization (ISO),
941 "Information Processing -- 8-bit Single-Byte Coded Graphic
942 Character Sets -- Part 8: Latin/Hebrew alphabet", ISO 8859-8:1988.
948 File: tm-en.info, Node: ISO 8859-9, Next: ISO-IR-165, Prev: ISO 8859-8, Up: Glossary
954 [ISO 8859-9] International Organization for Standardization (ISO),
955 "Information Processing -- 8-bit Single-Byte Coded Graphic
956 Character Sets -- Part 9: Latin alphabet No.5", ISO 8859-9:1990.
962 File: tm-en.info, Node: ISO-IR-165, Next: JIS X0201, Prev: ISO 8859-9, Up: Glossary
964 ISO-IR-165, CCITT Extended GB
965 -----------------------------
967 A 94x94-character set (*Note 94x94-character set::) for Chinese mainly
968 written by simplified Chinese mainly used in the Chinese mainland
971 It consists of GB 2312 (*Note GB 2312::), GB 8865.2 (*Note GB 8865.2::)
972 and additional 150 characters.
974 Final byte of ISO 2022 (*Note ISO 2022::) is 04/05 (`E').
979 File: tm-en.info, Node: JIS X0201, Next: JIS C6226, Prev: ISO-IR-165, Up: Glossary
984 It defines two 94-character set (*Note 94-character set::), for Latin
985 script (a variant of ISO 646 (*Note ISO 646::)) and Katakana script, and
986 7bit and 8bit coded character set (*Note coded character set::)s.
988 It was renamed from *JIS C6220-1976*.
991 [JIS X0201-1976] Japanese Standards Association, "Code for
992 Information Interchange", JIS X 0201-1976:.
995 In addition, revised version will be published in 1997.
998 [JIS X0201-1997?] Japanese Standards Association, "7-bit and 8-bit
999 coded character sets for information interchange", JIS X 0201:1997?
1006 File: tm-en.info, Node: JIS C6226, Next: JIS X0208, Prev: JIS X0201, Up: Glossary
1011 A 94x94-character set (*Note 94x94-character set::) for Japanese. It
1012 was renamed to JIS X0208-1978.
1014 (cf. *Note JIS X0208::)
1020 File: tm-en.info, Node: JIS X0208, Next: JIS X0212, Prev: JIS C6226, Up: Glossary
1025 A 94x94-character set (*Note 94x94-character set::) for Japanese.
1026 Japanese standard. It was published in 1978, and revised in 1983 and
1027 1990. In the Internet message, 1983 edition is major.
1029 JIS X0208 contains some symbols, numbers, primary Latin script, Hiragana
1030 script, Katakana script, Greek script, Cyrillic script, box drawing
1031 parts, Kanji (Ideographic characters used in Japanese). Notice that
1032 some symbols and box drawing parts were added in 1983 and some Kanjis
1033 were changed or swapped code points. So 1978 edition and 1983 edition
1034 are regarded as different graphic character set.
1036 1990 edition added some characters, so designation of 1990 edition
1037 requires `identify revised registration' sequence, ESC 02/06 4/0 as
1038 prefix of designation sequence.
1041 [JIS X0208-1978] Japanese Standards Association, "Code of the
1042 Japanese graphic character set for information interchange", JIS
1046 [JIS X0208-1983,1990] Japanese Standards Association, "Code of the
1047 Japanese graphic character set for information interchange", JIS
1051 In addition, revised version will be published in 1997. (It does not
1052 change graphic character set)
1055 [JIS X0208-1997?] Japanese Standards Association, "7-bit and 8-bit
1056 double byte coded Kanji sets for information interchange", JIS X
1063 File: tm-en.info, Node: JIS X0212, Next: koi8-r, Prev: JIS X0208, Up: Glossary
1068 A 94x94 character set (*Note 94x94 character set::) for Japanese as
1069 supplement to JIS X0208 (*Note JIS X0208::). It is a standard of Japan.
1071 Final byte of ISO 2022 (*Note ISO 2022::) is 04/04 (`D').
1076 File: tm-en.info, Node: koi8-r, Next: KS C5601, Prev: JIS X0212, Up: Glossary
1081 A MIME charset (*Note MIME charset::) for Cyrillic script for Russian or
1084 It is a 1 byte 8bit (*Note 8bit::) coded character set (*Note coded
1085 character set::), not based on ISO 2022 (*Note ISO 2022::). It is a
1088 It is defined in RFC 1489.
1091 [RFC 1489] A. Chernov, "Registration of a Cyrillic Character Set",
1098 File: tm-en.info, Node: KS C5601, Next: media type, Prev: koi8-r, Up: Glossary
1103 A 94x94-character set (*Note 94x94-character set::) for Korean language
1104 (Hangul script). Korean Standard. Final byte of ISO 2022 (*Note ISO
1105 2022::) is 04/03 (`C').
1108 [KS C5601] Korea Industrial Standards Association, "Code for
1109 Information Interchange (Hangul and Hanja)", KS C 5601:1987.
1115 File: tm-en.info, Node: media type, Next: message, Prev: KS C5601, Up: Glossary
1120 *media type* specifies the nature of the data
1121 in the body of MIME (*Note MIME::) entity (*Note entity::). It consists of
1122 *type* and *subtype*. It is
1123 defined in RFC 2046 (*Note RFC 2046::).
1125 Currently there are following types:
1132 * *multipart* (*Note multipart::)
1136 And there are various subtypes, for example, application/octet-stream,
1137 audio/basic, image/jpeg, multipart/mixed (*Note multipart/mixed::),
1138 text/plain (*Note text/plain::), video/mpeg...
1140 You can refer registered media types at MEDIA TYPES
1141 (ftp://ftp.isi.edu/in-notes/iana/assignments/media-types).
1143 In addition, you can use private type or subtype using
1144 *x-token*, which as the prefix `x-'. However you
1145 can not use them in public.
1147 (cf. *Note Content-Type field::)
1153 File: tm-en.info, Node: message, Next: message/rfc822, Prev: media type, Up: Glossary
1158 In this document, it means mail defined in RFC 822 (*Note RFC 822::) and
1159 news message defined in RFC 1036 (*Note RFC 1036::).
1164 File: tm-en.info, Node: message/rfc822, Next: method, Prev: message, Up: Glossary
1169 *message/rfc822* indicates that the body
1170 contains an encapsulated message, with the syntax of an RFC 822 (*Note
1171 RFC 822::) message. It is the replacement of traditional RFC 934 (*Note
1172 RFC 934::) encapsulation. It is defined in RFC 2046 (*Note RFC 2046::).
1177 File: tm-en.info, Node: method, Next: MIME, Prev: message/rfc822, Up: Glossary
1182 Application program of tm-view to process for specified media type
1183 (*Note media type::) when user plays an entity.
1185 There are two kinds of methods, *internal method* and *external method*.
1186 Internal method is written by Emacs Lisp. External method is written by
1187 C or script languages and called by asynchronous process call.
1189 (cf. *Note (tm-view-en)method::)
1195 File: tm-en.info, Node: MIME, Next: MIME charset, Prev: method, Up: Glossary
1200 MIME stands for *Multipurpose Internet Mail Extensions*, it is an
1201 extension for RFC 822 (*Note RFC 822::).
1203 According to RFC 2045:
1205 STD 11, RFC 822, defines a message representation protocol specifying
1206 considerable detail about US-ASCII message headers, and leaves the
1207 message content, or message body, as flat US-ASCII text. This set of
1208 documents, collectively called the Multipurpose Internet Mail
1209 Extensions, or MIME, redefines the format of messages to allow for
1211 1. textual message bodies in character sets other than US-ASCII,
1212 2. an extensible set of different formats for non-textual message
1214 3. multi-part message bodies, and
1215 4. textual header information in character sets other than US-ASCII.
1218 It is defined in RFC 2045 (*Note RFC 2045::), RFC 2046 (*Note RFC
1219 2046::), RFC 2047 (*Note encoded-word::), RFC 2048 (*Note RFC 2048::)
1220 and RFC 2049 (*Note RFC 2049::).
1225 File: tm-en.info, Node: MIME charset, Next: MTA, Prev: MIME, Up: Glossary
1230 Coded character set (*Note Coded character set::) used in Content-Type
1231 field (*Note Content-Type field::) or charset parameter of encoded-word
1232 (*Note encoded-word::).
1234 It is defined in RFC 2045 (*Note RFC 2045::).
1236 iso-2022-jp (*Note iso-2022-jp::) or euc-kr (*Note euc-kr::) are kinds
1237 of it. (In this document, MIME charsets are written by small letters to
1238 distinguish graphic character set (*Note graphic character set::). For
1239 example, ISO 8859-1 is a graphic character set, and iso-8859-1 is a MIME
1245 File: tm-en.info, Node: MTA, Next: MUA, Prev: MIME charset, Up: Glossary
1250 *Message Transfer Agent*. It
1251 means mail transfer programs (ex. sendmail) and news servers.
1259 File: tm-en.info, Node: MUA, Next: MULE, Prev: MTA, Up: Glossary
1264 *Message User Agent*. It means mail
1265 readers and news readers.
1273 File: tm-en.info, Node: MULE, Next: multipart, Prev: MUA, Up: Glossary
1278 Multilingual extension of GNU Emacs (*Note Emacs::) by HANDA Ken'ichi et
1282 [MULE] Nishikimi M., Handa K. and Tomura S., "Mule: MULtilingual
1283 Enhancement to GNU Emacs", Proc. of INET'93, August, 1993.
1285 Now, FSF and HANDA Ken'ichi et al. are working to merge MULE feature
1286 into Emacs, there is alpha version of mule merged emacs
1287 (ftp://etlport.etl.go.jp/pub/mule/mule-19.33-delta.taz).
1289 In addition, there is XEmacs with mule feature.
1291 So now, there are 3 kinds of mule variants.
1293 In this document, *mule* means any mule variants,
1294 *MULE* means original MULE (..2.3),
1295 *Emacs/mule* means mule merged Emacs,
1296 *XEmacs/mule* means XEmacs with mule feature.
1301 File: tm-en.info, Node: multipart, Next: multipart/alternative, Prev: MULE, Up: Glossary
1306 *multipart* means media type (*Note media type::)
1307 to insert multiple entities (*Note entities::) in a single body. Or it
1308 also indicates a message consists of multiple entities.
1310 There are following subtypes registered in RFC 2046 (*Note RFC 2046::):
1312 * multipart/mixed (*Note multipart/mixed::)
1313 * multipart/alternative (*Note multipart/alternative::)
1314 * multipart/digest (*Note multipart/digest::)
1315 * multipart/parallel (*Note multipart/parallel::)
1317 and registered in RFC 1847 (*Note Security multipart::):
1319 * multipart/signed (*Note multipart/signed::)
1320 * multipart/encrypted (*Note multipart/encrypted::)
1326 File: tm-en.info, Node: multipart/alternative, Next: multipart/digest, Prev: multipart, Up: Glossary
1328 multipart/alternative
1329 ---------------------
1331 *multipart/digest* is one of multipart
1332 (*Note multipart::) media types. This type is syntactically identical
1333 to multipart/mixed (*Note multipart/mixed::), but the semantics are
1334 different. In particular, each of the body parts is an "alternative"
1335 version of the same information.
1337 (cf. *Note RFC 2046::)
1343 File: tm-en.info, Node: multipart/digest, Next: multipart/encrypted, Prev: multipart/alternative, Up: Glossary
1348 *multipart/digest* is one of multipart
1349 (*Note multipart::) media types. This type is syntactically identical
1350 to multipart/mixed (*Note multipart/mixed::), but the semantics are
1351 different. In particular, in a digest, the default Content-Type value
1352 for a body part is changed from text/plain (*Note text/plain::) to
1353 message/rfc822 (*Note message/rfc822::).
1355 This is the replacement of traditional RFC 1153 (*Note RFC 1153::) based
1356 encapsulation (*Note encapsulation::).
1358 (cf. *Note RFC 2046::)
1364 File: tm-en.info, Node: multipart/encrypted, Next: multipart/mixed, Prev: multipart/digest, Up: Glossary
1369 It is a Security multipart (*Note Security multipart::) defined in RFC
1370 1847, used to represent encrypted message.
1372 (cf. *Note PGP/MIME::)
1378 File: tm-en.info, Node: multipart/mixed, Next: multipart/parallel, Prev: multipart/encrypted, Up: Glossary
1383 Primary and default subtype of multipart (*Note multipart::), it is used
1384 when the body parts are independent and need to be bundled in a
1387 (cf. *Note RFC 2046::)
1393 File: tm-en.info, Node: multipart/parallel, Next: multipart/signed, Prev: multipart/mixed, Up: Glossary
1398 *multipart/parallel* is a subtype of
1399 multipart (*Note multipart::). This type is syntactically identical to
1400 multipart/mixed (*Note multipart/mixed::), but the semantics are
1401 different. In particular, in a parallel entity, the order of body parts
1404 (cf. *Note RFC 2046::)
1410 File: tm-en.info, Node: multipart/signed, Next: PGP, Prev: multipart/parallel, Up: Glossary
1415 It is a Security multipart (*Note Security multipart::) defined in RFC
1416 1847, used to represent signed message.
1418 (cf. *Note PGP/MIME::)
1424 File: tm-en.info, Node: PGP, Next: PGP-kazu, Prev: multipart/signed, Up: Glossary
1429 A public key encryption program by Phil Zimmermann. It provides
1430 encryption and signature for message (*Note message::). PGP stands for
1431 *Pretty Good Privacy*.
1433 Traditional PGP uses RFC 934 (*Note RFC 934::) encapsulation (*Note
1434 encapsulation::). It is conflict with MIME (*Note MIME::). So PGP/MIME
1435 (*Note PGP/MIME::) is defined. On the other hand, PGP-kazu (*Note
1436 PGP-kazu::) was proposed to use PGP encapsulation in MIME. But it is
1440 [PGP: RFC 1991] D. Atkins, W. Stallings and P. Zimmermann, "PGP
1441 Message Exchange Formats", August 1996, Informational.
1448 File: tm-en.info, Node: PGP-kazu, Next: PGP/MIME, Prev: PGP, Up: Glossary
1453 In this document, *PGP-kazu* means a method to use traditional PGP
1454 encapsulation in MIME (*Note MIME::), proposed by YAMAMOTO Kazuhiko.
1456 PGP-kazu defines a media type (*Note media type::),
1459 In application/pgp entity, PGP encapsulation (*Note encapsulation::) is
1460 used. PGP encapsulation conflicts with MIME, so it requires
1461 PGP-processing to read as MIME message.
1463 It was obsoleted, so you should use PGP/MIME (*Note PGP/MIME::).
1464 However if you want to use traditional PGP message, it might be
1470 File: tm-en.info, Node: PGP/MIME, Next: Quoted-Printable, Prev: PGP-kazu, Up: Glossary
1475 PGP (*Note PGP::) and MIME (*Note MIME::) integration proposed by
1478 It is based on RFC 1847 (*Note Security multipart::), so it is
1479 harmonious with MIME, but it is not compatible with traditional PGP
1480 encapsulation. However MIME MUA can read PGP/MIME signed message even
1481 if it does not support PGP/MIME.
1483 PGP/MIME (*Note PGP/MIME::) will be standard of PGP message.
1486 [PGP/MIME: RFC 2015] M. Elkins, "MIME Security with Pretty Good
1487 Privacy (PGP)", October 1996, Standards Track.
1493 File: tm-en.info, Node: Quoted-Printable, Next: RFC 821, Prev: PGP/MIME, Up: Glossary
1498 *Quoted-Printable* is a transfer
1499 encoding method of MIME (*Note MIME::) defined in RFC 2045 (*Note RFC
1502 If the data being encoded are mostly US-ASCII text, the encoded form of
1503 the data remains largely recognizable by humans.
1505 (cf. *Note Base64::)
1511 File: tm-en.info, Node: RFC 821, Next: RFC 822, Prev: Quoted-Printable, Up: Glossary
1517 [SMTP: RFC 821] J. Postel, "Simple Mail Transfer Protocol", August
1524 File: tm-en.info, Node: RFC 822, Next: RFC 934, Prev: RFC 821, Up: Glossary
1529 A RFC defines format of Internet mail message, mainly *message header*.
1533 news message is based on RFC 822, so *Internet message* may be more suitable than
1538 [RFC 822] D. Crocker, "Standard for the Format of ARPA Internet
1539 Text Messages", August 1982, STD 11.
1545 File: tm-en.info, Node: RFC 934, Next: RFC 1036, Prev: RFC 822, Up: Glossary
1550 A RFC defines an *encapsulation* (*Note encapsulation::) method for
1551 Internet mail (*Note RFC 822::).
1553 It conflicts with MIME (*Note MIME::), so you should use message/rfc822
1554 (*Note message/rfc822::).
1557 [RFC 934] Marshall T. Rose and Einar A. Stefferud, "Proposed
1558 Standard for Message Encapsulation", January 1985.
1564 File: tm-en.info, Node: RFC 1036, Next: RFC 1153, Prev: RFC 934, Up: Glossary
1569 A RFC defines format of USENET message. It is a subset of RFC 822
1570 (*Note RFC 822::). It is not Internet standard, but a lot of netnews
1571 excepting Usenet uses it.
1574 [USENET: RFC 1036] M. Horton and R. Adams, "Standard for
1575 Interchange of USENET Messages", December 1987, (obsolete RFC 850).
1581 File: tm-en.info, Node: RFC 1153, Next: RFC 1557, Prev: RFC 1036, Up: Glossary
1587 [RFC 1153] F. Wancho, "Digest Message Format", April 1990.
1593 File: tm-en.info, Node: RFC 1557, Next: RFC 1922, Prev: RFC 1153, Up: Glossary
1598 A RFC defines MIME charset (*Note MIME charset::)s for Korean, euc-kr
1599 (*Note euc-kr::) and iso-2022-kr (*Note iso-2022-kr::).
1602 [RFC 1557] U. Choi, K. Chon and H. Park, "Korean Character Encoding
1603 for Internet Messages", December 1993, Informational.
1609 File: tm-en.info, Node: RFC 1922, Next: RFC 2045, Prev: RFC 1557, Up: Glossary
1614 A RFC defines MIME charset (*Note MIME charset::)s for Chinese,
1615 iso-2022-cn (*Note iso-2022-cn::), iso-2022-cn-ext (*Note
1616 iso-2022-cn-ext::), cn-gb (*Note cn-gb::), cn-big5 (*Note cn-big5::),
1619 In addition, it defines additional parameters of Content-Type field
1620 (*Note Content-Type field::) field,
1621 *charset-edition* and
1622 *charset-extension*.
1625 [RFC 1922] Zhu, HF., Hu, DY., Wang, ZG., Kao, TC., Chang, WCH. and
1626 Crispin, M., "Chinese Character Encoding for Internet Messages",
1627 March 1996, Informational.
1633 File: tm-en.info, Node: RFC 2045, Next: RFC 2046, Prev: RFC 1922, Up: Glossary
1639 [RFC 2045] N. Freed and N. Borenstein, "Multipurpose Internet Mail
1640 Extensions (MIME) Part One: Format of Internet Message Bodies",
1641 November 1996, Standards Track (obsolete RFC 1521, 1522, 1590).
1647 File: tm-en.info, Node: RFC 2046, Next: RFC 2048, Prev: RFC 2045, Up: Glossary
1653 [RFC 2046] N. Freed and N. Borenstein, "Multipurpose Internet Mail
1654 Extensions (MIME) Part Two: Media Types", November 1996, Standards
1655 Track (obsolete RFC 1521, 1522, 1590).
1661 File: tm-en.info, Node: RFC 2048, Next: RFC 2049, Prev: RFC 2046, Up: Glossary
1667 [RFC 2048] N. Freed, J. Klensin and J. Postel, "Multipurpose
1668 Internet Mail Extensions (MIME) Part Four: Registration
1669 Procedures", November 1996, Standards Track (obsolete RFC 1521,
1676 File: tm-en.info, Node: RFC 2049, Next: plain text, Prev: RFC 2048, Up: Glossary
1682 [RFC 2049] N. Freed and N. Borenstein, "Multipurpose Internet Mail
1683 Extensions (MIME) Part Five: Conformance Criteria and Examples",
1684 November 1996, Standards Track (obsolete RFC 1521, 1522, 1590).
1690 File: tm-en.info, Node: plain text, Next: Security multipart, Prev: RFC 2049, Up: Glossary
1695 A textual data represented by only coded character set (*Note coded
1696 character set::). It does not have information about font or
1697 typesetting. (cf. *Note text/plain::)
1703 File: tm-en.info, Node: Security multipart, Next: text/enriched, Prev: plain text, Up: Glossary
1708 A format to represent signed/encrypted message in MIME (*Note MIME::).
1710 It defines two multipart media types,
1712 (*Note multipart/signed::) and
1713 *multipart/encrypted*
1714 (*Note multipart/encrypted::).
1716 MOSS and PGP/MIME (*Note PGP/MIME::) are based on it.
1719 [Security multipart: RFC 1847] James Galvin, Gale Murphy, Steve
1720 Crocker and Ned Freed, "Security Multiparts for MIME:
1721 Multipart/Signed and Multipart/Encrypted", October 1995, Standards
1728 File: tm-en.info, Node: text/enriched, Next: text/plain, Prev: Security multipart, Up: Glossary
1734 [text/enriched: RFC 1896] P. Resnick and A. Walker, "The
1735 text/enriched MIME Content-type", February 1996, (obsolete RFC
1742 File: tm-en.info, Node: text/plain, Next: tm-kernel, Prev: text/enriched, Up: Glossary
1747 *text/plain* is a media type (*Note media type::) for plain text (*Note plain text::), defined in RFC 2046 (*Note RFC 2046::).
1749 The default media type of "text/plain; charset=us-ascii" for Internet
1750 mail describes existing Internet practice. That is, it is the type of
1751 body defined by RFC 822 (*Note RFC 822::).
1753 (cf. *Note MIME charset::) (cf. *Note us-ascii::)
1759 File: tm-en.info, Node: tm-kernel, Next: tm-MUA, Prev: text/plain, Up: Glossary
1764 A libraries to provide user interface about MIME (*Note MIME::) for
1765 emacs. tm stands for `tools for MIME'.
1767 *[Unimportant notice(^-^;]*
1769 * tm may not stand for "tiny-mime"(^-^;
1771 * tm may not stand for initial of an author (^-^;
1773 * "Tools for MIME" may be strained (^-^;
1779 File: tm-en.info, Node: tm-MUA, Next: us-ascii, Prev: tm-kernel, Up: Glossary
1784 MUA (*Note MUA::) or MUA extender using tm (*Note tm-kernel::).
1786 *tm oomori package* has following extenders:
1788 * *tm-mh-e* (*Note (tm-mh-e-en)::)
1789 for mh-e (*Note (mh-e)::)
1790 * *tm-gnus* (*Note (tm-gnus_en)::) for GNUS
1791 * *gnus-mime* (*Note (gnus-mime-en)::) for Gnus
1792 * *tm-vm* (*Note (tm-vm_en)::) for VM
1793 * *tm-rmail* for RMAIL
1799 File: tm-en.info, Node: us-ascii, Prev: tm-MUA, Up: Glossary
1804 A MIME charset (*Note MIME charset::) for primary Latin script mainly
1805 written by English or other languages.
1807 It is a 7bit coded character set (*Note coded character set::) based on
1808 ISO 2022 (*Note ISO 2022::), it contains only ASCII (*Note ASCII::) and
1809 code extension (*Note code extension::) is not allowed.
1811 It is standard coded character set of Internet mail. If MIME charset is
1812 not specified, *us-ascii* is used as default.
1814 In addition, *ASCII* of RFC 822 (*Note RFC 822::) should be interpreted
1820 File: tm-en.info, Node: Setting, Next: Bug report, Prev: Introduction, Up: Top
1825 In the tm package, two files, `mime-setup.el' and `tm-setup.el', are
1826 provided to ease the setup.
1828 The `mime-setup.el' is used for the whole MIME related setup including
1829 MIME encoding using `tm-edit.el', while `tm-setup.el' is used to set up
1835 * mime-setup:: Normal setting
1836 * tm-setup:: Setting not to use tm-edit
1837 * setting for VM:: Setting for VM
1838 * manual setting:: Setting up without loading provided setup files
1842 File: tm-en.info, Node: mime-setup, Next: tm-setup, Prev: Setting, Up: Setting
1847 If you want normal setting, please use *mime-setup*. For example,
1848 please insert following into `~/.emacs':
1853 As `mime-setup.el' loads `tm-setup.el', you don't need to load
1854 `tm-setup.el' when you use `mime-setup.el' (Description of old version
1855 of Gnus FAQ is wrong!)
1861 * Notice about GNUS:: Notices for GNUS
1865 File: tm-en.info, Node: signature, Next: Notice about GNUS, Prev: mime-setup, Up: mime-setup
1870 You can set up the *automatic signature selection tool* using
1871 `mime-setup'. If you want to automatically select the signature file
1872 depending on how the message headers show, add lines like shown below to
1873 your .emacs (Refer to the reference manual of `signature.el' for more
1876 (setq signature-file-alist
1877 '((("Newsgroups" . "jokes") . "~/.signature-jokes")
1878 (("Newsgroups" . ("zxr" "nzr")) . "~/.signature-sun")
1879 (("To" . ("ishimaru" "z-suzuki")) . "~/.signature-sun")
1880 (("To" . "tea") . "~/.signature-jokes")
1881 (("To" . ("sim" "oku" "takuo")) . "~/.signature-formal")
1886 -- Variable: mime-setup-use-signature
1888 If it is not `nil', `mime-setup.el' sets up for `signature.el'.
1889 Its default value is `t'.
1893 -- Variable: mime-setup-signature-key-alist
1895 It defines key to bind signature inserting command for each
1896 major-mode. Its default value is following:
1898 ((mail-mode . "\C-c\C-w"))
1901 If you want to change, please rewrite it. For example:
1903 (set-alist 'mime-setup-signature-key-alist
1904 'news-reply-mode "\C-c\C-w")
1909 -- Variable: mime-setup-default-signature-key
1911 If key to bind signature inserting command for a major-mode is not
1912 found from `mime-setup-signature-key-alist', its value is used as
1913 key. Its default value is `"\C-c\C-s"'.
1919 File: tm-en.info, Node: Notice about GNUS, Prev: signature, Up: mime-setup
1924 When `mime-setup.el' sets up for `signature.el', it sets variable
1925 `gnus-signature-file' to `nil'. Therefore GNUS does not insert
1926 signature automatically when it is sending a message. Reason of this
1927 setting is following:
1929 GNUS inserts signature after `tm-edit.el' composed as MIME message.
1930 Therefore signature inserted by GNUS is not processed as a valid MIME
1931 part. In particular, for multipart message, signature places in outside
1932 of MIME part. So MIME MUA might not display it.
1934 Other notice is key bind. In historical reason, key bind to insert
1935 signature is `C-c C-s' (like mh-e (*Note (mh-e)::)) instead of `C-c
1936 C-w'. If you change to GNUS's default, please set following:
1938 (set-alist 'mime-setup-signature-key-alist 'news-reply-mode "\C-c\C-w")
1944 File: tm-en.info, Node: tm-setup, Next: setting for VM, Prev: mime-setup, Up: Setting
1946 Setting not to use tm-edit
1947 ==========================
1949 *tm-setup* only sets up tm-MUA (*Note tm-MUA::)s.
1950 In other words, it is a setting to avoid to use tm-edit. If you don't
1951 want to compose MIME message or want to use other MIME composer, please
1952 use it instead of `mime-setup.el'.
1954 For example, please insert following into `~/.emacs':
1962 If you use `mime-setup.el', you you don't need to load
1969 File: tm-en.info, Node: setting for VM, Next: manual setting, Prev: tm-setup, Up: Setting
1974 If you use *vm*, please insert following in `~/.vm':
1982 If you use *BBDB*, please insert `(require 'tm-vm)' *after*
1983 `(bbdb-insinuate-vm)'.
1989 File: tm-en.info, Node: manual setting, Prev: setting for VM, Up: Setting
1991 Setting up without loading provided setup files
1992 ===============================================
1994 You may find the valuable hints in `mime-setup.el' or `tm-setup.el' if
1995 you want to set up MIME environment without loading the tm-provided
2000 Current tm provides some convenient features to expect tm-edit, and
2001 they can not use if `mime-setup.el' is not used. If you want to
2002 set up original setting to use tm-edit, please declare following
2005 (provide 'mime-setup)
2012 File: tm-en.info, Node: Bug report, Next: Concept Index, Prev: Setting, Up: Top
2014 How to report bug and about mailing list of tm
2015 **********************************************
2017 If you write bug-reports and/or suggestions for improvement, please send
2018 them to the tm Mailing List:
2020 * Japanese <bug-tm-ja@chamonix.jaist.ac.jp>
2021 * English <bug-tm-en@chamonix.jaist.ac.jp>
2024 Notice that, we does not welcome bug reports about too old version.
2025 Bugs in old version might be fixed. So please try latest version at
2028 You should write *good bug report*. If you write only "tm does not
2029 work", we can not find such situations. At least, you should write
2030 name, type, variants and version of OS, emacs, tm and MUA, and setting.
2031 In addition, if error occurs, to send backtrace is very
2032 important. (cf. *Note (emacs)Bugs::)
2034 Bug may not appear only your environment, but also in a lot of
2035 environment (otherwise it might not bug). Therefor if you send mail to
2036 author directly, we must write a lot of mails. So please send mail to
2037 address for tm bugs instead of author.
2039 Via the tm ML, you can report tm bugs, obtain the latest release of tm,
2040 and discuss future enhancements to tm. To join the tm ML, send e-mail
2043 * Japanese <tm-ja-admin@chamonix.jaist.ac.jp>
2044 * English <tm-en-admin@chamonix.jaist.ac.jp>
2046 Since the user registration is done manually, please write the mail body
2047 in human-recognizable language (^_^).
2052 File: tm-en.info, Node: Concept Index, Next: Variable Index, Prev: Bug report, Up: Top
2062 * 7bit (textual) string: 7bit. 12.
2066 * 94-character set: 94-character set. 5.
2067 * 94x94-character set: 94x94-character set. 5.
2068 * 96-character set: 96-character set. 5.
2069 * ANSI X3.4:1986: ASCII. 9.
2070 * application: media type. 21.
2071 * application/pgp: PGP-kazu. 9.
2074 * ASCII: us-ascii. 16.
2075 * audio: media type. 17.
2076 * automatic signature selection
2077 * Base64: Base64. 5.
2078 * BBDB: setting for VM. 14.
2079 * BIG5: cn-big5. 15.
2080 * binary: binary. 6.
2081 * charset-edition: RFC 1922. 12.
2082 * charset-extension: RFC 1922. 13.
2083 * CNS 11643:1992: CNS 11643. 35.
2084 * CNS 11643-1992: CNS 11643. 35.
2085 * Emacs/mule: MULE. 22.
2086 * encapsulation: RFC 934. 6.
2087 * euc-kr: euc-kr. 14.
2088 * Experimental: Content-Disposition. 8.
2089 * external method: method. 10.
2091 * GB 2312: GB 2312. 11.
2092 * GB 2312:1980: GB 2312. 11.
2093 * GB 8565.2: GB 8565.2. 8.
2094 * GB 8565.2:1988: GB 8565.2. 8.
2095 * gnus-mime: tm-MUA. 15.
2096 * good bug report: Bug report. 17.
2097 * image: media type. 15.
2098 * Informational: hz-gb2312. 15.
2099 * Informational: hz-gb2312. 20.
2100 * Informational: iso-2022-jp-2. 10.
2101 * Informational: iso-8859-7. 13.
2102 * Informational: PGP. 15.
2103 * Informational: RFC 1557. 8.
2104 * Informational: RFC 1922. 15.
2105 * internal method: method. 9.
2107 * Internet mail: RFC 822. 10.
2108 * ISO 2022: ISO 2022. 8.
2109 * ISO 646: ISO 646. 5.
2110 * ISO 8859-1: ISO 8859-1. 5.
2111 * ISO 8859-1:1987: ISO 8859-1. 5.
2112 * ISO 8859-2: ISO 8859-2. 5.
2113 * ISO 8859-2:1987: ISO 8859-2. 5.
2114 * ISO 8859-3: ISO 8859-3. 5.
2115 * ISO 8859-3:1988: ISO 8859-3. 5.
2116 * ISO 8859-4: ISO 8859-4. 5.
2117 * ISO 8859-4:1988: ISO 8859-4. 5.
2118 * ISO 8859-5: ISO 8859-5. 5.
2119 * ISO 8859-5:1988: ISO 8859-5. 5.
2120 * ISO 8859-6: ISO 8859-6. 5.
2121 * ISO 8859-6:1987: ISO 8859-6. 5.
2122 * ISO 8859-7: ISO 8859-7. 5.
2123 * ISO 8859-7:1987: ISO 8859-7. 5.
2124 * ISO 8859-8: ISO 8859-8. 5.
2125 * ISO 8859-8:1988: ISO 8859-8. 5.
2126 * ISO 8859-9: ISO 8859-9. 5.
2127 * ISO 8859-9:1990: ISO 8859-9. 5.
2128 * iso-2022-jp: iso-2022-jp. 19.
2129 * iso-2022-jp-2: iso-2022-jp-2. 10.
2130 * iso-8859-1: iso-8859-1. 5.
2131 * iso-8859-2: iso-8859-2. 5.
2132 * iso-8859-5: iso-8859-5. 5.
2133 * iso-8859-7: iso-8859-7. 13.
2134 * iso-8859-7: iso-8859-7. 5.
2135 * ISO/IEC 2022:1994: ISO 2022. 8.
2136 * ISO/IEC 646:1991: ISO 646. 5.
2137 * JIS X 0201-1976:: JIS X0201. 11.
2138 * JIS X0208:1983,1990: JIS X0208. 25.
2139 * JIS C6220-1976: JIS X0201. 10.
2140 * JIS C6226:1978: JIS X0208. 20.
2141 * JIS X 0208:1997? draft: JIS X0208. 34.
2142 * JIS X 0201:1997? draft: JIS X0201. 18.
2143 * JIS X0201-1976: JIS X0201. 11.
2144 * JIS X0201-1997?: JIS X0201. 18.
2145 * JIS X0208-1978: JIS X0208. 20.
2146 * JIS X0208-1983,1990: JIS X0208. 25.
2147 * JIS X0208-1997?: JIS X0208. 34.
2148 * KS C 5601:1987: KS C5601. 9.
2149 * KS C 5861:1992: euc-kr. 14.
2150 * KS C5601: KS C5601. 9.
2151 * media type: media type. 5.
2153 * message: media type. 25.
2154 * Message Transfer Agent: MTA. 5.
2155 * Message User Agent: MUA. 5.
2156 * message/rfc822: message/rfc822. 5.
2157 * mime-setup: mime-setup. 6.
2161 * multipart: media type. 23.
2162 * multipart: multipart. 5.
2163 * multipart/digest: multipart/alternative. 5.
2164 * multipart/digest: multipart/digest. 5.
2165 * multipart/encrypted: Security multipart. 10.
2166 * multipart/parallel: multipart/parallel. 5.
2167 * multipart/signed: Security multipart. 8.
2168 * Multipurpose Internet Mail
2170 * parameter: Content-Type field. 21.
2172 * PGP-kazu: PGP-kazu. 6.
2173 * PGP/MIME: PGP/MIME. 15.
2174 * Pretty Good Privacy: PGP. 7.
2175 * Quoted-Printable: Quoted-Printable. 5.
2176 * RFC 1036: RFC 1036. 9.
2177 * RFC 1153: RFC 1153. 5.
2178 * RFC 1468: iso-2022-jp. 19.
2179 * RFC 1489: koi8-r. 14.
2180 * RFC 1554: iso-2022-jp-2. 10.
2181 * RFC 1557: RFC 1557. 8.
2182 * RFC 1806: Content-Disposition. 8.
2183 * RFC 1842: hz-gb2312. 15.
2184 * RFC 1843: hz-gb2312. 20.
2185 * RFC 1847: Security multipart. 15.
2186 * RFC 1896: text/enriched. 5.
2187 * RFC 1922: RFC 1922. 15.
2188 * RFC 1947: iso-8859-7. 13.
2189 * RFC 1991: PGP. 15.
2190 * RFC 2015: PGP/MIME. 15.
2191 * RFC 2045: RFC 2045. 5.
2192 * RFC 2046: RFC 2046. 5.
2193 * RFC 2047: encoded-word. 7.
2194 * RFC 2047: encoded-word. 8.
2195 * RFC 2048: RFC 2048. 5.
2196 * RFC 2049: RFC 2049. 5.
2197 * RFC 821: RFC 821. 5.
2198 * RFC 822: RFC 822. 13.
2199 * RFC 934: RFC 934. 11.
2201 * Security multipart: Security multipart. 15.
2203 * Standards Track: encoded-word. 8.
2204 * Standards Track: PGP/MIME. 15.
2205 * Standards Track: RFC 2045. 5.
2206 * Standards Track: RFC 2046. 5.
2207 * Standards Track: RFC 2048. 5.
2208 * Standards Track: RFC 2049. 5.
2209 * Standards Track: Security multipart. 15.
2210 * STD 10: RFC 821. 5.
2211 * STD 11: RFC 822. 13.
2213 * subtype: Content-Type field. 20.
2214 * subtype: media type. 8.
2215 * text: media type. 13.
2216 * text/enriched: text/enriched. 5.
2217 * text/plain: text/plain. 5.
2218 * tm oomori package: tm-MUA. 7.
2219 * tm-gnus: tm-MUA. 13.
2220 * tm-mh-e: tm-MUA. 10.
2221 * tm-rmail: tm-MUA. 19.
2222 * tm-setup: tm-setup. 5.
2223 * tm-vm: tm-MUA. 17.
2224 * type: Content-Type field. 20.
2225 * type: media type. 7.
2226 * us-ascii: us-ascii. 14.
2227 * USENET: RFC 1036. 9.
2228 * video: media type. 19.
2229 * vm: setting for VM. 6.
2230 * XEmacs/mule: MULE. 23.
2231 * x-token: media type. 29.
2234 Extensions: MIME. 6.
2236 message: RFC 822. 10.
2242 File: tm-en.info, Node: Variable Index, Prev: Concept Index, Up: Top
2250 * mime-setup-default-signature-key: signature. 46.
2251 * mime-setup-signature-key-alist: signature. 30.
2252 * mime-setup-use-signature: signature. 23.
2256 Node: Introduction
\7f583
2257 Node: Glossary
\7f1260
2260 Node: 94-character set
\7f6629
2261 Node: 96-character set
\7f6991
2262 Node: 94x94-character set
\7f7337
2267 Node: cn-big5
\7f9531
2268 Node: CNS 11643
\7f10094
2269 Node: coded character set
\7f10834
2270 Node: code extension
\7f11164
2271 Node: Content-Disposition
\7f11448
2272 Node: Content-Type field
\7f11885
2274 Node: encoded-word
\7f13154
2275 Node: encapsulation
\7f13566
2276 Node: euc-kr
\7f13854
2278 Node: GB 2312
\7f14527
2279 Node: GB 8565.2
\7f14974
2280 Node: graphic character set
\7f15403
2281 Node: hz-gb2312
\7f15622
2282 Node: ISO 2022
\7f16448
2283 Node: iso-2022-cn
\7f16849
2284 Node: iso-2022-cn-ext
\7f17310
2285 Node: iso-2022-jp
\7f17950
2286 Node: iso-2022-jp-2
\7f18654
2287 Node: iso-2022-kr
\7f19065
2288 Node: ISO 646
\7f19494
2289 Node: ISO 8859-1
\7f19779
2290 Node: iso-8859-1
\7f20093
2291 Node: ISO 8859-2
\7f20556
2292 Node: iso-8859-2
\7f20873
2293 Node: ISO 8859-3
\7f21336
2294 Node: ISO 8859-4
\7f21653
2295 Node: ISO 8859-5
\7f21970
2296 Node: iso-8859-5
\7f22296
2297 Node: ISO 8859-6
\7f22727
2298 Node: ISO 8859-7
\7f23046
2299 Node: iso-8859-7
\7f23364
2300 Node: ISO 8859-8
\7f23900
2301 Node: ISO 8859-9
\7f24219
2302 Node: ISO-IR-165
\7f24536
2303 Node: JIS X0201
\7f25008
2304 Node: JIS C6226
\7f25690
2305 Node: JIS X0208
\7f25936
2306 Node: JIS X0212
\7f27382
2307 Node: koi8-r
\7f27698
2308 Node: KS C5601
\7f28157
2309 Node: media type
\7f28567
2310 Node: message
\7f29497
2311 Node: message/rfc822
\7f29732
2312 Node: method
\7f30109
2314 Node: MIME charset
\7f31558
2318 Node: multipart
\7f33285
2319 Node: multipart/alternative
\7f34025
2320 Node: multipart/digest
\7f34483
2321 Node: multipart/encrypted
\7f35130
2322 Node: multipart/mixed
\7f35421
2323 Node: multipart/parallel
\7f35747
2324 Node: multipart/signed
\7f36188
2326 Node: PGP-kazu
\7f37132
2327 Node: PGP/MIME
\7f37754
2328 Node: Quoted-Printable
\7f38365
2329 Node: RFC 821
\7f38749
2330 Node: RFC 822
\7f38945
2331 Node: RFC 934
\7f39347
2332 Node: RFC 1036
\7f39767
2333 Node: RFC 1153
\7f40166
2334 Node: RFC 1557
\7f40331
2335 Node: RFC 1922
\7f40691
2336 Node: RFC 2045
\7f41312
2337 Node: RFC 2046
\7f41623
2338 Node: RFC 2048
\7f41912
2339 Node: RFC 2049
\7f42227
2340 Node: plain text
\7f42541
2341 Node: Security multipart
\7f42831
2342 Node: text/enriched
\7f43450
2343 Node: text/plain
\7f43720
2344 Node: tm-kernel
\7f44200
2345 Node: tm-MUA
\7f44618
2346 Node: us-ascii
\7f45064
2347 Node: Setting
\7f45666
2348 Node: mime-setup
\7f46265
2349 Node: signature
\7f46766
2350 Node: Notice about GNUS
\7f48311
2351 Node: tm-setup
\7f49187
2352 Node: setting for VM
\7f49735
2353 Node: manual setting
\7f50047
2354 Node: Bug report
\7f50649
2355 Node: Concept Index
\7f52082
2356 Node: Variable Index
\7f62552