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 * mime/viewer-mode (*Note (tm-view-en)::)
48 * mime/editor-mode (*Note (tm-edit-en)::)
55 File: tm-en.info, Node: Glossary, Prev: Introduction, Up: Introduction
66 * 94x94-character set::
70 * cn-gb:: cn-gb, gb2312
71 * cn-big5:: cn-big5, big5
72 * CNS 11643:: CNS 11643-1992
73 * coded character set:: Coded character set, Character code
74 * code extension:: Code extension
75 * Content-Disposition:: Content-Disposition field
76 * Content-Type field::
83 * GB 2312:: GB 2312-1980
84 * GB 8565.2:: GB 8565.2-1988
85 * graphic character set:: Graphic Character Set
107 * ISO-IR-165:: ISO-IR-165, CCITT Extended GB
109 * JIS C6226:: JIS C6226-1978
111 * JIS X0212:: JIS X0212-1990
113 * KS C5601:: KS C5601-1987
123 * multipart:: Multipart
124 * multipart/alternative::
126 * multipart/encrypted::
128 * multipart/parallel::
146 * Security multipart::
149 * tm-kernel:: tm-kernel, tm
154 File: tm-en.info, Node: 7bit, Next: 8bit, Prev: Glossary, Up: Glossary
159 *7bit* means any integer between 0 .. 127.
161 Any data represented by 7bit integers is called *7bit data*.
163 Textual string consisted of Control characters between 0 .. 31 and
164 127, and space represented by 32, and graphic characters between 33 ..
165 236 are called *7bit (textual) string*.
167 Traditional Internet MTA (*Note MTA::) can translate 7bit data, so
168 it is no need to translate by Quoted-Printable (*Note
169 Quoted-Printable::) or Base64 (*Note Base64::) for 7bit data.
171 However if there are too long lines, it can not translate by 7bit MTA
172 even if it is 7bit data. RFC 821 (*Note RFC 821::) and RFC 2045 (*Note
173 RFC 2045::) require lines in 7bit data must be less than 998 bytes. So
174 if a "7bit data" has a line more than 999 bytes, it is regarded as
175 binary (*Note binary::). For example, Postscript file should be
176 encoded by Quoted-Printable.
179 File: tm-en.info, Node: 8bit, Next: 94-character set, Prev: 7bit, Up: Glossary
184 *8bit* means any integer between 0 .. 255.
186 Any data represented by 8bit integers is called *8bit data*.
188 Textual string consisted of Control characters between 0 .. 31, 127,
189 and 128 .. 159, and space represented by 32, and graphic characters
190 between 33 .. 236 and 160 .. 255 are called *8bit (textual) string*.
192 For example, iso-8859-1 (*Note iso-8859-1::) or euc-kr (*Note
193 euc-kr::) are coded-character-set represented by 8bit textual string.
195 Traditional Internet MTA (*Note MTA::) can translate only 7bit
196 (*Note 7bit::) data, so if a 8bit data will be translated such MTA, it
197 must be encoded by Quoted-Printable (*Note Quoted-Printable::) or Base64
200 However 8bit MTA are increasing today.
202 However if there are too long lines, it can not translate by 8bit MTA
203 even if it is 8bit data. RFC 2045 (*Note RFC 2045::) require lines in
204 8bit data must be less than 998 bytes. So if a "8bit data" has a line
205 more than 999 bytes, it is regarded as binary (*Note binary::), so it
206 must be encoded by Base64 or Quoted-Printable.
209 File: tm-en.info, Node: 94-character set, Next: 96-character set, Prev: 8bit, Up: Glossary
214 *94-character set* is a kind of 1 byte graphic character set (*Note
215 graphic character set::), each characters are in positions 02/01 (33)
216 to 07/14 (126) or 10/01 (161) to 15/14 (254). (ex. ASCII (*Note
217 ASCII::), JIS X0201-Latin)
220 File: tm-en.info, Node: 96-character set, Next: 94x94-character set, Prev: 94-character set, Up: Glossary
225 *96-character set* is a kind of 1 byte graphic character set (*Note
226 graphic character set::), each characters are in positions 02/00 (32)
227 to 07/15 (126) or 10/00 (160) to 15/15 (255). (ex. ISO 8859)
230 File: tm-en.info, Node: 94x94-character set, Next: ASCII, Prev: 96-character set, Up: Glossary
235 *94x94-character set* is a kind of 2 byte graphic character set
236 (*Note graphic character set::), each bytes are in positions 02/01 (33)
237 to 07/14 (126) or 10/01 (161) to 15/14 (254). (ex. JIS X0208 (*Note
238 JIS X0208::), GB 2312 (*Note GB 2312::))
241 File: tm-en.info, Node: ASCII, Next: Base64, Prev: 94x94-character set, Up: Glossary
246 *ASCII* is a 94-character set (*Note 94-character set::) contains
247 primary latin characters (A-Z, a-z), numbers and some characters. It is
248 a standard of the United States of America. It is a variant of ISO 646
252 "Coded Character Set - 7-Bit American Standard Code for Information
253 Interchange", ANSI X3.4:1986.
256 File: tm-en.info, Node: Base64, Next: binary, Prev: ASCII, Up: Glossary
261 *Base64* is a transfer encoding method of MIME (*Note MIME::)
262 defined in RFC 2045 (*Note RFC 2045::).
264 The encoding process represents 24-bit groups of input bits as output
265 strings of 4 encoded characters. Encoded characters represent integer 0
266 .. 63 or *pad*. Base64 data must be 4 * n bytes, so pad is used to
269 These 65 characters are subset of all versions of ISO 646, including
270 US-ASCII, and all versions of EBCDIC. So it is safe even if it is
271 translated by non-Internet gateways.
274 File: tm-en.info, Node: binary, Next: cn-gb, Prev: Base64, Up: Glossary
279 Any byte stream is called *binary*.
281 It does not require structureof lines. It differs from from 8bit
284 In addition, if line structured data contain too long line (more than
285 998 bytes), it is regarded as binary.
288 File: tm-en.info, Node: cn-gb, Next: cn-big5, Prev: binary, Up: Glossary
293 A MIME charset (*Note MIME charset::) for simplified Chinese mainly
294 used in the Chinese mainland.
296 It is a 8bit (*Note 8bit::) coded character set (*Note coded
297 character set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII
298 (*Note ASCII::) to combine GB 2312 (*Note GB 2312::).
300 It is defined in RFC 1922 (*Note RFC 1922::).
303 File: tm-en.info, Node: cn-big5, Next: CNS 11643, Prev: cn-gb, Up: Glossary
308 A MIME charset (*Note MIME charset::) for traditional Chinese mainly
309 used in Taiwan and Hon Kong.
311 It is a 8bit (*Note 8bit::) coded character set (*Note coded
312 character set::) not based on ISO 2022 (*Note ISO 2022::). It is a
315 It is defined in RFC 1922 (*Note RFC 1922::).
320 Institute for Information Industry, "Chinese Coded Character Set in
321 Computer", March 1984.
323 It corresponds to CNS 11643 (*Note CNS 11643::).
326 File: tm-en.info, Node: CNS 11643, Next: coded character set, Prev: cn-big5, Up: Glossary
331 Graphic character sets (*Note graphic character set::) for Chinese
332 mainly written by traditional Chinese mainly used in Taiwan and Hong
333 Kong. It is a standard of Taiwan. Currently there are seven
334 94x94-character set (*Note 94x94-character set::).
336 Final byte of ISO 2022 (*Note ISO 2022::) are following:
360 "Standard Interchange Code for Generally-Used Chinese Characters",
364 File: tm-en.info, Node: coded character set, Next: code extension, Prev: CNS 11643, Up: Glossary
366 Coded character set, Character code
367 -----------------------------------
369 A set of unambiguous rules that establishes a character set and the
370 one-to-one relationship between the characters of the set and their bit
374 File: tm-en.info, Node: code extension, Next: Content-Disposition, Prev: coded character set, Up: Glossary
379 The techniques for the encoding of characters that are not included
380 in the character set of a given code. (ex. ISO 2022 (*Note ISO 2022::))
383 File: tm-en.info, Node: Content-Disposition, Next: Content-Type field, Prev: code extension, Up: Glossary
385 Content-Disposition field
386 -------------------------
388 A field to specify presentation of entity or file name. It is an
389 extension for MIME (*Note MIME::).
392 E R. Troost and S. Dorner, "Communicating Presentation Information
393 in Internet Messages: The Content-Disposition Header", June 1995,
397 File: tm-en.info, Node: Content-Type field, Next: Emacs, Prev: Content-Disposition, Up: Glossary
402 Header field to represent information about body, such as media type
403 (*Note media type::), MIME charset (*Note MIME charset::). It is
404 defined in RFC 2045 (*Note RFC 2045::).
407 Historically, Content-Type field was proposed in RFC 1049. In it,
408 Content-Type did not distinguish type and subtype. However MIME
409 parser may be able to accept RFC 1049 based Content-Type as
412 Content-Type field is defined as following:
414 "Content-Type" ":" *type* "/" *subtype* *( ";" *parameter* )
418 Content-Type: image/jpeg
420 Content-Type: text/plain; charset=iso-2022-jp
423 A part does not have content-type field is regarded as
425 Content-Type: text/plain; charset=us-ascii
427 (cf. *Note us-ascii::)
429 And a part has unknown type/subtype is regarded as
431 Content-Type: application/octet-stream
435 File: tm-en.info, Node: Emacs, Next: encoded-word, Prev: Content-Type field, Up: Glossary
440 In this document, `Emacs' means GNU Emacs released by FSF, and
441 `emacs' means any variants of GNU Emacs.
444 File: tm-en.info, Node: encoded-word, Next: encapsulation, Prev: Emacs, Up: Glossary
449 Representation non ASCII (*Note ASCII::) characters in header. It is
450 defined in *RFC 2047*.
453 K. Moore, "MIME (Multipurpose Internet Mail Extensions) Part Three:
454 Message Header Extensions for Non-ASCII Text", November 1996,
455 Standards Track (obsolete RFC 1521,1522,1590).
458 File: tm-en.info, Node: encapsulation, Next: entity, Prev: encoded-word, Up: Glossary
463 Method to insert whole Internet message (*Note RFC 822::) into
464 another Internet message.
466 For example, it is used to forward a message.
468 (cf. *Note message/rfc822::)
471 File: tm-en.info, Node: entity, Next: euc-kr, Prev: encapsulation, Up: Glossary
476 Header fields and contents of a message or one of the parts in the
477 body of a multipart (*Note multipart::) entity.
480 In this document, `entity' might be called "part".
483 File: tm-en.info, Node: euc-kr, Next: FTP, Prev: entity, Up: Glossary
488 A MIME charset (*Note MIME charset::) for Korean.
490 It is a 8bit (*Note 8bit::) coded character set (*Note coded
491 character set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII
492 (*Note ASCII::) to combine KS C5601 (*Note KS C5601::).
494 It is defined in RFC 1557 (*Note RFC 1557::).
499 Korea Industrial Standards Association, "Hangul Unix Environment",
503 File: tm-en.info, Node: FTP, Next: GB 2312, Prev: euc-kr, Up: Glossary
509 Postel, J. and J. Reynolds, "File Transfer Protocol", October 1985,
513 File: tm-en.info, Node: GB 2312, Next: GB 8565.2, Prev: FTP, Up: Glossary
518 A 94x94-character set (*Note 94x94-character set::) for Chinese
519 mainly written by simplified Chinese mainly used in the Chinese
520 mainland. It is a standard of China.
522 Final byte of ISO 2022 (*Note ISO 2022::) is 04/01 (`A').
525 "Code of Chinese Graphic Character Set for Information Interchange
526 - Primary Set", GB 2312:1980.
529 File: tm-en.info, Node: GB 8565.2, Next: graphic character set, Prev: GB 2312, Up: Glossary
534 A 94x94-character set (*Note 94x94-character set::) for Chinese as
535 supplement to GB 2312 (*Note GB 2312::). It is a standard of China.
538 "Information Processing - Coded Character Sets for Text
539 Communication - Part 2: Graphic Characters used with Primary Set",
543 File: tm-en.info, Node: graphic character set, Next: hz-gb2312, Prev: GB 8565.2, Up: Glossary
545 Graphic Character Set
546 ---------------------
548 Coded character set (*Note coded character set::) for graphic
552 File: tm-en.info, Node: hz-gb2312, Next: ISO 2022, Prev: graphic character set, Up: Glossary
557 A MIME charset (*Note MIME charset::) for simplified Chinese mainly
558 used in the Chinese mainland.
560 It extends ASCII (*Note ASCII::) to combine GB 2312 (*Note GB
561 2312::), its technique is like iso-2022-jp (*Note iso-2022-jp::), but
562 it is designed to be ASCII printable to use special form for ESC
563 sequence to designate GB 2312 to G0.
565 It is defined in RFC 1842 and 1843.
568 Y. Wei, Y. Zhang, J. Li, J. Ding and Y. Jiang, "ASCII Printable
569 Characters-Based Chinese Character Encoding for Internet Messages",
570 August 1995, Informational.
573 F. Lee, "HZ - A Data Format for Exchanging Files of Arbitrarily
574 Mixed Chinese and ASCII characters", August 1995, Informational.
577 File: tm-en.info, Node: ISO 2022, Next: iso-2022-cn, Prev: hz-gb2312, Up: Glossary
582 It is a standard for character code structure and code extension
583 (*Note code extension::) technique.
586 International Organization for Standardization (ISO), "Information
587 Processing: ISO 7-bit and 8-bit coded character sets: Code
588 extension techniques", ISO/IEC 2022:1994.
591 File: tm-en.info, Node: iso-2022-cn, Next: iso-2022-cn-ext, Prev: ISO 2022, Up: Glossary
596 A MIME charset (*Note MIME charset::) for Chinese.
598 It is a 7bit (*Note 7bit::) coded character set (*Note coded
599 character set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII
600 (*Note ASCII::) to combine GB 2312 (*Note GB 2312::) and/or CNS 11643
601 plain 1, plain 2 (*Note CNS 11643::).
603 It is defined in RFC 1922 (*Note RFC 1922::).
606 File: tm-en.info, Node: iso-2022-cn-ext, Next: iso-2022-jp, Prev: iso-2022-cn, Up: Glossary
611 A MIME charset (*Note MIME charset::) for Chinese.
613 It is a 7bit (*Note 7bit::) coded character set (*Note coded
614 character set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII
615 (*Note ASCII::) to combine GB 2312 (*Note GB 2312::), CNS 11643 plain 1
616 .. 7 (*Note CNS 11643::), ISO-IR-165 (*Note ISO-IR-165::) and other
617 Chinese graphic character sets.
619 It is defined in RFC 1922 (*Note RFC 1922::).
622 MULE 2.3 and current XEmacs/mule can not use it correctly.
624 Emacs/mule can use it.
627 File: tm-en.info, Node: iso-2022-jp, Next: iso-2022-jp-2, Prev: iso-2022-cn-ext, Up: Glossary
632 A MIME charset (*Note MIME charset::) for Japanese.
634 It is a 7bit (*Note 7bit::) coded character set (*Note coded
635 character set::) based on old ISO 2022 (*Note ISO 2022::). It switches
636 ASCII (*Note ASCII::), JIS X0201-Latin, JIS X0208-1978 (*Note JIS
637 C6226::) and JIS X0208-1983 (*Note JIS X0208::).
639 It is defined in RFC 1468.
642 JIS X0208-1997? will define it in annex as non-ISO 2022 (*Note ISO
645 [iso-2022-jp: RFC 1468]
646 Murai J., M. Crispin, and E. van der Poel, "Japanese Character
647 Encoding for Internet Messages", June 1993.
650 File: tm-en.info, Node: iso-2022-jp-2, Next: iso-2022-kr, Prev: iso-2022-jp, Up: Glossary
655 A MIME charset (*Note MIME charset::), which is a multilingual
656 extension of iso-2022-jp (*Note iso-2022-jp::).
658 It is defined in RFC 1554.
660 [iso-2022-jp-2: RFC 1554]
661 Ohta M. and Handa K., "ISO-2022-JP-2: Multilingual Extension of
662 ISO-2022-JP", December 1993, Informational.
665 File: tm-en.info, Node: iso-2022-kr, Next: ISO 646, Prev: iso-2022-jp-2, Up: Glossary
670 A MIME charset (*Note MIME charset::) for Korean language (Hangul
673 It is based on ISO 2022 (*Note ISO 2022::) code extension (*Note
674 code extension::) technique to extend ASCII (*Note ASCII::) to use KS
675 C5601 (*Note KS C5601::) as 7bit (*Note 7bit::) text.
677 It is defined in RFC 1557 (*Note RFC 1557::).
680 File: tm-en.info, Node: ISO 646, Next: ISO 8859-1, Prev: iso-2022-kr, Up: Glossary
686 International Organization for Standardization (ISO), "Information
687 technology: ISO 7-bit coded character set for information
688 interchange", ISO/IEC 646:1991.
691 File: tm-en.info, Node: ISO 8859-1, Next: iso-8859-1, Prev: ISO 646, Up: Glossary
697 International Organization for Standardization (ISO), "Information
698 Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
699 1: Latin Alphabet No.1", ISO 8859-1:1987.
702 File: tm-en.info, Node: iso-8859-1, Next: ISO 8859-2, Prev: ISO 8859-1, Up: Glossary
707 *iso-8859-1* is a MIME charset (*Note MIME charset::) for
708 west-European languages written by Latin script.
710 It is a 8bit (*Note 8bit::) coded character set (*Note coded
711 character set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII
712 (*Note ASCII::) to combine ISO 8859-1 (*Note ISO 8859-1::).
714 It is defined in RFC 2046 (*Note RFC 2046::).
717 File: tm-en.info, Node: ISO 8859-2, Next: iso-8859-2, Prev: iso-8859-1, Up: Glossary
723 International Organization for Standardization (ISO), "Information
724 Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
725 2: Latin alphabet No.2", ISO 8859-2:1987.
728 File: tm-en.info, Node: iso-8859-2, Next: ISO 8859-3, Prev: ISO 8859-2, Up: Glossary
733 *iso-8859-2* is a MIME charset (*Note MIME charset::) for
734 east-European languages written by Latin script.
736 It is a 8bit (*Note 8bit::) coded character set (*Note coded
737 character set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII
738 (*Note ASCII::) to combine ISO 8859-2 (*Note ISO 8859-2::).
740 It is defined in RFC 2046 (*Note RFC 2046::).
743 File: tm-en.info, Node: ISO 8859-3, Next: ISO 8859-4, Prev: iso-8859-2, Up: Glossary
749 International Organization for Standardization (ISO), "Information
750 Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
751 3: Latin alphabet No.3", ISO 8859-3:1988.
754 File: tm-en.info, Node: ISO 8859-4, Next: ISO 8859-5, Prev: ISO 8859-3, Up: Glossary
760 International Organization for Standardization (ISO), "Information
761 Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
762 4: Latin alphabet No.4", ISO 8859-4:1988.
765 File: tm-en.info, Node: ISO 8859-5, Next: iso-8859-5, Prev: ISO 8859-4, Up: Glossary
771 International Organization for Standardization (ISO), "Information
772 Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
773 5: Latin/Cyrillic alphabet", ISO 8859-5:1988.
776 File: tm-en.info, Node: iso-8859-5, Next: ISO 8859-6, Prev: ISO 8859-5, Up: Glossary
781 *iso-8859-5* is a MIME charset (*Note MIME charset::) for Cyrillic
784 It is a 8bit (*Note 8bit::) coded character set (*Note coded
785 character set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII
786 (*Note ASCII::) to combine ISO 8859-5 (*Note ISO 8859-5::).
788 It is defined in RFC 2046 (*Note RFC 2046::).
791 File: tm-en.info, Node: ISO 8859-6, Next: ISO 8859-7, Prev: iso-8859-5, Up: Glossary
797 International Organization for Standardization (ISO), "Information
798 Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
799 6: Latin/Arabic alphabet", ISO 8859-6:1987.
802 File: tm-en.info, Node: ISO 8859-7, Next: iso-8859-7, Prev: ISO 8859-6, Up: Glossary
808 International Organization for Standardization (ISO), "Information
809 Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
810 7: Latin/Greek alphabet", ISO 8859-7:1987.
813 File: tm-en.info, Node: iso-8859-7, Next: ISO 8859-8, Prev: ISO 8859-7, Up: Glossary
818 *iso-8859-7* is a MIME charset (*Note MIME charset::) for Greek
821 It is a 8bit (*Note 8bit::) coded character set (*Note coded
822 character set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII
823 (*Note ASCII::) to combine ISO 8859-7 (*Note ISO 8859-7::).
825 It is defined in RFC 1947.
827 [iso-8859-7: RFC 1947]
828 D. Spinellis, "Greek Character Encoding for Electronic Mail
829 Messages", May 1996, Informational.
832 File: tm-en.info, Node: ISO 8859-8, Next: ISO 8859-9, Prev: iso-8859-7, Up: Glossary
838 International Organization for Standardization (ISO), "Information
839 Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
840 8: Latin/Hebrew alphabet", ISO 8859-8:1988.
843 File: tm-en.info, Node: ISO 8859-9, Next: ISO-IR-165, Prev: ISO 8859-8, Up: Glossary
849 International Organization for Standardization (ISO), "Information
850 Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
851 9: Latin alphabet No.5", ISO 8859-9:1990.
854 File: tm-en.info, Node: ISO-IR-165, Next: JIS X0201, Prev: ISO 8859-9, Up: Glossary
856 ISO-IR-165, CCITT Extended GB
857 -----------------------------
859 A 94x94-character set (*Note 94x94-character set::) for Chinese
860 mainly written by simplified Chinese mainly used in the Chinese mainland
863 It consists of GB 2312 (*Note GB 2312::), GB 8565.2 (*Note GB
864 8565.2::) and additional 150 characters.
866 Final byte of ISO 2022 (*Note ISO 2022::) is 04/05 (`E').
869 File: tm-en.info, Node: JIS X0201, Next: JIS C6226, Prev: ISO-IR-165, Up: Glossary
874 It defines two 94-character set (*Note 94-character set::), for Latin
875 script (a variant of ISO 646 (*Note ISO 646::)) and Katakana script, and
876 7bit and 8bit coded character set (*Note coded character set::)s.
878 It was renamed from *JIS C6220-1976*.
881 Japanese Standards Association, "Code for Information Interchange",
884 In addition, revised version will be published in 1997.
887 Japanese Standards Association, "7-bit and 8-bit coded character
888 sets for information interchange", JIS X 0201:1997? draft.
891 File: tm-en.info, Node: JIS C6226, Next: JIS X0208, Prev: JIS X0201, Up: Glossary
896 A 94x94-character set (*Note 94x94-character set::) for Japanese.
897 It was renamed to JIS X0208-1978.
899 (cf. *Note JIS X0208::)
902 File: tm-en.info, Node: JIS X0208, Next: JIS X0212, Prev: JIS C6226, Up: Glossary
907 A 94x94-character set (*Note 94x94-character set::) for Japanese.
908 Japanese standard. It was published in 1978, and revised in 1983 and
909 1990. In the Internet message, 1983 edition is major.
911 JIS X0208 contains some symbols, numbers, primary Latin script,
912 Hiragana script, Katakana script, Greek script, Cyrillic script, box
913 drawing parts, Kanji (Ideographic characters used in Japanese). Notice
914 that some symbols and box drawing parts were added in 1983 and some
915 Kanjis were changed or swapped code points. So 1978 edition and 1983
916 edition are regarded as different graphic character set.
918 1990 edition added some characters, so designation of 1990 edition
919 requires `identify revised registration' sequence, ESC 02/06 4/0 as
920 prefix of designation sequence.
923 Japanese Standards Association, "Code of the Japanese graphic
924 character set for information interchange", JIS C6226:1978.
926 [JIS X0208-1983,1990]
927 Japanese Standards Association, "Code of the Japanese graphic
928 character set for information interchange", JIS X0208:1983,1990.
930 In addition, revised version will be published in 1997. (It does not
931 change graphic character set)
934 Japanese Standards Association, "7-bit and 8-bit double byte coded
935 Kanji sets for information interchange", JIS X 0208:1997? draft.
938 File: tm-en.info, Node: JIS X0212, Next: koi8-r, Prev: JIS X0208, Up: Glossary
943 A 94x94-character set (*Note 94x94-character set::) for Japanese as
944 supplement to JIS X0208 (*Note JIS X0208::). It is a standard of Japan.
946 Final byte of ISO 2022 (*Note ISO 2022::) is 04/04 (`D').
949 File: tm-en.info, Node: koi8-r, Next: KS C5601, Prev: JIS X0212, Up: Glossary
954 A MIME charset (*Note MIME charset::) for Cyrillic script for
955 Russian or other languages.
957 It is a 1 byte 8bit (*Note 8bit::) coded character set (*Note coded
958 character set::), not based on ISO 2022 (*Note ISO 2022::). It is a
961 It is defined in RFC 1489.
964 A. Chernov, "Registration of a Cyrillic Character Set", July 1993.
967 File: tm-en.info, Node: KS C5601, Next: media type, Prev: koi8-r, Up: Glossary
972 A 94x94-character set (*Note 94x94-character set::) for Korean
973 language (Hangul script). Korean Standard. Final byte of ISO 2022
974 (*Note ISO 2022::) is 04/03 (`C').
977 Korea Industrial Standards Association, "Code for Information
978 Interchange (Hangul and Hanja)", KS C 5601:1987.
981 File: tm-en.info, Node: media type, Next: message, Prev: KS C5601, Up: Glossary
986 *media type* specifies the nature of the data in the body of MIME
987 (*Note MIME::) entity (*Note entity::). It consists of *type* and
988 *subtype*. It is defined in RFC 2046 (*Note RFC 2046::).
990 Currently there are following types:
1002 * *multipart* (*Note multipart::)
1006 And there are various subtypes, for example,
1007 application/octet-stream, audio/basic, image/jpeg, multipart/mixed
1008 (*Note multipart/mixed::), text/plain (*Note text/plain::),
1011 You can refer registered media types at MEDIA TYPES
1012 (ftp://ftp.isi.edu/in-notes/iana/assignments/media-types).
1014 In addition, you can use private type or subtype using *x-token*,
1015 which as the prefix `x-'. However you can not use them in public.
1017 (cf. *Note Content-Type field::)
1020 File: tm-en.info, Node: message, Next: message/rfc822, Prev: media type, Up: Glossary
1025 In this document, it means mail defined in RFC 822 (*Note RFC 822::)
1026 and news message defined in RFC 1036 (*Note RFC 1036::).
1029 File: tm-en.info, Node: message/rfc822, Next: method, Prev: message, Up: Glossary
1034 *message/rfc822* indicates that the body contains an encapsulated
1035 message, with the syntax of an RFC 822 (*Note RFC 822::) message. It is
1036 the replacement of traditional RFC 934 (*Note RFC 934::) encapsulation.
1037 It is defined in RFC 2046 (*Note RFC 2046::).
1040 File: tm-en.info, Node: method, Next: MIME, Prev: message/rfc822, Up: Glossary
1045 Application program of tm-view to process for specified media type
1046 (*Note media type::) when user plays an entity.
1048 There are two kinds of methods, *internal method* and *external
1049 method*. Internal method is written by Emacs Lisp. External method is
1050 written by C or script languages and called by asynchronous process
1053 (cf. *Note (tm-view-en)method::)
1056 File: tm-en.info, Node: MIME, Next: MIME charset, Prev: method, Up: Glossary
1061 MIME stands for *Multipurpose Internet Mail Extensions*, it is an
1062 extension for RFC 822 (*Note RFC 822::).
1064 According to RFC 2045:
1066 STD 11, RFC 822, defines a message representation protocol specifying
1067 considerable detail about US-ASCII message headers, and leaves the
1068 message content, or message body, as flat US-ASCII text. This set of
1069 documents, collectively called the Multipurpose Internet Mail
1070 Extensions, or MIME, redefines the format of messages to allow for
1072 1. textual message bodies in character sets other than US-ASCII,
1074 2. an extensible set of different formats for non-textual message
1077 3. multi-part message bodies, and
1079 4. textual header information in character sets other than US-ASCII.
1081 It is defined in RFC 2045 (*Note RFC 2045::), RFC 2046 (*Note RFC
1082 2046::), RFC 2047 (*Note encoded-word::), RFC 2048 (*Note RFC 2048::)
1083 and RFC 2049 (*Note RFC 2049::).
1086 File: tm-en.info, Node: MIME charset, Next: MTA, Prev: MIME, Up: Glossary
1091 Coded character set (*Note coded character set::) used in
1092 Content-Type field (*Note Content-Type field::) or charset parameter of
1093 encoded-word (*Note encoded-word::).
1095 It is defined in RFC 2045 (*Note RFC 2045::).
1097 iso-2022-jp (*Note iso-2022-jp::) or euc-kr (*Note euc-kr::) are
1098 kinds of it. (In this document, MIME charsets are written by small
1099 letters to distinguish graphic character set (*Note graphic character
1100 set::). For example, ISO 8859-1 is a graphic character set, and
1101 iso-8859-1 is a MIME charset)
1104 File: tm-en.info, Node: MTA, Next: MUA, Prev: MIME charset, Up: Glossary
1109 *Message Transfer Agent*. It means mail transfer programs (ex.
1110 sendmail) and news servers.
1115 File: tm-en.info, Node: MUA, Next: MULE, Prev: MTA, Up: Glossary
1120 *Message User Agent*. It means mail readers and news readers.
1125 File: tm-en.info, Node: MULE, Next: multipart, Prev: MUA, Up: Glossary
1130 Multilingual extension of GNU Emacs (*Note Emacs::) by HANDA
1134 Nishikimi M., Handa K. and Tomura S., "Mule: MULtilingual
1135 Enhancement to GNU Emacs", Proc. of INET'93, August, 1993.
1137 Now, FSF and HANDA Ken'ichi et al. are working to merge MULE feature
1138 into Emacs, there is alpha version of mule merged emacs
1139 (ftp://etlport.etl.go.jp/pub/mule/mule-19.33-delta.taz).
1141 In addition, there is XEmacs with mule feature.
1143 So now, there are 3 kinds of mule variants.
1145 In this document, *mule* means any mule variants, *MULE* means
1146 original MULE (..2.3), *Emacs/mule* means mule merged Emacs,
1147 *XEmacs/mule* means XEmacs with mule feature.
1150 File: tm-en.info, Node: multipart, Next: multipart/alternative, Prev: MULE, Up: Glossary
1155 *multipart* means media type (*Note media type::) to insert multiple
1156 entities (*Note entity::) in a single body. Or it also indicates a
1157 message consists of multiple entities.
1159 There are following subtypes registered in RFC 2046 (*Note RFC
1162 * multipart/mixed (*Note multipart/mixed::)
1164 * multipart/alternative (*Note multipart/alternative::)
1166 * multipart/digest (*Note multipart/digest::)
1168 * multipart/parallel (*Note multipart/parallel::)
1170 and registered in RFC 1847 (*Note Security multipart::):
1172 * multipart/signed (*Note multipart/signed::)
1174 * multipart/encrypted (*Note multipart/encrypted::)
1177 File: tm-en.info, Node: multipart/alternative, Next: multipart/digest, Prev: multipart, Up: Glossary
1179 multipart/alternative
1180 ---------------------
1182 *multipart/digest* is one of multipart (*Note multipart::) media
1183 types. This type is syntactically identical to multipart/mixed (*Note
1184 multipart/mixed::), but the semantics are different. In particular,
1185 each of the body parts is an "alternative" version of the same
1188 (cf. *Note RFC 2046::)
1191 File: tm-en.info, Node: multipart/digest, Next: multipart/encrypted, Prev: multipart/alternative, Up: Glossary
1196 *multipart/digest* is one of multipart (*Note multipart::) media
1197 types. This type is syntactically identical to multipart/mixed (*Note
1198 multipart/mixed::), but the semantics are different. In particular, in
1199 a digest, the default Content-Type value for a body part is changed
1200 from text/plain (*Note text/plain::) to message/rfc822 (*Note
1203 This is the replacement of traditional RFC 1153 (*Note RFC 1153::)
1204 based encapsulation (*Note encapsulation::).
1206 (cf. *Note RFC 2046::)
1209 File: tm-en.info, Node: multipart/encrypted, Next: multipart/mixed, Prev: multipart/digest, Up: Glossary
1214 It is a Security multipart (*Note Security multipart::) defined in
1215 RFC 1847, used to represent encrypted message.
1217 (cf. *Note PGP/MIME::)
1220 File: tm-en.info, Node: multipart/mixed, Next: multipart/parallel, Prev: multipart/encrypted, Up: Glossary
1225 Primary and default subtype of multipart (*Note multipart::), it is
1226 used when the body parts are independent and need to be bundled in a
1229 (cf. *Note RFC 2046::)
1232 File: tm-en.info, Node: multipart/parallel, Next: multipart/signed, Prev: multipart/mixed, Up: Glossary
1237 *multipart/parallel* is a subtype of multipart (*Note multipart::).
1238 This type is syntactically identical to multipart/mixed (*Note
1239 multipart/mixed::), but the semantics are different. In particular, in
1240 a parallel entity, the order of body parts is not significant.
1242 (cf. *Note RFC 2046::)
1245 File: tm-en.info, Node: multipart/signed, Next: PGP, Prev: multipart/parallel, Up: Glossary
1250 It is a Security multipart (*Note Security multipart::) defined in
1251 RFC 1847, used to represent signed message.
1253 (cf. *Note PGP/MIME::)
1256 File: tm-en.info, Node: PGP, Next: PGP-kazu, Prev: multipart/signed, Up: Glossary
1261 A public key encryption program by Phil Zimmermann. It provides
1262 encryption and signature for message (*Note message::). PGP stands for
1263 *Pretty Good Privacy*.
1265 Traditional PGP uses RFC 934 (*Note RFC 934::) encapsulation (*Note
1266 encapsulation::). It is conflict with MIME (*Note MIME::). So
1267 PGP/MIME (*Note PGP/MIME::) is defined. On the other hand, PGP-kazu
1268 (*Note PGP-kazu::) was proposed to use PGP encapsulation in MIME. But
1272 D. Atkins, W. Stallings and P. Zimmermann, "PGP Message Exchange
1273 Formats", August 1996, Informational.
1276 File: tm-en.info, Node: PGP-kazu, Next: PGP/MIME, Prev: PGP, Up: Glossary
1281 In this document, *PGP-kazu* means a method to use traditional PGP
1282 encapsulation in MIME (*Note MIME::), proposed by YAMAMOTO Kazuhiko.
1284 PGP-kazu defines a media type (*Note media type::),
1287 In application/pgp entity, PGP encapsulation (*Note encapsulation::)
1288 is used. PGP encapsulation conflicts with MIME, so it requires
1289 PGP-processing to read as MIME message.
1291 It was obsoleted, so you should use PGP/MIME (*Note PGP/MIME::).
1292 However if you want to use traditional PGP message, it might be
1296 File: tm-en.info, Node: PGP/MIME, Next: Quoted-Printable, Prev: PGP-kazu, Up: Glossary
1301 PGP (*Note PGP::) and MIME (*Note MIME::) integration proposed by
1304 It is based on RFC 1847 (*Note Security multipart::), so it is
1305 harmonious with MIME, but it is not compatible with traditional PGP
1306 encapsulation. However MIME MUA can read PGP/MIME signed message even
1307 if it does not support PGP/MIME.
1309 PGP/MIME (*Note PGP/MIME::) will be standard of PGP message.
1311 [PGP/MIME: RFC 2015]
1312 M. Elkins, "MIME Security with Pretty Good Privacy (PGP)", October
1313 1996, Standards Track.
1316 File: tm-en.info, Node: Quoted-Printable, Next: RFC 821, Prev: PGP/MIME, Up: Glossary
1321 *Quoted-Printable* is a transfer encoding method of MIME (*Note
1322 MIME::) defined in RFC 2045 (*Note RFC 2045::).
1324 If the data being encoded are mostly US-ASCII text, the encoded form
1325 of the data remains largely recognizable by humans.
1327 (cf. *Note Base64::)
1330 File: tm-en.info, Node: RFC 821, Next: RFC 822, Prev: Quoted-Printable, Up: Glossary
1336 J. Postel, "Simple Mail Transfer Protocol", August 1982, STD 10.
1339 File: tm-en.info, Node: RFC 822, Next: RFC 934, Prev: RFC 821, Up: Glossary
1344 A RFC defines format of Internet mail message, mainly *message
1348 news message is based on RFC 822, so *Internet message* may be
1349 more suitable than *Internet mail* .
1352 D. Crocker, "Standard for the Format of ARPA Internet Text
1353 Messages", August 1982, STD 11.
1356 File: tm-en.info, Node: RFC 934, Next: RFC 1036, Prev: RFC 822, Up: Glossary
1361 A RFC defines an *encapsulation* (*Note encapsulation::) method for
1362 Internet mail (*Note RFC 822::).
1364 It conflicts with MIME (*Note MIME::), so you should use
1365 message/rfc822 (*Note message/rfc822::).
1368 Marshall T. Rose and Einar A. Stefferud, "Proposed Standard for
1369 Message Encapsulation", January 1985.
1372 File: tm-en.info, Node: RFC 1036, Next: RFC 1153, Prev: RFC 934, Up: Glossary
1377 A RFC defines format of USENET message. It is a subset of RFC 822
1378 (*Note RFC 822::). It is not Internet standard, but a lot of netnews
1379 excepting Usenet uses it.
1382 M. Horton and R. Adams, "Standard for Interchange of USENET
1383 Messages", December 1987, (obsolete RFC 850).
1386 File: tm-en.info, Node: RFC 1153, Next: RFC 1557, Prev: RFC 1036, Up: Glossary
1392 F. Wancho, "Digest Message Format", April 1990.
1395 File: tm-en.info, Node: RFC 1557, Next: RFC 1922, Prev: RFC 1153, Up: Glossary
1400 A RFC defines MIME charset (*Note MIME charset::)s for Korean, euc-kr
1401 (*Note euc-kr::) and iso-2022-kr (*Note iso-2022-kr::).
1404 U. Choi, K. Chon and H. Park, "Korean Character Encoding for
1405 Internet Messages", December 1993, Informational.
1408 File: tm-en.info, Node: RFC 1922, Next: RFC 2045, Prev: RFC 1557, Up: Glossary
1413 A RFC defines MIME charset (*Note MIME charset::)s for Chinese,
1414 iso-2022-cn (*Note iso-2022-cn::), iso-2022-cn-ext (*Note
1415 iso-2022-cn-ext::), cn-gb (*Note cn-gb::), cn-big5 (*Note cn-big5::),
1418 In addition, it defines additional parameters of Content-Type field
1419 (*Note Content-Type field::) field, *charset-edition* and
1420 *charset-extension*.
1423 Zhu, HF., Hu, DY., Wang, ZG., Kao, TC., Chang, WCH. and Crispin,
1424 M., "Chinese Character Encoding for Internet Messages", March 1996,
1428 File: tm-en.info, Node: RFC 2045, Next: RFC 2046, Prev: RFC 1922, Up: Glossary
1434 N. Freed and N. Borenstein, "Multipurpose Internet Mail Extensions
1435 (MIME) Part One: Format of Internet Message Bodies", November 1996,
1436 Standards Track (obsolete RFC 1521, 1522, 1590).
1439 File: tm-en.info, Node: RFC 2046, Next: RFC 2048, Prev: RFC 2045, Up: Glossary
1445 N. Freed and N. Borenstein, "Multipurpose Internet Mail Extensions
1446 (MIME) Part Two: Media Types", November 1996, Standards Track
1447 (obsolete RFC 1521, 1522, 1590).
1450 File: tm-en.info, Node: RFC 2048, Next: RFC 2049, Prev: RFC 2046, Up: Glossary
1456 N. Freed, J. Klensin and J. Postel, "Multipurpose Internet Mail
1457 Extensions (MIME) Part Four: Registration Procedures", November
1458 1996, Standards Track (obsolete RFC 1521, 1522, 1590).
1461 File: tm-en.info, Node: RFC 2049, Next: plain text, Prev: RFC 2048, Up: Glossary
1467 N. Freed and N. Borenstein, "Multipurpose Internet Mail Extensions
1468 (MIME) Part Five: Conformance Criteria and Examples", November
1469 1996, Standards Track (obsolete RFC 1521, 1522, 1590).
1472 File: tm-en.info, Node: plain text, Next: Security multipart, Prev: RFC 2049, Up: Glossary
1477 A textual data represented by only coded character set (*Note coded
1478 character set::). It does not have information about font or
1479 typesetting. (cf. *Note text/plain::)
1482 File: tm-en.info, Node: Security multipart, Next: text/enriched, Prev: plain text, Up: Glossary
1487 A format to represent signed/encrypted message in MIME (*Note
1490 It defines two multipart media types, *multipart/signed* (*Note
1491 multipart/signed::) and *multipart/encrypted* (*Note
1492 multipart/encrypted::).
1494 MOSS and PGP/MIME (*Note PGP/MIME::) are based on it.
1496 [Security multipart: RFC 1847]
1497 James Galvin, Gale Murphy, Steve Crocker and Ned Freed, "Security
1498 Multiparts for MIME: Multipart/Signed and Multipart/Encrypted",
1499 October 1995, Standards Track.
1502 File: tm-en.info, Node: text/enriched, Next: text/plain, Prev: Security multipart, Up: Glossary
1507 [text/enriched: RFC 1896]
1508 P. Resnick and A. Walker, "The text/enriched MIME Content-type",
1509 February 1996, (obsolete RFC 1563).
1512 File: tm-en.info, Node: text/plain, Next: tm-kernel, Prev: text/enriched, Up: Glossary
1517 *text/plain* is a media type (*Note media type::) for plain text
1518 (*Note plain text::), defined in RFC 2046 (*Note RFC 2046::).
1520 The default media type of "text/plain; charset=us-ascii" for Internet
1521 mail describes existing Internet practice. That is, it is the type of
1522 body defined by RFC 822 (*Note RFC 822::).
1524 (cf. *Note MIME charset::) (cf. *Note us-ascii::)
1527 File: tm-en.info, Node: tm-kernel, Next: tm-MUA, Prev: text/plain, Up: Glossary
1532 A libraries to provide user interface about MIME (*Note MIME::) for
1533 emacs. tm stands for `tools for MIME'.
1535 *[Unimportant notice(^-^;]*
1536 * tm may not stand for "tiny-mime"(^-^;
1538 * tm may not stand for initial of an author (^-^;
1540 * "Tools for MIME" may be strained (^-^;
1543 File: tm-en.info, Node: tm-MUA, Next: us-ascii, Prev: tm-kernel, Up: Glossary
1548 MUA (*Note MUA::) or MUA extender using tm (*Note tm-kernel::).
1550 *tm oomori package* has following extenders:
1552 * *tm-mh-e* (*Note (tm-mh-e-en)::) for mh-e (*Note (mh-e)::)
1554 * *tm-gnus* (*Note (tm-gnus_en)::) for GNUS
1556 * *gnus-mime* (*Note (gnus-mime-en)::) for Gnus
1558 * *tm-vm* (*Note (tm-vm_en)::) for VM
1560 * *tm-rmail* for RMAIL
1563 File: tm-en.info, Node: us-ascii, Prev: tm-MUA, Up: Glossary
1568 A MIME charset (*Note MIME charset::) for primary Latin script mainly
1569 written by English or other languages.
1571 It is a 7bit coded character set (*Note coded character set::) based
1572 on ISO 2022 (*Note ISO 2022::), it contains only ASCII (*Note ASCII::)
1573 and code extension (*Note code extension::) is not allowed.
1575 It is standard coded character set of Internet mail. If MIME
1576 charset is not specified, *us-ascii* is used as default.
1578 In addition, *ASCII* of RFC 822 (*Note RFC 822::) should be
1579 interpreted as us-ascii.
1582 File: tm-en.info, Node: Setting, Next: Bug report, Prev: Introduction, Up: Top
1587 In the tm package, two files, `mime-setup.el' and `tm-setup.el', are
1588 provided to ease the setup.
1590 The `mime-setup.el' is used for the whole MIME related setup
1591 including MIME encoding using `tm-edit.el', while `tm-setup.el' is used
1592 to set up tm-MUA only.
1596 * mime-setup:: Normal setting
1597 * tm-setup:: Setting not to use tm-edit
1598 * setting for VM:: Setting for VM
1599 * manual setting:: Setting up without loading provided setup files
1602 File: tm-en.info, Node: mime-setup, Next: tm-setup, Prev: Setting, Up: Setting
1607 If you want normal setting, please use *mime-setup*. For example,
1608 please insert following into `~/.emacs':
1612 As `mime-setup.el' loads `tm-setup.el', you don't need to load
1613 `tm-setup.el' when you use `mime-setup.el' (Description of old version
1614 of Gnus FAQ is wrong!)
1619 * Notice about GNUS:: Notices for GNUS
1622 File: tm-en.info, Node: signature, Next: Notice about GNUS, Prev: mime-setup, Up: mime-setup
1627 You can set up the *automatic signature selection tool* using
1628 `mime-setup'. If you want to automatically select the signature file
1629 depending on how the message headers show, add lines like shown below
1630 to your .emacs (Refer to the reference manual of `signature.el' for
1633 (setq signature-file-alist
1634 '((("Newsgroups" . "jokes") . "~/.signature-jokes")
1635 (("Newsgroups" . ("zxr" "nzr")) . "~/.signature-sun")
1636 (("To" . ("ishimaru" "z-suzuki")) . "~/.signature-sun")
1637 (("To" . "tea") . "~/.signature-jokes")
1638 (("To" . ("sim" "oku" "takuo")) . "~/.signature-formal")
1641 - Variable: mime-setup-use-signature
1642 If it is not `nil', `mime-setup.el' sets up for `signature.el'.
1643 Its default value is `t'.
1645 - Variable: mime-setup-signature-key-alist
1646 It defines key to bind signature inserting command for each
1647 major-mode. Its default value is following:
1649 ((mail-mode . "\C-c\C-w"))
1651 If you want to change, please rewrite it. For example:
1653 (set-alist 'mime-setup-signature-key-alist
1654 'news-reply-mode "\C-c\C-w")
1657 - Variable: mime-setup-default-signature-key
1658 If key to bind signature inserting command for a major-mode is not
1659 found from `mime-setup-signature-key-alist', its value is used as
1660 key. Its default value is `"\C-c\C-s"'.
1663 File: tm-en.info, Node: Notice about GNUS, Prev: signature, Up: mime-setup
1668 When `mime-setup.el' sets up for `signature.el', it sets variable
1669 `gnus-signature-file' to `nil'. Therefore GNUS does not insert
1670 signature automatically when it is sending a message. Reason of this
1671 setting is following:
1673 GNUS inserts signature after `tm-edit.el' composed as MIME message.
1674 Therefore signature inserted by GNUS is not processed as a valid MIME
1675 part. In particular, for multipart message, signature places in outside
1676 of MIME part. So MIME MUA might not display it.
1678 Other notice is key bind. In historical reason, key bind to insert
1679 signature is `C-c C-s' (like mh-e (*Note (mh-e)::)) instead of `C-c
1680 C-w'. If you change to GNUS's default, please set following:
1682 (set-alist 'mime-setup-signature-key-alist 'news-reply-mode "\C-c\C-w")
1685 File: tm-en.info, Node: tm-setup, Next: setting for VM, Prev: mime-setup, Up: Setting
1687 Setting not to use tm-edit
1688 ==========================
1690 *tm-setup* only sets up tm-MUA (*Note tm-MUA::)s. In other words,
1691 it is a setting to avoid to use tm-edit. If you don't want to compose
1692 MIME message or want to use other MIME composer, please use it instead
1695 For example, please insert following into `~/.emacs':
1700 If you use `mime-setup.el', you you don't need to load
1704 File: tm-en.info, Node: setting for VM, Next: manual setting, Prev: tm-setup, Up: Setting
1709 If you use *vm*, please insert following in `~/.vm':
1714 If you use *BBDB*, please insert `(require 'tm-vm)' *after*
1715 `(bbdb-insinuate-vm)'.
1718 File: tm-en.info, Node: manual setting, Prev: setting for VM, Up: Setting
1720 Setting up without loading provided setup files
1721 ===============================================
1723 You may find the valuable hints in `mime-setup.el' or `tm-setup.el'
1724 if you want to set up MIME environment without loading the tm-provided
1728 Current tm provides some convenient features to expect tm-edit, and
1729 they can not use if `mime-setup.el' is not used. If you want to
1730 set up original setting to use tm-edit, please declare following
1733 (provide 'mime-setup)
1737 File: tm-en.info, Node: Bug report, Next: Acknowledgments, Prev: Setting, Up: Top
1739 How to report bug and about mailing list of tm
1740 **********************************************
1742 If you write bug-reports and/or suggestions for improvement, please
1743 send them to the tm Mailing List:
1745 * Japanese <bug-tm-ja@chamonix.jaist.ac.jp>
1747 * English <bug-tm-en@chamonix.jaist.ac.jp>
1749 Notice that, we does not welcome bug reports about too old version.
1750 Bugs in old version might be fixed. So please try latest version at
1753 You should write *good bug report*. If you write only "tm does not
1754 work", we can not find such situations. At least, you should write
1755 name, type, variants and version of OS, emacs, tm and MUA, and setting.
1756 In addition, if error occurs, to send backtrace is very important. (cf.
1757 *Note (emacs)Bugs::)
1759 Bug may not appear only your environment, but also in a lot of
1760 environment (otherwise it might not bug). Therefor if you send mail to
1761 author directly, we must write a lot of mails. So please send mail to
1762 address for tm bugs instead of author.
1764 Via the tm ML, you can report tm bugs, obtain the latest release of
1765 tm, and discuss future enhancements to tm. To join the tm ML, send
1768 * Japanese <tm-ja-admin@chamonix.jaist.ac.jp>
1770 * English <tm-en-admin@chamonix.jaist.ac.jp>
1772 Since the user registration is done manually, please write the mail
1773 body in human-recognizable language (^_^).
1776 File: tm-en.info, Node: Acknowledgments, Next: Concept Index, Prev: Bug report, Up: Top
1781 I thank MASUTANI Yasuhiro. He requested me a lot of important
1782 features and gave me a lot of suggestions when tm-view was born.
1783 tm-view is based on his influence.
1785 I thank ENAMI Tsugutomo for work of `mime.el', which is an origin of
1786 `tm-ew-d.el' and `mel-b.el', and permission to rewrite for tm.
1788 I thank OKABE Yasuo for work of internal method for LaTeX and
1789 automatic assembling method for message/partial. I thank UENO Hiroshi
1790 for work of internal method for tar archive.
1792 I thank UMEDA Masanobu for his work of `mime.el', which is the
1793 origin of tm-edit, and permission to rewrite his work as tm-edit.
1795 I thank KOBAYASHI Shuhei for his work as a tm maintainer. In
1796 addition, he often points out or suggests about conformity with RFCs.
1798 I thank Oscar Figueiredo for his work as the maintainer of tm-vm. He
1799 improves tm-vm and wrote a good manual of tm-vm.
1801 Last of all, I thank members of two tm mailing lists, Japanese and
1805 File: tm-en.info, Node: Concept Index, Next: Variable Index, Prev: Acknowledgments, Up: Top
1813 * 7bit (textual) string: 7bit.
1816 * 8bit (textual) string: 8bit.
1818 * 94-character set: 94-character set.
1819 * 94x94-character set: 94x94-character set.
1820 * 96-character set: 96-character set.
1821 * ANSI X3.4:1986: ASCII.
1822 * application: media type.
1823 * application/pgp: PGP-kazu.
1825 * ASCII <1>: us-ascii.
1827 * audio: media type.
1828 * automatic signature selection tool: signature.
1830 * BBDB: setting for VM.
1833 * charset-edition: RFC 1922.
1834 * charset-extension: RFC 1922.
1835 * CNS 11643:1992: CNS 11643.
1836 * CNS 11643-1992: CNS 11643.
1838 * encapsulation: RFC 934.
1840 * Experimental: Content-Disposition.
1841 * external method: method.
1844 * GB 2312:1980: GB 2312.
1845 * GB 8565.2: GB 8565.2.
1846 * GB 8565.2:1988: GB 8565.2.
1847 * gnus-mime: tm-MUA.
1848 * good bug report: Bug report.
1849 * image: media type.
1850 * Informational <1>: hz-gb2312.
1851 * Informational <1>: RFC 1557.
1852 * Informational <1>: RFC 1922.
1853 * Informational <1>: hz-gb2312.
1854 * Informational <1>: iso-2022-jp-2.
1855 * Informational <1>: iso-8859-7.
1856 * Informational: PGP.
1857 * internal method: method.
1858 * Internet mail: RFC 822.
1859 * Internet message: RFC 822.
1860 * ISO 2022: ISO 2022.
1862 * ISO 8859-1: ISO 8859-1.
1863 * ISO 8859-1:1987: ISO 8859-1.
1864 * ISO 8859-2: ISO 8859-2.
1865 * ISO 8859-2:1987: ISO 8859-2.
1866 * ISO 8859-3: ISO 8859-3.
1867 * ISO 8859-3:1988: ISO 8859-3.
1868 * ISO 8859-4: ISO 8859-4.
1869 * ISO 8859-4:1988: ISO 8859-4.
1870 * ISO 8859-5: ISO 8859-5.
1871 * ISO 8859-5:1988: ISO 8859-5.
1872 * ISO 8859-6: ISO 8859-6.
1873 * ISO 8859-6:1987: ISO 8859-6.
1874 * ISO 8859-7: ISO 8859-7.
1875 * ISO 8859-7:1987: ISO 8859-7.
1876 * ISO 8859-8: ISO 8859-8.
1877 * ISO 8859-8:1988: ISO 8859-8.
1878 * ISO 8859-9: ISO 8859-9.
1879 * ISO 8859-9:1990: ISO 8859-9.
1880 * iso-2022-jp: iso-2022-jp.
1881 * iso-2022-jp-2: iso-2022-jp-2.
1882 * iso-8859-1: iso-8859-1.
1883 * iso-8859-2: iso-8859-2.
1884 * iso-8859-5: iso-8859-5.
1885 * iso-8859-7: iso-8859-7.
1886 * ISO/IEC 2022:1994: ISO 2022.
1887 * ISO/IEC 646:1991: ISO 646.
1888 * JIS X 0201-1976:: JIS X0201.
1889 * JIS X0208:1983,1990: JIS X0208.
1890 * JIS C6220-1976: JIS X0201.
1891 * JIS C6226:1978: JIS X0208.
1892 * JIS X 0208:1997? draft: JIS X0208.
1893 * JIS X 0201:1997? draft: JIS X0201.
1894 * JIS X0201-1976: JIS X0201.
1895 * JIS X0201-1997?: JIS X0201.
1896 * JIS X0208-1978: JIS X0208.
1897 * JIS X0208-1983,1990: JIS X0208.
1898 * JIS X0208-1997?: JIS X0208.
1899 * KS C 5601:1987: KS C5601.
1900 * KS C 5861:1992: euc-kr.
1901 * KS C5601: KS C5601.
1902 * media type: media type.
1903 * message: media type.
1904 * message header: RFC 822.
1905 * Message Transfer Agent: MTA.
1906 * Message User Agent: MUA.
1907 * message/rfc822: message/rfc822.
1908 * mime-setup: mime-setup.
1910 * multipart <1>: media type.
1911 * multipart: multipart.
1912 * multipart/digest <1>: multipart/alternative.
1913 * multipart/digest: multipart/digest.
1914 * multipart/encrypted: Security multipart.
1915 * multipart/parallel: multipart/parallel.
1916 * multipart/signed: Security multipart.
1917 * Multipurpose Internet Mail Extensions: MIME.
1919 * parameter: Content-Type field.
1921 * PGP-kazu: PGP-kazu.
1922 * PGP/MIME: PGP/MIME.
1923 * Pretty Good Privacy: PGP.
1924 * Quoted-Printable: Quoted-Printable.
1925 * RFC 1036: RFC 1036.
1926 * RFC 1153: RFC 1153.
1927 * RFC 1468: iso-2022-jp.
1929 * RFC 1554: iso-2022-jp-2.
1930 * RFC 1557: RFC 1557.
1931 * RFC 1806: Content-Disposition.
1932 * RFC 1842: hz-gb2312.
1933 * RFC 1843: hz-gb2312.
1934 * RFC 1847: Security multipart.
1935 * RFC 1896: text/enriched.
1936 * RFC 1922: RFC 1922.
1937 * RFC 1947: iso-8859-7.
1939 * RFC 2015: PGP/MIME.
1940 * RFC 2045: RFC 2045.
1941 * RFC 2046: RFC 2046.
1942 * RFC 2047: encoded-word.
1943 * RFC 2048: RFC 2048.
1944 * RFC 2049: RFC 2049.
1949 * Security multipart: Security multipart.
1951 * Standards Track <1>: PGP/MIME.
1952 * Standards Track <1>: RFC 2046.
1953 * Standards Track <1>: RFC 2049.
1954 * Standards Track <1>: Security multipart.
1955 * Standards Track <1>: encoded-word.
1956 * Standards Track <1>: RFC 2045.
1957 * Standards Track: RFC 2048.
1961 * subtype <1>: Content-Type field.
1962 * subtype: media type.
1964 * text/enriched: text/enriched.
1965 * text/plain: text/plain.
1966 * tm oomori package: tm-MUA.
1970 * tm-setup: tm-setup.
1972 * type <1>: media type.
1973 * type: Content-Type field.
1974 * us-ascii: us-ascii.
1976 * video: media type.
1977 * vm: setting for VM.
1978 * x-token: media type.
1979 * XEmacs/mule: MULE.
1982 File: tm-en.info, Node: Variable Index, Prev: Concept Index, Up: Top
1989 * mime-setup-default-signature-key: signature.
1990 * mime-setup-signature-key-alist: signature.
1991 * mime-setup-use-signature: signature.
1997 Node: Introduction
\7f497
1998 Node: Glossary
\7f1167
2001 Node: 94-character set
\7f5292
2002 Node: 96-character set
\7f5659
2003 Node: 94x94-character set
\7f6010
2008 Node: cn-big5
\7f8249
2009 Node: CNS 11643
\7f8834
2010 Node: coded character set
\7f9583
2011 Node: code extension
\7f9918
2012 Node: Content-Disposition
\7f10207
2013 Node: Content-Type field
\7f10652
2015 Node: encoded-word
\7f11924
2016 Node: encapsulation
\7f12344
2017 Node: entity
\7f12642
2018 Node: euc-kr
\7f12929
2020 Node: GB 2312
\7f13618
2021 Node: GB 8565.2
\7f14076
2022 Node: graphic character set
\7f14513
2023 Node: hz-gb2312
\7f14737
2024 Node: ISO 2022
\7f15576
2025 Node: iso-2022-cn
\7f15985
2026 Node: iso-2022-cn-ext
\7f16457
2027 Node: iso-2022-jp
\7f17107
2028 Node: iso-2022-jp-2
\7f17819
2029 Node: iso-2022-kr
\7f18236
2030 Node: ISO 646
\7f18676
2031 Node: ISO 8859-1
\7f18966
2032 Node: iso-8859-1
\7f19283
2033 Node: ISO 8859-2
\7f19757
2034 Node: iso-8859-2
\7f20077
2035 Node: ISO 8859-3
\7f20551
2036 Node: ISO 8859-4
\7f20871
2037 Node: ISO 8859-5
\7f21191
2038 Node: iso-8859-5
\7f21515
2039 Node: ISO 8859-6
\7f21957
2040 Node: ISO 8859-7
\7f22279
2041 Node: iso-8859-7
\7f22600
2042 Node: ISO 8859-8
\7f23150
2043 Node: ISO 8859-9
\7f23472
2044 Node: ISO-IR-165
\7f23792
2045 Node: JIS X0201
\7f24275
2046 Node: JIS C6226
\7f24969
2047 Node: JIS X0208
\7f25221
2048 Node: JIS X0212
\7f26675
2049 Node: koi8-r
\7f26999
2050 Node: KS C5601
\7f27467
2051 Node: media type
\7f27885
2052 Node: message
\7f28839
2053 Node: message/rfc822
\7f29079
2054 Node: method
\7f29460
2056 Node: MIME charset
\7f30936
2060 Node: multipart
\7f32709
2061 Node: multipart/alternative
\7f33458
2062 Node: multipart/digest
\7f33923
2063 Node: multipart/encrypted
\7f34580
2064 Node: multipart/mixed
\7f34878
2065 Node: multipart/parallel
\7f35211
2066 Node: multipart/signed
\7f35658
2068 Node: PGP-kazu
\7f36619
2069 Node: PGP/MIME
\7f37255
2070 Node: Quoted-Printable
\7f37880
2071 Node: RFC 821
\7f38274
2072 Node: RFC 822
\7f38470
2073 Node: RFC 934
\7f38878
2074 Node: RFC 1036
\7f39309
2075 Node: RFC 1153
\7f39716
2076 Node: RFC 1557
\7f39886
2077 Node: RFC 1922
\7f40254
2078 Node: RFC 2045
\7f40886
2079 Node: RFC 2046
\7f41202
2080 Node: RFC 2048
\7f41496
2081 Node: RFC 2049
\7f41811
2082 Node: plain text
\7f42130
2083 Node: Security multipart
\7f42424
2084 Node: text/enriched
\7f43052
2085 Node: text/plain
\7f43322
2086 Node: tm-kernel
\7f43812
2087 Node: tm-MUA
\7f44229
2088 Node: us-ascii
\7f44681
2089 Node: Setting
\7f45296
2090 Node: mime-setup
\7f45903
2091 Node: signature
\7f46392
2092 Node: Notice about GNUS
\7f47928
2093 Node: tm-setup
\7f48813
2094 Node: setting for VM
\7f49366
2095 Node: manual setting
\7f49679
2096 Node: Bug report
\7f50283
2097 Node: Acknowledgments
\7f51737
2098 Node: Concept Index
\7f52830
2099 Node: Variable Index
\7f61554