1 This is Info file tm-en.info, produced by Makeinfo-1.63 from the input
5 File: tm-en.info, Node: Top, Next: Introduction, Prev: (dir), Up: (dir)
7 tm 7.100 Manual (English Version)
8 *********************************
10 This file documents tm, a MIME package for GNU Emacs.
14 * Introduction:: What is tm?
16 * Bug report:: How to report bug and about mailing list of tm
22 File: tm-en.info, Node: Introduction, Next: Setting, Prev: Top, Up: Top
27 The tm package is a set of modules to enjoy MIME on GNU Emacs. Using
30 * playback or view the MIME messages using tm-view
32 * compose MIME message using tm-edit
34 * use the enhanced MIME features with mh-e, GNUS, Gnus, RMAIL and VM
38 Please read following about each topics:
40 * tm-MUA for Gnus (*Note (gnus-mime-en)::)
42 * tm-MUA for GNUS (*Note (tm-gnus-en)::)
44 * tm-MUA for mh-e (*Note (tm-mh-e-en)::)
46 * tm-MUA for VM (*Note (tm-vm-en)::)
48 * mime/viewer-mode (*Note (tm-view-en)::)
50 * mime/editor-mode (*Note (tm-edit-en)::)
57 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::
85 * GB 2312:: GB 2312-1980
86 * GB 8565.2:: GB 8565.2-1988
87 * graphic character set:: Graphic Character Set
109 * ISO-IR-165:: ISO-IR-165, CCITT Extended GB
111 * JIS C6226:: JIS C6226-1978
113 * JIS X0212:: JIS X0212-1990
115 * KS C5601:: KS C5601-1987
125 * multipart:: Multipart
126 * multipart/alternative::
128 * multipart/encrypted::
130 * multipart/parallel::
148 * Security multipart::
151 * 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
166 127, and space represented by 32, and graphic characters between 33 ..
167 236 are called *7bit (textual) string*.
169 Traditional Internet MTA (*Note MTA::) can translate 7bit data, so
170 it is no need to translate by Quoted-Printable (*Note
171 Quoted-Printable::) or 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
178 encoded by Quoted-Printable.
181 File: tm-en.info, Node: 8bit, Next: 94-character set, Prev: 7bit, Up: Glossary
186 *8bit* means any integer between 0 .. 255.
188 Any data represented by 8bit integers is called *8bit data*.
190 Textual string consisted of Control characters between 0 .. 31, 127,
191 and 128 .. 159, and space represented by 32, and graphic characters
192 between 33 .. 236 and 160 .. 255 are called *8bit (textual) string*.
194 For example, iso-8859-1 (*Note iso-8859-1::) or euc-kr (*Note
195 euc-kr::) are coded-character-set represented by 8bit textual string.
197 Traditional Internet MTA (*Note MTA::) can translate only 7bit
198 (*Note 7bit::) data, so if a 8bit data will be translated such MTA, it
199 must be encoded by Quoted-Printable (*Note Quoted-Printable::) or Base64
202 However 8bit MTA are increasing today.
204 However if there are too long lines, it can not translate by 8bit MTA
205 even if it is 8bit data. RFC 2045 (*Note RFC 2045::) require lines in
206 8bit data must be less than 998 bytes. So if a "8bit data" has a line
207 more than 999 bytes, it is regarded as binary (*Note binary::), so it
208 must be encoded by Base64 or Quoted-Printable.
211 File: tm-en.info, Node: 94-character set, Next: 96-character set, Prev: 8bit, Up: Glossary
216 *94-character set* is a kind of 1 byte graphic character set (*Note
217 graphic character set::), each characters are in positions 02/01 (33)
218 to 07/14 (126) or 10/01 (161) to 15/14 (254). (ex. ASCII (*Note
219 ASCII::), JIS X0201-Latin)
222 File: tm-en.info, Node: 96-character set, Next: 94x94-character set, Prev: 94-character set, Up: Glossary
227 *96-character set* is a kind of 1 byte graphic character set (*Note
228 graphic character set::), each characters are in positions 02/00 (32)
229 to 07/15 (126) or 10/00 (160) to 15/15 (255). (ex. ISO 8859)
232 File: tm-en.info, Node: 94x94-character set, Next: ASCII, Prev: 96-character set, Up: Glossary
237 *94x94-character set* is a kind of 2 byte graphic character set
238 (*Note graphic character set::), each bytes are in positions 02/01 (33)
239 to 07/14 (126) or 10/01 (161) to 15/14 (254). (ex. JIS X0208 (*Note
240 JIS X0208::), GB 2312 (*Note GB 2312::))
243 File: tm-en.info, Node: ASCII, Next: Base64, Prev: 94x94-character set, Up: Glossary
248 *ASCII* is a 94-character set (*Note 94-character set::) contains
249 primary latin characters (A-Z, a-z), numbers and some characters. It is
250 a standard of the United States of America. It is a variant of ISO 646
254 "Coded Character Set - 7-Bit American Standard Code for Information
255 Interchange", ANSI X3.4:1986.
258 File: tm-en.info, Node: Base64, Next: binary, Prev: ASCII, Up: Glossary
263 *Base64* is a transfer encoding method of MIME (*Note MIME::)
264 defined in RFC 2045 (*Note RFC 2045::).
266 The encoding process represents 24-bit groups of input bits as output
267 strings of 4 encoded characters. Encoded characters represent integer 0
268 .. 63 or *pad*. Base64 data must be 4 * n bytes, so pad is used to
271 These 65 characters are subset of all versions of ISO 646, including
272 US-ASCII, and all versions of EBCDIC. So it is safe even if it is
273 translated by non-Internet gateways.
276 File: tm-en.info, Node: binary, Next: cn-gb, Prev: Base64, Up: Glossary
281 Any byte stream is called *binary*.
283 It does not require structureof lines. It differs from from 8bit
286 In addition, if line structured data contain too long line (more than
287 998 bytes), it is regarded as binary.
290 File: tm-en.info, Node: cn-gb, Next: cn-big5, Prev: binary, Up: Glossary
295 A MIME charset (*Note MIME charset::) for simplified Chinese mainly
296 used in the Chinese mainland.
298 It is a 8bit (*Note 8bit::) coded character set (*Note coded
299 character set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII
300 (*Note ASCII::) to combine GB 2312 (*Note GB 2312::).
302 It is defined in RFC 1922 (*Note RFC 1922::).
305 File: tm-en.info, Node: cn-big5, Next: CNS 11643, Prev: cn-gb, Up: Glossary
310 A MIME charset (*Note MIME charset::) for traditional Chinese mainly
311 used in Taiwan and Hon Kong.
313 It is a 8bit (*Note 8bit::) coded character set (*Note coded
314 character set::) not based on ISO 2022 (*Note ISO 2022::). It is a
317 It is defined in RFC 1922 (*Note RFC 1922::).
322 Institute for Information Industry, "Chinese Coded Character Set in
323 Computer", March 1984.
325 It corresponds to CNS 11643 (*Note CNS 11643::).
328 File: tm-en.info, Node: CNS 11643, Next: coded character set, Prev: cn-big5, Up: Glossary
333 Graphic character sets (*Note graphic character set::) for Chinese
334 mainly written by traditional Chinese mainly used in Taiwan and Hong
335 Kong. It is a standard of Taiwan. Currently there are seven
336 94x94-character set (*Note 94x94-character set::).
338 Final byte of ISO 2022 (*Note ISO 2022::) are following:
362 "Standard Interchange Code for Generally-Used Chinese Characters",
366 File: tm-en.info, Node: coded character set, Next: code extension, Prev: CNS 11643, Up: Glossary
368 Coded character set, Character code
369 -----------------------------------
371 A set of unambiguous rules that establishes a character set and the
372 one-to-one relationship between the characters of the set and their bit
376 File: tm-en.info, Node: code extension, Next: Content-Disposition, Prev: coded character set, Up: Glossary
381 The techniques for the encoding of characters that are not included
382 in the character set of a given code. (ex. ISO 2022 (*Note ISO 2022::))
385 File: tm-en.info, Node: Content-Disposition, Next: Content-Type field, Prev: code extension, Up: Glossary
387 Content-Disposition field
388 -------------------------
390 A field to specify presentation of entity or file name. It is an
391 extension for MIME (*Note MIME::).
394 E R. Troost and S. Dorner, "Communicating Presentation Information
395 in Internet Messages: The Content-Disposition Header", June 1995,
399 File: tm-en.info, Node: Content-Type field, Next: Emacs, Prev: Content-Disposition, Up: Glossary
404 Header field to represent information about body, such as media type
405 (*Note media type::), MIME charset (*Note MIME charset::). It is
406 defined in RFC 2045 (*Note RFC 2045::).
409 Historically, Content-Type field was proposed in RFC 1049. In it,
410 Content-Type did not distinguish type and subtype. However MIME
411 parser may be able to accept RFC 1049 based Content-Type as
414 Content-Type field is defined as following:
416 "Content-Type" ":" *type* "/" *subtype* *( ";" *parameter* )
420 Content-Type: image/jpeg
422 Content-Type: text/plain; charset=iso-2022-jp
425 A part does not have content-type field is regarded as
427 Content-Type: text/plain; charset=us-ascii
429 (cf. *Note us-ascii::)
431 And a part has unknown type/subtype is regarded as
433 Content-Type: application/octet-stream
437 File: tm-en.info, Node: Emacs, Next: encoded-word, Prev: Content-Type field, Up: Glossary
442 In this document, `Emacs' means GNU Emacs released by FSF, and
443 `emacs' means any variants of GNU Emacs.
446 File: tm-en.info, Node: encoded-word, Next: encapsulation, Prev: Emacs, Up: Glossary
451 Representation non ASCII (*Note ASCII::) characters in header. It is
452 defined in *RFC 2047*.
455 K. Moore, "MIME (Multipurpose Internet Mail Extensions) Part Three:
456 Message Header Extensions for Non-ASCII Text", November 1996,
457 Standards Track (obsolete RFC 1521,1522,1590).
460 File: tm-en.info, Node: encapsulation, Next: entity, Prev: encoded-word, Up: Glossary
465 Method to insert whole Internet message (*Note RFC 822::) into
466 another Internet message.
468 For example, it is used to forward a message.
470 (cf. *Note message/rfc822::)
473 File: tm-en.info, Node: entity, Next: euc-kr, Prev: encapsulation, Up: Glossary
478 Header fields and contents of a message or one of the parts in the
479 body of a multipart (*Note multipart::) entity.
482 In this document, `entity' might be called "part".
485 File: tm-en.info, Node: euc-kr, Next: FTP, Prev: entity, Up: Glossary
490 A MIME charset (*Note MIME charset::) for Korean.
492 It is a 8bit (*Note 8bit::) coded character set (*Note coded
493 character set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII
494 (*Note ASCII::) to combine KS C5601 (*Note KS C5601::).
496 It is defined in RFC 1557 (*Note RFC 1557::).
501 Korea Industrial Standards Association, "Hangul Unix Environment",
505 File: tm-en.info, Node: FTP, Next: GB 2312, Prev: euc-kr, Up: Glossary
511 Postel, J. and J. Reynolds, "File Transfer Protocol", October 1985,
515 File: tm-en.info, Node: GB 2312, Next: GB 8565.2, Prev: FTP, Up: Glossary
520 A 94x94-character set (*Note 94x94-character set::) for Chinese
521 mainly written by simplified Chinese mainly used in the Chinese
522 mainland. It is a standard of China.
524 Final byte of ISO 2022 (*Note ISO 2022::) is 04/01 (`A').
527 "Code of Chinese Graphic Character Set for Information Interchange
528 - Primary Set", GB 2312:1980.
531 File: tm-en.info, Node: GB 8565.2, Next: graphic character set, Prev: GB 2312, Up: Glossary
536 A 94x94-character set (*Note 94x94-character set::) for Chinese as
537 supplement to GB 2312 (*Note GB 2312::). It is a standard of China.
540 "Information Processing - Coded Character Sets for Text
541 Communication - Part 2: Graphic Characters used with Primary Set",
545 File: tm-en.info, Node: graphic character set, Next: hz-gb2312, Prev: GB 8565.2, Up: Glossary
547 Graphic Character Set
548 ---------------------
550 Coded character set (*Note coded character set::) for graphic
554 File: tm-en.info, Node: hz-gb2312, Next: ISO 2022, Prev: graphic character set, Up: Glossary
559 A MIME charset (*Note MIME charset::) for simplified Chinese mainly
560 used in the Chinese mainland.
562 It extends ASCII (*Note ASCII::) to combine GB 2312 (*Note GB
563 2312::), its technique is like iso-2022-jp (*Note iso-2022-jp::), but
564 it is designed to be ASCII printable to use special form for ESC
565 sequence to designate GB 2312 to G0.
567 It is defined in RFC 1842 and 1843.
570 Y. Wei, Y. Zhang, J. Li, J. Ding and Y. Jiang, "ASCII Printable
571 Characters-Based Chinese Character Encoding for Internet Messages",
572 August 1995, Informational.
575 F. Lee, "HZ - A Data Format for Exchanging Files of Arbitrarily
576 Mixed Chinese and ASCII characters", August 1995, Informational.
579 File: tm-en.info, Node: ISO 2022, Next: iso-2022-cn, Prev: hz-gb2312, Up: Glossary
584 It is a standard for character code structure and code extension
585 (*Note code extension::) technique.
588 International Organization for Standardization (ISO), "Information
589 Processing: ISO 7-bit and 8-bit coded character sets: Code
590 extension techniques", ISO/IEC 2022:1994.
593 File: tm-en.info, Node: iso-2022-cn, Next: iso-2022-cn-ext, Prev: ISO 2022, Up: Glossary
598 A MIME charset (*Note MIME charset::) for Chinese.
600 It is a 7bit (*Note 7bit::) coded character set (*Note coded
601 character set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII
602 (*Note ASCII::) to combine GB 2312 (*Note GB 2312::) and/or CNS 11643
603 plain 1, plain 2 (*Note CNS 11643::).
605 It is defined in RFC 1922 (*Note RFC 1922::).
608 File: tm-en.info, Node: iso-2022-cn-ext, Next: iso-2022-jp, Prev: iso-2022-cn, Up: Glossary
613 A MIME charset (*Note MIME charset::) for Chinese.
615 It is a 7bit (*Note 7bit::) coded character set (*Note coded
616 character set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII
617 (*Note ASCII::) to combine GB 2312 (*Note GB 2312::), CNS 11643 plain 1
618 .. 7 (*Note CNS 11643::), ISO-IR-165 (*Note ISO-IR-165::) and other
619 Chinese graphic character sets.
621 It is defined in RFC 1922 (*Note RFC 1922::).
624 MULE 2.3 and current XEmacs/mule can not use it correctly.
626 Emacs/mule can use it.
629 File: tm-en.info, Node: iso-2022-jp, Next: iso-2022-jp-2, Prev: iso-2022-cn-ext, Up: Glossary
634 A MIME charset (*Note MIME charset::) for Japanese.
636 It is a 7bit (*Note 7bit::) coded character set (*Note coded
637 character set::) based on old ISO 2022 (*Note ISO 2022::). It switches
638 ASCII (*Note ASCII::), JIS X0201-Latin, JIS X0208-1978 (*Note JIS
639 C6226::) and JIS X0208-1983 (*Note JIS X0208::).
641 It is defined in RFC 1468.
644 JIS X0208-1997? will define it in annex as non-ISO 2022 (*Note ISO
647 [iso-2022-jp: RFC 1468]
648 Murai J., M. Crispin, and E. van der Poel, "Japanese Character
649 Encoding for Internet Messages", June 1993.
652 File: tm-en.info, Node: iso-2022-jp-2, Next: iso-2022-kr, Prev: iso-2022-jp, Up: Glossary
657 A MIME charset (*Note MIME charset::), which is a multilingual
658 extension of iso-2022-jp (*Note iso-2022-jp::).
660 It is defined in RFC 1554.
662 [iso-2022-jp-2: RFC 1554]
663 Ohta M. and Handa K., "ISO-2022-JP-2: Multilingual Extension of
664 ISO-2022-JP", December 1993, Informational.
667 File: tm-en.info, Node: iso-2022-kr, Next: ISO 646, Prev: iso-2022-jp-2, Up: Glossary
672 A MIME charset (*Note MIME charset::) for Korean language (Hangul
675 It is based on ISO 2022 (*Note ISO 2022::) code extension (*Note
676 code extension::) technique to extend ASCII (*Note ASCII::) to use KS
677 C5601 (*Note KS C5601::) as 7bit (*Note 7bit::) text.
679 It is defined in RFC 1557 (*Note RFC 1557::).
682 File: tm-en.info, Node: ISO 646, Next: ISO 8859-1, Prev: iso-2022-kr, Up: Glossary
688 International Organization for Standardization (ISO), "Information
689 technology: ISO 7-bit coded character set for information
690 interchange", ISO/IEC 646:1991.
693 File: tm-en.info, Node: ISO 8859-1, Next: iso-8859-1, Prev: ISO 646, Up: Glossary
699 International Organization for Standardization (ISO), "Information
700 Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
701 1: Latin Alphabet No.1", ISO 8859-1:1987.
704 File: tm-en.info, Node: iso-8859-1, Next: ISO 8859-2, Prev: ISO 8859-1, Up: Glossary
709 *iso-8859-1* is a MIME charset (*Note MIME charset::) for
710 west-European languages written by Latin script.
712 It is a 8bit (*Note 8bit::) coded character set (*Note coded
713 character set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII
714 (*Note ASCII::) to combine ISO 8859-1 (*Note ISO 8859-1::).
716 It is defined in RFC 2046 (*Note RFC 2046::).
719 File: tm-en.info, Node: ISO 8859-2, Next: iso-8859-2, Prev: iso-8859-1, Up: Glossary
725 International Organization for Standardization (ISO), "Information
726 Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
727 2: Latin alphabet No.2", ISO 8859-2:1987.
730 File: tm-en.info, Node: iso-8859-2, Next: ISO 8859-3, Prev: ISO 8859-2, Up: Glossary
735 *iso-8859-2* is a MIME charset (*Note MIME charset::) for
736 east-European languages written by Latin script.
738 It is a 8bit (*Note 8bit::) coded character set (*Note coded
739 character set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII
740 (*Note ASCII::) to combine ISO 8859-2 (*Note ISO 8859-2::).
742 It is defined in RFC 2046 (*Note RFC 2046::).
745 File: tm-en.info, Node: ISO 8859-3, Next: ISO 8859-4, Prev: iso-8859-2, Up: Glossary
751 International Organization for Standardization (ISO), "Information
752 Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
753 3: Latin alphabet No.3", ISO 8859-3:1988.
756 File: tm-en.info, Node: ISO 8859-4, Next: ISO 8859-5, Prev: ISO 8859-3, Up: Glossary
762 International Organization for Standardization (ISO), "Information
763 Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
764 4: Latin alphabet No.4", ISO 8859-4:1988.
767 File: tm-en.info, Node: ISO 8859-5, Next: iso-8859-5, Prev: ISO 8859-4, Up: Glossary
773 International Organization for Standardization (ISO), "Information
774 Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
775 5: Latin/Cyrillic alphabet", ISO 8859-5:1988.
778 File: tm-en.info, Node: iso-8859-5, Next: ISO 8859-6, Prev: ISO 8859-5, Up: Glossary
783 *iso-8859-5* is a MIME charset (*Note MIME charset::) for Cyrillic
786 It is a 8bit (*Note 8bit::) coded character set (*Note coded
787 character set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII
788 (*Note ASCII::) to combine ISO 8859-5 (*Note ISO 8859-5::).
790 It is defined in RFC 2046 (*Note RFC 2046::).
793 File: tm-en.info, Node: ISO 8859-6, Next: ISO 8859-7, Prev: iso-8859-5, Up: Glossary
799 International Organization for Standardization (ISO), "Information
800 Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
801 6: Latin/Arabic alphabet", ISO 8859-6:1987.
804 File: tm-en.info, Node: ISO 8859-7, Next: iso-8859-7, Prev: ISO 8859-6, Up: Glossary
810 International Organization for Standardization (ISO), "Information
811 Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
812 7: Latin/Greek alphabet", ISO 8859-7:1987.
815 File: tm-en.info, Node: iso-8859-7, Next: ISO 8859-8, Prev: ISO 8859-7, Up: Glossary
820 *iso-8859-7* is a MIME charset (*Note MIME charset::) for Greek
823 It is a 8bit (*Note 8bit::) coded character set (*Note coded
824 character set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII
825 (*Note ASCII::) to combine ISO 8859-7 (*Note ISO 8859-7::).
827 It is defined in RFC 1947.
829 [iso-8859-7: RFC 1947]
830 D. Spinellis, "Greek Character Encoding for Electronic Mail
831 Messages", May 1996, Informational.
834 File: tm-en.info, Node: ISO 8859-8, Next: ISO 8859-9, Prev: iso-8859-7, Up: Glossary
840 International Organization for Standardization (ISO), "Information
841 Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
842 8: Latin/Hebrew alphabet", ISO 8859-8:1988.
845 File: tm-en.info, Node: ISO 8859-9, Next: ISO-IR-165, Prev: ISO 8859-8, Up: Glossary
851 International Organization for Standardization (ISO), "Information
852 Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
853 9: Latin alphabet No.5", ISO 8859-9:1990.
856 File: tm-en.info, Node: ISO-IR-165, Next: JIS X0201, Prev: ISO 8859-9, Up: Glossary
858 ISO-IR-165, CCITT Extended GB
859 -----------------------------
861 A 94x94-character set (*Note 94x94-character set::) for Chinese
862 mainly written by simplified Chinese mainly used in the Chinese mainland
865 It consists of GB 2312 (*Note GB 2312::), GB 8565.2 (*Note GB
866 8565.2::) and additional 150 characters.
868 Final byte of ISO 2022 (*Note ISO 2022::) is 04/05 (`E').
871 File: tm-en.info, Node: JIS X0201, Next: JIS C6226, Prev: ISO-IR-165, Up: Glossary
876 It defines two 94-character set (*Note 94-character set::), for Latin
877 script (a variant of ISO 646 (*Note ISO 646::)) and Katakana script, and
878 7bit and 8bit coded character set (*Note coded character set::)s.
880 It was renamed from *JIS C6220-1976*.
883 Japanese Standards Association, "Code for Information Interchange",
886 In addition, revised version will be published in 1997.
889 Japanese Standards Association, "7-bit and 8-bit coded character
890 sets for information interchange", JIS X 0201:1997? draft.
893 File: tm-en.info, Node: JIS C6226, Next: JIS X0208, Prev: JIS X0201, Up: Glossary
898 A 94x94-character set (*Note 94x94-character set::) for Japanese.
899 It was renamed to JIS X0208-1978.
901 (cf. *Note JIS X0208::)
904 File: tm-en.info, Node: JIS X0208, Next: JIS X0212, Prev: JIS C6226, Up: Glossary
909 A 94x94-character set (*Note 94x94-character set::) for Japanese.
910 Japanese standard. It was published in 1978, and revised in 1983 and
911 1990. In the Internet message, 1983 edition is major.
913 JIS X0208 contains some symbols, numbers, primary Latin script,
914 Hiragana script, Katakana script, Greek script, Cyrillic script, box
915 drawing parts, Kanji (Ideographic characters used in Japanese). Notice
916 that some symbols and box drawing parts were added in 1983 and some
917 Kanjis were changed or swapped code points. So 1978 edition and 1983
918 edition are regarded as different graphic character set.
920 1990 edition added some characters, so designation of 1990 edition
921 requires `identify revised registration' sequence, ESC 02/06 4/0 as
922 prefix of designation sequence.
925 Japanese Standards Association, "Code of the Japanese graphic
926 character set for information interchange", JIS C6226:1978.
928 [JIS X0208-1983,1990]
929 Japanese Standards Association, "Code of the Japanese graphic
930 character set for information interchange", JIS X0208:1983,1990.
932 In addition, revised version will be published in 1997. (It does not
933 change graphic character set)
936 Japanese Standards Association, "7-bit and 8-bit double byte coded
937 Kanji sets for information interchange", JIS X 0208:1997? draft.
940 File: tm-en.info, Node: JIS X0212, Next: koi8-r, Prev: JIS X0208, Up: Glossary
945 A 94x94-character set (*Note 94x94-character set::) for Japanese as
946 supplement to JIS X0208 (*Note JIS X0208::). It is a standard of Japan.
948 Final byte of ISO 2022 (*Note ISO 2022::) is 04/04 (`D').
951 File: tm-en.info, Node: koi8-r, Next: KS C5601, Prev: JIS X0212, Up: Glossary
956 A MIME charset (*Note MIME charset::) for Cyrillic script for
957 Russian or other languages.
959 It is a 1 byte 8bit (*Note 8bit::) coded character set (*Note coded
960 character set::), not based on ISO 2022 (*Note ISO 2022::). It is a
963 It is defined in RFC 1489.
966 A. Chernov, "Registration of a Cyrillic Character Set", July 1993.
969 File: tm-en.info, Node: KS C5601, Next: media type, Prev: koi8-r, Up: Glossary
974 A 94x94-character set (*Note 94x94-character set::) for Korean
975 language (Hangul script). Korean Standard. Final byte of ISO 2022
976 (*Note ISO 2022::) is 04/03 (`C').
979 Korea Industrial Standards Association, "Code for Information
980 Interchange (Hangul and Hanja)", KS C 5601:1987.
983 File: tm-en.info, Node: media type, Next: message, Prev: KS C5601, Up: Glossary
988 *media type* specifies the nature of the data in the body of MIME
989 (*Note MIME::) entity (*Note entity::). It consists of *type* and
990 *subtype*. It is defined in RFC 2046 (*Note RFC 2046::).
992 Currently there are following types:
1004 * *multipart* (*Note multipart::)
1008 And there are various subtypes, for example,
1009 application/octet-stream, audio/basic, image/jpeg, multipart/mixed
1010 (*Note multipart/mixed::), text/plain (*Note text/plain::),
1013 You can refer registered media types at MEDIA TYPES
1014 (ftp://ftp.isi.edu/in-notes/iana/assignments/media-types).
1016 In addition, you can use private type or subtype using *x-token*,
1017 which as the prefix `x-'. However you can not use them in public.
1019 (cf. *Note Content-Type field::)
1022 File: tm-en.info, Node: message, Next: message/rfc822, Prev: media type, Up: Glossary
1027 In this document, it means mail defined in RFC 822 (*Note RFC 822::)
1028 and news message defined in RFC 1036 (*Note RFC 1036::).
1031 File: tm-en.info, Node: message/rfc822, Next: method, Prev: message, Up: Glossary
1036 *message/rfc822* indicates that the body contains an encapsulated
1037 message, with the syntax of an RFC 822 (*Note RFC 822::) message. It is
1038 the replacement of traditional RFC 934 (*Note RFC 934::) encapsulation.
1039 It is defined in RFC 2046 (*Note RFC 2046::).
1042 File: tm-en.info, Node: method, Next: MIME, Prev: message/rfc822, Up: Glossary
1047 Application program of tm-view to process for specified media type
1048 (*Note media type::) when user plays an entity.
1050 There are two kinds of methods, *internal method* and *external
1051 method*. Internal method is written by Emacs Lisp. External method is
1052 written by C or script languages and called by asynchronous process
1055 (cf. *Note (tm-view-en)method::)
1058 File: tm-en.info, Node: MIME, Next: MIME charset, Prev: method, Up: Glossary
1063 MIME stands for *Multipurpose Internet Mail Extensions*, it is an
1064 extension for RFC 822 (*Note RFC 822::).
1066 According to RFC 2045:
1068 STD 11, RFC 822, defines a message representation protocol specifying
1069 considerable detail about US-ASCII message headers, and leaves the
1070 message content, or message body, as flat US-ASCII text. This set of
1071 documents, collectively called the Multipurpose Internet Mail
1072 Extensions, or MIME, redefines the format of messages to allow for
1074 1. textual message bodies in character sets other than US-ASCII,
1076 2. an extensible set of different formats for non-textual message
1079 3. multi-part message bodies, and
1081 4. textual header information in character sets other than US-ASCII.
1083 It is defined in RFC 2045 (*Note RFC 2045::), RFC 2046 (*Note RFC
1084 2046::), RFC 2047 (*Note encoded-word::), RFC 2048 (*Note RFC 2048::)
1085 and RFC 2049 (*Note RFC 2049::).
1088 File: tm-en.info, Node: MIME charset, Next: MTA, Prev: MIME, Up: Glossary
1093 Coded character set (*Note coded character set::) used in
1094 Content-Type field (*Note Content-Type field::) or charset parameter of
1095 encoded-word (*Note encoded-word::).
1097 It is defined in RFC 2045 (*Note RFC 2045::).
1099 iso-2022-jp (*Note iso-2022-jp::) or euc-kr (*Note euc-kr::) are
1100 kinds of it. (In this document, MIME charsets are written by small
1101 letters to distinguish graphic character set (*Note graphic character
1102 set::). For example, ISO 8859-1 is a graphic character set, and
1103 iso-8859-1 is a MIME charset)
1106 File: tm-en.info, Node: MTA, Next: MUA, Prev: MIME charset, Up: Glossary
1111 *Message Transfer Agent*. It means mail transfer programs (ex.
1112 sendmail) and news servers.
1117 File: tm-en.info, Node: MUA, Next: MULE, Prev: MTA, Up: Glossary
1122 *Message User Agent*. It means mail readers and news readers.
1127 File: tm-en.info, Node: MULE, Next: multipart, Prev: MUA, Up: Glossary
1132 Multilingual extension of GNU Emacs (*Note Emacs::) by HANDA
1136 Nishikimi M., Handa K. and Tomura S., "Mule: MULtilingual
1137 Enhancement to GNU Emacs", Proc. of INET'93, August, 1993.
1139 Now, FSF and HANDA Ken'ichi et al. are working to merge MULE feature
1140 into Emacs, there is alpha version of mule merged emacs
1141 (ftp://etlport.etl.go.jp/pub/mule/mule-19.33-delta.taz).
1143 In addition, there is XEmacs with mule feature.
1145 So now, there are 3 kinds of mule variants.
1147 In this document, *mule* means any mule variants, *MULE* means
1148 original MULE (..2.3), *Emacs/mule* means mule merged Emacs,
1149 *XEmacs/mule* means XEmacs with mule feature.
1152 File: tm-en.info, Node: multipart, Next: multipart/alternative, Prev: MULE, Up: Glossary
1157 *multipart* means media type (*Note media type::) to insert multiple
1158 entities (*Note entity::) in a single body. Or it also indicates a
1159 message consists of multiple entities.
1161 There are following subtypes registered in RFC 2046 (*Note RFC
1164 * multipart/mixed (*Note multipart/mixed::)
1166 * multipart/alternative (*Note multipart/alternative::)
1168 * multipart/digest (*Note multipart/digest::)
1170 * multipart/parallel (*Note multipart/parallel::)
1172 and registered in RFC 1847 (*Note Security multipart::):
1174 * multipart/signed (*Note multipart/signed::)
1176 * multipart/encrypted (*Note multipart/encrypted::)
1179 File: tm-en.info, Node: multipart/alternative, Next: multipart/digest, Prev: multipart, Up: Glossary
1181 multipart/alternative
1182 ---------------------
1184 *multipart/digest* is one of multipart (*Note multipart::) media
1185 types. This type is syntactically identical to multipart/mixed (*Note
1186 multipart/mixed::), but the semantics are different. In particular,
1187 each of the body parts is an "alternative" version of the same
1190 (cf. *Note RFC 2046::)
1193 File: tm-en.info, Node: multipart/digest, Next: multipart/encrypted, Prev: multipart/alternative, Up: Glossary
1198 *multipart/digest* is one of multipart (*Note multipart::) media
1199 types. This type is syntactically identical to multipart/mixed (*Note
1200 multipart/mixed::), but the semantics are different. In particular, in
1201 a digest, the default Content-Type value for a body part is changed
1202 from text/plain (*Note text/plain::) to message/rfc822 (*Note
1205 This is the replacement of traditional RFC 1153 (*Note RFC 1153::)
1206 based encapsulation (*Note encapsulation::).
1208 (cf. *Note RFC 2046::)
1211 File: tm-en.info, Node: multipart/encrypted, Next: multipart/mixed, Prev: multipart/digest, Up: Glossary
1216 It is a Security multipart (*Note Security multipart::) defined in
1217 RFC 1847, used to represent encrypted message.
1219 (cf. *Note PGP/MIME::)
1222 File: tm-en.info, Node: multipart/mixed, Next: multipart/parallel, Prev: multipart/encrypted, Up: Glossary
1227 Primary and default subtype of multipart (*Note multipart::), it is
1228 used when the body parts are independent and need to be bundled in a
1231 (cf. *Note RFC 2046::)
1234 File: tm-en.info, Node: multipart/parallel, Next: multipart/signed, Prev: multipart/mixed, Up: Glossary
1239 *multipart/parallel* is a subtype of multipart (*Note multipart::).
1240 This type is syntactically identical to multipart/mixed (*Note
1241 multipart/mixed::), but the semantics are different. In particular, in
1242 a parallel entity, the order of body parts is not significant.
1244 (cf. *Note RFC 2046::)
1247 File: tm-en.info, Node: multipart/signed, Next: PGP, Prev: multipart/parallel, Up: Glossary
1252 It is a Security multipart (*Note Security multipart::) defined in
1253 RFC 1847, used to represent signed message.
1255 (cf. *Note PGP/MIME::)
1258 File: tm-en.info, Node: PGP, Next: PGP-kazu, Prev: multipart/signed, Up: Glossary
1263 A public key encryption program by Phil Zimmermann. It provides
1264 encryption and signature for message (*Note message::). PGP stands for
1265 *Pretty Good Privacy*.
1267 Traditional PGP uses RFC 934 (*Note RFC 934::) encapsulation (*Note
1268 encapsulation::). It is conflict with MIME (*Note MIME::). So
1269 PGP/MIME (*Note PGP/MIME::) is defined. On the other hand, PGP-kazu
1270 (*Note PGP-kazu::) was proposed to use PGP encapsulation in MIME. But
1274 D. Atkins, W. Stallings and P. Zimmermann, "PGP Message Exchange
1275 Formats", August 1996, Informational.
1278 File: tm-en.info, Node: PGP-kazu, Next: PGP/MIME, Prev: PGP, Up: Glossary
1283 In this document, *PGP-kazu* means a method to use traditional PGP
1284 encapsulation in MIME (*Note MIME::), proposed by YAMAMOTO Kazuhiko.
1286 PGP-kazu defines a media type (*Note media type::),
1289 In application/pgp entity, PGP encapsulation (*Note encapsulation::)
1290 is used. PGP encapsulation conflicts with MIME, so it requires
1291 PGP-processing to read as MIME message.
1293 It was obsoleted, so you should use PGP/MIME (*Note PGP/MIME::).
1294 However if you want to use traditional PGP message, it might be
1298 File: tm-en.info, Node: PGP/MIME, Next: Quoted-Printable, Prev: PGP-kazu, Up: Glossary
1303 PGP (*Note PGP::) and MIME (*Note MIME::) integration proposed by
1306 It is based on RFC 1847 (*Note Security multipart::), so it is
1307 harmonious with MIME, but it is not compatible with traditional PGP
1308 encapsulation. However MIME MUA can read PGP/MIME signed message even
1309 if it does not support PGP/MIME.
1311 PGP/MIME (*Note PGP/MIME::) will be standard of PGP message.
1313 [PGP/MIME: RFC 2015]
1314 M. Elkins, "MIME Security with Pretty Good Privacy (PGP)", October
1315 1996, Standards Track.
1318 File: tm-en.info, Node: Quoted-Printable, Next: RFC 821, Prev: PGP/MIME, Up: Glossary
1323 *Quoted-Printable* is a transfer encoding method of MIME (*Note
1324 MIME::) defined in RFC 2045 (*Note RFC 2045::).
1326 If the data being encoded are mostly US-ASCII text, the encoded form
1327 of the data remains largely recognizable by humans.
1329 (cf. *Note Base64::)
1332 File: tm-en.info, Node: RFC 821, Next: RFC 822, Prev: Quoted-Printable, Up: Glossary
1338 J. Postel, "Simple Mail Transfer Protocol", August 1982, STD 10.
1341 File: tm-en.info, Node: RFC 822, Next: RFC 934, Prev: RFC 821, Up: Glossary
1346 A RFC defines format of Internet mail message, mainly *message
1350 news message is based on RFC 822, so *Internet message* may be
1351 more suitable than *Internet mail* .
1354 D. Crocker, "Standard for the Format of ARPA Internet Text
1355 Messages", August 1982, STD 11.
1358 File: tm-en.info, Node: RFC 934, Next: RFC 1036, Prev: RFC 822, Up: Glossary
1363 A RFC defines an *encapsulation* (*Note encapsulation::) method for
1364 Internet mail (*Note RFC 822::).
1366 It conflicts with MIME (*Note MIME::), so you should use
1367 message/rfc822 (*Note message/rfc822::).
1370 Marshall T. Rose and Einar A. Stefferud, "Proposed Standard for
1371 Message Encapsulation", January 1985.
1374 File: tm-en.info, Node: RFC 1036, Next: RFC 1153, Prev: RFC 934, Up: Glossary
1379 A RFC defines format of USENET message. It is a subset of RFC 822
1380 (*Note RFC 822::). It is not Internet standard, but a lot of netnews
1381 excepting Usenet uses it.
1384 M. Horton and R. Adams, "Standard for Interchange of USENET
1385 Messages", December 1987, (obsolete RFC 850).
1388 File: tm-en.info, Node: RFC 1153, Next: RFC 1557, Prev: RFC 1036, Up: Glossary
1394 F. Wancho, "Digest Message Format", April 1990.
1397 File: tm-en.info, Node: RFC 1557, Next: RFC 1922, Prev: RFC 1153, Up: Glossary
1402 A RFC defines MIME charset (*Note MIME charset::)s for Korean, euc-kr
1403 (*Note euc-kr::) and iso-2022-kr (*Note iso-2022-kr::).
1406 U. Choi, K. Chon and H. Park, "Korean Character Encoding for
1407 Internet Messages", December 1993, Informational.
1410 File: tm-en.info, Node: RFC 1922, Next: RFC 2045, Prev: RFC 1557, Up: Glossary
1415 A RFC defines MIME charset (*Note MIME charset::)s for Chinese,
1416 iso-2022-cn (*Note iso-2022-cn::), iso-2022-cn-ext (*Note
1417 iso-2022-cn-ext::), cn-gb (*Note cn-gb::), cn-big5 (*Note cn-big5::),
1420 In addition, it defines additional parameters of Content-Type field
1421 (*Note Content-Type field::) field, *charset-edition* and
1422 *charset-extension*.
1425 Zhu, HF., Hu, DY., Wang, ZG., Kao, TC., Chang, WCH. and Crispin,
1426 M., "Chinese Character Encoding for Internet Messages", March 1996,
1430 File: tm-en.info, Node: RFC 2045, Next: RFC 2046, Prev: RFC 1922, Up: Glossary
1436 N. Freed and N. Borenstein, "Multipurpose Internet Mail Extensions
1437 (MIME) Part One: Format of Internet Message Bodies", November 1996,
1438 Standards Track (obsolete RFC 1521, 1522, 1590).
1441 File: tm-en.info, Node: RFC 2046, Next: RFC 2048, Prev: RFC 2045, Up: Glossary
1447 N. Freed and N. Borenstein, "Multipurpose Internet Mail Extensions
1448 (MIME) Part Two: Media Types", November 1996, Standards Track
1449 (obsolete RFC 1521, 1522, 1590).
1452 File: tm-en.info, Node: RFC 2048, Next: RFC 2049, Prev: RFC 2046, Up: Glossary
1458 N. Freed, J. Klensin and J. Postel, "Multipurpose Internet Mail
1459 Extensions (MIME) Part Four: Registration Procedures", November
1460 1996, Standards Track (obsolete RFC 1521, 1522, 1590).
1463 File: tm-en.info, Node: RFC 2049, Next: plain text, Prev: RFC 2048, Up: Glossary
1469 N. Freed and N. Borenstein, "Multipurpose Internet Mail Extensions
1470 (MIME) Part Five: Conformance Criteria and Examples", November
1471 1996, Standards Track (obsolete RFC 1521, 1522, 1590).
1474 File: tm-en.info, Node: plain text, Next: Security multipart, Prev: RFC 2049, Up: Glossary
1479 A textual data represented by only coded character set (*Note coded
1480 character set::). It does not have information about font or
1481 typesetting. (cf. *Note text/plain::)
1484 File: tm-en.info, Node: Security multipart, Next: text/enriched, Prev: plain text, Up: Glossary
1489 A format to represent signed/encrypted message in MIME (*Note
1492 It defines two multipart media types, *multipart/signed* (*Note
1493 multipart/signed::) and *multipart/encrypted* (*Note
1494 multipart/encrypted::).
1496 MOSS and PGP/MIME (*Note PGP/MIME::) are based on it.
1498 [Security multipart: RFC 1847]
1499 James Galvin, Gale Murphy, Steve Crocker and Ned Freed, "Security
1500 Multiparts for MIME: Multipart/Signed and Multipart/Encrypted",
1501 October 1995, Standards Track.
1504 File: tm-en.info, Node: text/enriched, Next: text/plain, Prev: Security multipart, Up: Glossary
1509 [text/enriched: RFC 1896]
1510 P. Resnick and A. Walker, "The text/enriched MIME Content-type",
1511 February 1996, (obsolete RFC 1563).
1514 File: tm-en.info, Node: text/plain, Next: tm-kernel, Prev: text/enriched, Up: Glossary
1519 *text/plain* is a media type (*Note media type::) for plain text
1520 (*Note plain text::), defined in RFC 2046 (*Note RFC 2046::).
1522 The default media type of "text/plain; charset=us-ascii" for Internet
1523 mail describes existing Internet practice. That is, it is the type of
1524 body defined by RFC 822 (*Note RFC 822::).
1526 (cf. *Note MIME charset::) (cf. *Note us-ascii::)
1529 File: tm-en.info, Node: tm-kernel, Next: tm-MUA, Prev: text/plain, Up: Glossary
1534 A libraries to provide user interface about MIME (*Note MIME::) for
1535 emacs. tm stands for `tools for MIME'.
1537 *[Unimportant notice(^-^;]*
1538 * tm may not stand for "tiny-mime"(^-^;
1540 * tm may not stand for initial of an author (^-^;
1542 * "Tools for MIME" may be strained (^-^;
1545 File: tm-en.info, Node: tm-MUA, Next: us-ascii, Prev: tm-kernel, Up: Glossary
1550 MUA (*Note MUA::) or MUA extender using tm (*Note tm-kernel::).
1552 *tm oomori package* has following extenders:
1554 * *tm-mh-e* (*Note (tm-mh-e-en)::) for mh-e (*Note (mh-e)::)
1556 * *tm-gnus* (*Note (tm-gnus_en)::) for GNUS
1558 * *gnus-mime* (*Note (gnus-mime-en)::) for Gnus
1560 * *tm-vm* (*Note (tm-vm-en)::) for VM
1562 * *tm-rmail* for RMAIL
1565 File: tm-en.info, Node: us-ascii, Prev: tm-MUA, Up: Glossary
1570 A MIME charset (*Note MIME charset::) for primary Latin script mainly
1571 written by English or other languages.
1573 It is a 7bit coded character set (*Note coded character set::) based
1574 on ISO 2022 (*Note ISO 2022::), it contains only ASCII (*Note ASCII::)
1575 and code extension (*Note code extension::) is not allowed.
1577 It is standard coded character set of Internet mail. If MIME
1578 charset is not specified, *us-ascii* is used as default.
1580 In addition, *ASCII* of RFC 822 (*Note RFC 822::) should be
1581 interpreted as us-ascii.
1584 File: tm-en.info, Node: Setting, Next: Bug report, Prev: Introduction, Up: Top
1589 In the tm package, two files, `mime-setup.el' and `tm-setup.el', are
1590 provided to ease the setup.
1592 The `mime-setup.el' is used for the whole MIME related setup
1593 including MIME encoding using `tm-edit.el', while `tm-setup.el' is used
1594 to set up tm-MUA only.
1598 * mime-setup:: Normal setting
1599 * tm-setup:: Setting not to use tm-edit
1600 * setting for VM:: Setting for VM
1601 * manual setting:: Setting up without loading provided setup files
1604 File: tm-en.info, Node: mime-setup, Next: tm-setup, Prev: Setting, Up: Setting
1609 If you want normal setting, please use *mime-setup*. For example,
1610 please insert following into `~/.emacs':
1614 As `mime-setup.el' loads `tm-setup.el', you don't need to load
1615 `tm-setup.el' when you use `mime-setup.el' (Description of old version
1616 of Gnus FAQ is wrong!)
1621 * Notice about GNUS:: Notices for GNUS
1624 File: tm-en.info, Node: signature, Next: Notice about GNUS, Prev: mime-setup, Up: mime-setup
1629 You can set up the *automatic signature selection tool* using
1630 `mime-setup'. If you want to automatically select the signature file
1631 depending on how the message headers show, add lines like shown below
1632 to your .emacs (Refer to the reference manual of `signature.el' for
1635 (setq signature-file-alist
1636 '((("Newsgroups" . "jokes") . "~/.signature-jokes")
1637 (("Newsgroups" . ("zxr" "nzr")) . "~/.signature-sun")
1638 (("To" . ("ishimaru" "z-suzuki")) . "~/.signature-sun")
1639 (("To" . "tea") . "~/.signature-jokes")
1640 (("To" . ("sim" "oku" "takuo")) . "~/.signature-formal")
1643 - Variable: mime-setup-use-signature
1644 If it is not `nil', `mime-setup.el' sets up for `signature.el'.
1645 Its default value is `t'.
1647 - Variable: mime-setup-signature-key-alist
1648 It defines key to bind signature inserting command for each
1649 major-mode. Its default value is following:
1651 ((mail-mode . "\C-c\C-w"))
1653 If you want to change, please rewrite it. For example:
1655 (set-alist 'mime-setup-signature-key-alist
1656 'news-reply-mode "\C-c\C-w")
1659 - Variable: mime-setup-default-signature-key
1660 If key to bind signature inserting command for a major-mode is not
1661 found from `mime-setup-signature-key-alist', its value is used as
1662 key. Its default value is `"\C-c\C-s"'.
1665 File: tm-en.info, Node: Notice about GNUS, Prev: signature, Up: mime-setup
1670 When `mime-setup.el' sets up for `signature.el', it sets variable
1671 `gnus-signature-file' to `nil'. Therefore GNUS does not insert
1672 signature automatically when it is sending a message. Reason of this
1673 setting is following:
1675 GNUS inserts signature after `tm-edit.el' composed as MIME message.
1676 Therefore signature inserted by GNUS is not processed as a valid MIME
1677 part. In particular, for multipart message, signature places in outside
1678 of MIME part. So MIME MUA might not display it.
1680 Other notice is key bind. In historical reason, key bind to insert
1681 signature is `C-c C-s' (like mh-e (*Note (mh-e)::)) instead of `C-c
1682 C-w'. If you change to GNUS's default, please set following:
1684 (set-alist 'mime-setup-signature-key-alist 'news-reply-mode "\C-c\C-w")
1687 File: tm-en.info, Node: tm-setup, Next: setting for VM, Prev: mime-setup, Up: Setting
1689 Setting not to use tm-edit
1690 ==========================
1692 *tm-setup* only sets up tm-MUA (*Note tm-MUA::)s. In other words,
1693 it is a setting to avoid to use tm-edit. If you don't want to compose
1694 MIME message or want to use other MIME composer, please use it instead
1697 For example, please insert following into `~/.emacs':
1702 If you use `mime-setup.el', you you don't need to load
1706 File: tm-en.info, Node: setting for VM, Next: manual setting, Prev: tm-setup, Up: Setting
1711 If you use *vm*, please insert following in `~/.vm':
1716 If you use *BBDB*, please insert `(require 'tm-vm)' *after*
1717 `(bbdb-insinuate-vm)'.
1720 File: tm-en.info, Node: manual setting, Prev: setting for VM, Up: Setting
1722 Setting up without loading provided setup files
1723 ===============================================
1725 You may find the valuable hints in `mime-setup.el' or `tm-setup.el'
1726 if you want to set up MIME environment without loading the tm-provided
1730 Current tm provides some convenient features to expect tm-edit, and
1731 they can not use if `mime-setup.el' is not used. If you want to
1732 set up original setting to use tm-edit, please declare following
1735 (provide 'mime-setup)
1739 File: tm-en.info, Node: Bug report, Next: Acknowledgments, Prev: Setting, Up: Top
1741 How to report bug and about mailing list of tm
1742 **********************************************
1744 If you write bug-reports and/or suggestions for improvement, please
1745 send them to the tm Mailing List:
1747 * Japanese <bug-tm-ja@chamonix.jaist.ac.jp>
1749 * English <bug-tm-en@chamonix.jaist.ac.jp>
1751 Notice that, we does not welcome bug reports about too old version.
1752 Bugs in old version might be fixed. So please try latest version at
1755 You should write *good bug report*. If you write only "tm does not
1756 work", we can not find such situations. At least, you should write
1757 name, type, variants and version of OS, emacs, tm and MUA, and setting.
1758 In addition, if error occurs, to send backtrace is very important. (cf.
1759 *Note (emacs)Bugs::)
1761 Bug may not appear only your environment, but also in a lot of
1762 environment (otherwise it might not bug). Therefor if you send mail to
1763 author directly, we must write a lot of mails. So please send mail to
1764 address for tm bugs instead of author.
1766 Via the tm ML, you can report tm bugs, obtain the latest release of
1767 tm, and discuss future enhancements to tm. To join the tm ML, send
1770 * Japanese <tm-ja-admin@chamonix.jaist.ac.jp>
1772 * English <tm-en-admin@chamonix.jaist.ac.jp>
1774 Since the user registration is done manually, please write the mail
1775 body in human-recognizable language (^_^).
1778 File: tm-en.info, Node: Acknowledgments, Next: Concept Index, Prev: Bug report, Up: Top
1783 I thank MASUTANI Yasuhiro. He requested me a lot of important
1784 features and gave me a lot of suggestions when tm-view was born.
1785 tm-view is based on his influence.
1787 I thank ENAMI Tsugutomo for work of `mime.el', which is an origin of
1788 `tm-ew-d.el' and `mel-b.el', and permission to rewrite for tm.
1790 I thank OKABE Yasuo for work of internal method for LaTeX and
1791 automatic assembling method for message/partial. I thank UENO Hiroshi
1792 for work of internal method for tar archive.
1794 I thank UMEDA Masanobu for his work of `mime.el', which is the
1795 origin of tm-edit, and permission to rewrite his work as tm-edit.
1797 I thank KOBAYASHI Shuhei for his work as a tm maintainer. In
1798 addition, he often points out or suggests about conformity with RFCs.
1800 I thank Oscar Figueiredo for his work as the maintainer of tm-vm. He
1801 improves tm-vm and wrote a good manual of tm-vm.
1803 Last of all, I thank members of two tm mailing lists, Japanese and
1807 File: tm-en.info, Node: Concept Index, Next: Variable Index, Prev: Acknowledgments, Up: Top
1815 * 7bit (textual) string: 7bit.
1818 * 8bit (textual) string: 8bit.
1820 * 94-character set: 94-character set.
1821 * 94x94-character set: 94x94-character set.
1822 * 96-character set: 96-character set.
1823 * ANSI X3.4:1986: ASCII.
1824 * application: media type.
1825 * application/pgp: PGP-kazu.
1827 * ASCII <1>: us-ascii.
1829 * audio: media type.
1830 * automatic signature selection tool: signature.
1832 * BBDB: setting for VM.
1835 * charset-edition: RFC 1922.
1836 * charset-extension: RFC 1922.
1837 * CNS 11643:1992: CNS 11643.
1838 * CNS 11643-1992: CNS 11643.
1840 * encapsulation: RFC 934.
1842 * Experimental: Content-Disposition.
1843 * external method: method.
1846 * GB 2312:1980: GB 2312.
1847 * GB 8565.2: GB 8565.2.
1848 * GB 8565.2:1988: GB 8565.2.
1849 * gnus-mime: tm-MUA.
1850 * good bug report: Bug report.
1851 * image: media type.
1852 * Informational <1>: hz-gb2312.
1853 * Informational <1>: RFC 1557.
1854 * Informational <1>: RFC 1922.
1855 * Informational <1>: hz-gb2312.
1856 * Informational <1>: iso-2022-jp-2.
1857 * Informational <1>: iso-8859-7.
1858 * Informational: PGP.
1859 * internal method: method.
1860 * Internet mail: RFC 822.
1861 * Internet message: RFC 822.
1862 * ISO 2022: ISO 2022.
1864 * ISO 8859-1: ISO 8859-1.
1865 * ISO 8859-1:1987: ISO 8859-1.
1866 * ISO 8859-2: ISO 8859-2.
1867 * ISO 8859-2:1987: ISO 8859-2.
1868 * ISO 8859-3: ISO 8859-3.
1869 * ISO 8859-3:1988: ISO 8859-3.
1870 * ISO 8859-4: ISO 8859-4.
1871 * ISO 8859-4:1988: ISO 8859-4.
1872 * ISO 8859-5: ISO 8859-5.
1873 * ISO 8859-5:1988: ISO 8859-5.
1874 * ISO 8859-6: ISO 8859-6.
1875 * ISO 8859-6:1987: ISO 8859-6.
1876 * ISO 8859-7: ISO 8859-7.
1877 * ISO 8859-7:1987: ISO 8859-7.
1878 * ISO 8859-8: ISO 8859-8.
1879 * ISO 8859-8:1988: ISO 8859-8.
1880 * ISO 8859-9: ISO 8859-9.
1881 * ISO 8859-9:1990: ISO 8859-9.
1882 * iso-2022-jp: iso-2022-jp.
1883 * iso-2022-jp-2: iso-2022-jp-2.
1884 * iso-8859-1: iso-8859-1.
1885 * iso-8859-2: iso-8859-2.
1886 * iso-8859-5: iso-8859-5.
1887 * iso-8859-7: iso-8859-7.
1888 * ISO/IEC 2022:1994: ISO 2022.
1889 * ISO/IEC 646:1991: ISO 646.
1890 * JIS X 0201-1976:: JIS X0201.
1891 * JIS X0208:1983,1990: JIS X0208.
1892 * JIS C6220-1976: JIS X0201.
1893 * JIS C6226:1978: JIS X0208.
1894 * JIS X 0208:1997? draft: JIS X0208.
1895 * JIS X 0201:1997? draft: JIS X0201.
1896 * JIS X0201-1976: JIS X0201.
1897 * JIS X0201-1997?: JIS X0201.
1898 * JIS X0208-1978: JIS X0208.
1899 * JIS X0208-1983,1990: JIS X0208.
1900 * JIS X0208-1997?: JIS X0208.
1901 * KS C 5601:1987: KS C5601.
1902 * KS C 5861:1992: euc-kr.
1903 * KS C5601: KS C5601.
1904 * media type: media type.
1905 * message: media type.
1906 * message header: RFC 822.
1907 * Message Transfer Agent: MTA.
1908 * Message User Agent: MUA.
1909 * message/rfc822: message/rfc822.
1910 * mime-setup: mime-setup.
1912 * multipart <1>: media type.
1913 * multipart: multipart.
1914 * multipart/digest <1>: multipart/alternative.
1915 * multipart/digest: multipart/digest.
1916 * multipart/encrypted: Security multipart.
1917 * multipart/parallel: multipart/parallel.
1918 * multipart/signed: Security multipart.
1919 * Multipurpose Internet Mail Extensions: MIME.
1921 * parameter: Content-Type field.
1923 * PGP-kazu: PGP-kazu.
1924 * PGP/MIME: PGP/MIME.
1925 * Pretty Good Privacy: PGP.
1926 * Quoted-Printable: Quoted-Printable.
1927 * RFC 1036: RFC 1036.
1928 * RFC 1153: RFC 1153.
1929 * RFC 1468: iso-2022-jp.
1931 * RFC 1554: iso-2022-jp-2.
1932 * RFC 1557: RFC 1557.
1933 * RFC 1806: Content-Disposition.
1934 * RFC 1842: hz-gb2312.
1935 * RFC 1843: hz-gb2312.
1936 * RFC 1847: Security multipart.
1937 * RFC 1896: text/enriched.
1938 * RFC 1922: RFC 1922.
1939 * RFC 1947: iso-8859-7.
1941 * RFC 2015: PGP/MIME.
1942 * RFC 2045: RFC 2045.
1943 * RFC 2046: RFC 2046.
1944 * RFC 2047: encoded-word.
1945 * RFC 2048: RFC 2048.
1946 * RFC 2049: RFC 2049.
1951 * Security multipart: Security multipart.
1953 * Standards Track <1>: PGP/MIME.
1954 * Standards Track <1>: RFC 2046.
1955 * Standards Track <1>: RFC 2049.
1956 * Standards Track <1>: Security multipart.
1957 * Standards Track <1>: encoded-word.
1958 * Standards Track <1>: RFC 2045.
1959 * Standards Track: RFC 2048.
1963 * subtype <1>: Content-Type field.
1964 * subtype: media type.
1966 * text/enriched: text/enriched.
1967 * text/plain: text/plain.
1968 * tm oomori package: tm-MUA.
1972 * tm-setup: tm-setup.
1974 * type <1>: media type.
1975 * type: Content-Type field.
1976 * us-ascii: us-ascii.
1978 * video: media type.
1979 * vm: setting for VM.
1980 * x-token: media type.
1981 * XEmacs/mule: MULE.
1984 File: tm-en.info, Node: Variable Index, Prev: Concept Index, Up: Top
1991 * mime-setup-default-signature-key: signature.
1992 * mime-setup-signature-key-alist: signature.
1993 * mime-setup-use-signature: signature.
1999 Node: Introduction
\7f497
2000 Node: Glossary
\7f1208
2003 Node: 94-character set
\7f5333
2004 Node: 96-character set
\7f5700
2005 Node: 94x94-character set
\7f6051
2010 Node: cn-big5
\7f8290
2011 Node: CNS 11643
\7f8875
2012 Node: coded character set
\7f9624
2013 Node: code extension
\7f9959
2014 Node: Content-Disposition
\7f10248
2015 Node: Content-Type field
\7f10693
2017 Node: encoded-word
\7f11965
2018 Node: encapsulation
\7f12385
2019 Node: entity
\7f12683
2020 Node: euc-kr
\7f12970
2022 Node: GB 2312
\7f13659
2023 Node: GB 8565.2
\7f14117
2024 Node: graphic character set
\7f14554
2025 Node: hz-gb2312
\7f14778
2026 Node: ISO 2022
\7f15617
2027 Node: iso-2022-cn
\7f16026
2028 Node: iso-2022-cn-ext
\7f16498
2029 Node: iso-2022-jp
\7f17148
2030 Node: iso-2022-jp-2
\7f17860
2031 Node: iso-2022-kr
\7f18277
2032 Node: ISO 646
\7f18717
2033 Node: ISO 8859-1
\7f19007
2034 Node: iso-8859-1
\7f19324
2035 Node: ISO 8859-2
\7f19798
2036 Node: iso-8859-2
\7f20118
2037 Node: ISO 8859-3
\7f20592
2038 Node: ISO 8859-4
\7f20912
2039 Node: ISO 8859-5
\7f21232
2040 Node: iso-8859-5
\7f21556
2041 Node: ISO 8859-6
\7f21998
2042 Node: ISO 8859-7
\7f22320
2043 Node: iso-8859-7
\7f22641
2044 Node: ISO 8859-8
\7f23191
2045 Node: ISO 8859-9
\7f23513
2046 Node: ISO-IR-165
\7f23833
2047 Node: JIS X0201
\7f24316
2048 Node: JIS C6226
\7f25010
2049 Node: JIS X0208
\7f25262
2050 Node: JIS X0212
\7f26716
2051 Node: koi8-r
\7f27040
2052 Node: KS C5601
\7f27508
2053 Node: media type
\7f27926
2054 Node: message
\7f28880
2055 Node: message/rfc822
\7f29120
2056 Node: method
\7f29501
2058 Node: MIME charset
\7f30977
2062 Node: multipart
\7f32750
2063 Node: multipart/alternative
\7f33499
2064 Node: multipart/digest
\7f33964
2065 Node: multipart/encrypted
\7f34621
2066 Node: multipart/mixed
\7f34919
2067 Node: multipart/parallel
\7f35252
2068 Node: multipart/signed
\7f35699
2070 Node: PGP-kazu
\7f36660
2071 Node: PGP/MIME
\7f37296
2072 Node: Quoted-Printable
\7f37921
2073 Node: RFC 821
\7f38315
2074 Node: RFC 822
\7f38511
2075 Node: RFC 934
\7f38919
2076 Node: RFC 1036
\7f39350
2077 Node: RFC 1153
\7f39757
2078 Node: RFC 1557
\7f39927
2079 Node: RFC 1922
\7f40295
2080 Node: RFC 2045
\7f40927
2081 Node: RFC 2046
\7f41243
2082 Node: RFC 2048
\7f41537
2083 Node: RFC 2049
\7f41852
2084 Node: plain text
\7f42171
2085 Node: Security multipart
\7f42465
2086 Node: text/enriched
\7f43093
2087 Node: text/plain
\7f43363
2088 Node: tm-kernel
\7f43853
2089 Node: tm-MUA
\7f44270
2090 Node: us-ascii
\7f44722
2091 Node: Setting
\7f45337
2092 Node: mime-setup
\7f45944
2093 Node: signature
\7f46433
2094 Node: Notice about GNUS
\7f47969
2095 Node: tm-setup
\7f48854
2096 Node: setting for VM
\7f49407
2097 Node: manual setting
\7f49720
2098 Node: Bug report
\7f50324
2099 Node: Acknowledgments
\7f51778
2100 Node: Concept Index
\7f52871
2101 Node: Variable Index
\7f61595