1 <!doctype sinfo system>
3 <title>FLIM 1.9 Manual about MIME Features
4 <author>MORIOKA Tomohiko <mail>morioka@jaist.ac.jp</mail>
14 This file documents MIME features of FLIM, a Internet message
15 parsing/encoding library for GNU Emacs.
22 FLIM is a library to provide basic features about message
23 representation or encoding.
26 <h1> How to use MIME features
29 Please eval following to use MIME features provided by FLIM:
36 <h1> Message and Entity
39 According to <dref>RFC 2045</dref>, `The term ``entity'', refers
40 specifically to the MIME-defined header fields and contents of either
41 a message or one of the parts in the body of a multipart entity.' In
42 this document, the term <concept>entity</concept> indicates all of
43 header fields and body.
45 The definition of RFC 2045 indicates that a MIME message is a tree,
46 and each node of the tree is an entity. Namely MIME extends message
49 FLIM uses <concept>mime-entity</concept> structure to represent
50 information of entity. In this document, it is called simply
54 <h2> Functions to create mime-entity
55 <node> Entity creation
57 <defun name="mime-open-entity">
60 Open an entity and return it.
62 <var>type</var> is representation-type. <cf node="mm-backend">
64 <var>location</var> is location of entity. Specification of it is
65 depended on representation-type.
68 <defun name="mime-parse-buffer">
71 Parse <var>buffer</var> as message, and set the result to buffer local
72 variable <code>mime-message-structure</code> of <var>buffer</var> as
75 If <var>buffer</var> is omitted, current buffer is used.
77 <var>type</var> is representation-type of created mime-entity. <cf
78 node="mm-backend"> Default value is <var>buffer</var>.
82 <h2> Features about message tree
83 <node> Entity hierarchy
85 Structure of a MIME message is tree.
87 In the tree, root node is the entity indicates all of the message. In
88 this document, it is called <concept>root-entity</concept> or
89 <concept>message</concept>. In FLIM, it is indicated by buffer local
90 variable <code>mime-message-structure</code>.
92 Each entity except root-entity has a parent. An entity may have
93 children. We can indicate an entity by relative position from a base
94 entity, based on the parent-child relationship.
96 In addition, we can indicate an entity by absolute position of the
99 Each entity, which is a node of the tree, can be numbered by
100 depth and left-to-right order of the depth.
106 +-------------------+-------------------+
110 | +---------+---------+ |
111 +--+--+ +--+--+ +--+--+ +--+--+ +--+--+
112 | 0.0 | | 1.0 | | 1.1 | | 1.2 | | 2.0 |
113 +-----+ +-----+ +-----+ +-----+ +-----+
117 Namely, if depth of a node is n, the node has a node-number, which is
118 consists of n integers. In this document, it is called
119 <concept>entity-number</concept>. An entity-number is represented by
120 list of integer, like <code>(1 2 3)</code>.
122 mime-entity has also <concept>node-id</concept>. A node-id is
123 represented by reversed list of entity-number. For example, node-id
124 corresponding with 1.2.3 is <code>(3 2 1)</code>.
126 Each entity can be indicated by entity-number or node-id in
127 <code>mime-message-structure</code>.
129 <defvar name="mime-message-structure">
131 Buffer local variable to store mime-entity structure of message.
134 <defun name="mime-entity-children">
137 Return list of entities included in the <var>entity</var>.
140 <defun name="mime-entity-parent">
141 <args> entity <opts> message
143 Return parent entity of the <var>entity</var>.
145 If <var>message</var> is specified, it is regarded as root instead of
146 <code>mime-message-structure</code>.
149 <defun name="mime-root-entity-p">
152 Return non-<code>nil</code> if <var>entity</var> is root entity
156 <defun name="mime-entity-node-id">
159 Return node-id of <var>entity</var>.
162 <defun name="mime-entity-number">
165 Return entity-number of <var>entity</var>.
168 <defun name="mime-find-entity-from-number">
169 <args> entity-number <opts> message
171 Return entity from <var>entity-number</var> in <var>message</var>.
173 If <var>message</var> is not specified,
174 <code>mime-message-structure</code> is used.
177 <defun name="mime-find-entity-from-node-id">
178 <args> entity-node-id <opts> message
180 Return entity from <var>entity-node-id</var> in <var>message</var>.
182 If <var>message</var> is not specified,
183 <code>mime-message-structure</code> is used.
187 <h2> Functions about attributes of mime-entity
188 <node> Entity Attributes
190 <defun name="mime-entity-content-type">
193 Return content-type of <var>entity</var>.
194 <cf node="mime-content-type">
197 <defun name="mime-entity-content-disposition">
200 Return content-disposition of <var>entity</var>. <cf
201 node="mime-content-disposition">
204 <defun name="mime-entity-filename">
207 Return file name of <var>entity</var>.
210 <defun name="mime-entity-encoding">
211 <args> entity <opts> default-encoding
213 Return content-transfer-encoding of <var>entity</var>.
214 <cf node="Content-Transfer-Encoding">
216 If the <var>entity</var> does not have Content-Transfer-Encoding
217 field, this function returns <var>default-encoding</var>. If it is
218 nil, <code>"7bit"</code> is used as default value.
221 <defun name="mime-entity-cooked-p">
224 Return non-nil if contents of <var>entity</var> has been already
229 <h2> Information of entity header
232 <defun name="mime-fetch-field">
233 <args> field-name <opts> entity
235 Return field-body of <var>field-name</var> field in header of
238 The results is network representation.
240 If <var>entity</var> is omitted, <code>mime-message-structure</code>
241 is used as default value.
243 If <var>field-name</var> field is not found, this function returns
247 <defun name="mime-read-field">
248 <args> field-name <opts> entity
250 Parse <var>field-name</var> field in header of <var>entity</var>, and
253 Format of result is depended on kind of field. For non-structured
254 field, this function returns string. For structured field, it returns
255 list corresponding with structure of the field.
257 Strings in the result will be converted to internal representation of
260 If <var>entity</var> is omitted, <code>mime-message-structure</code>
261 is used as default value.
263 If <var>field-name</var> field is not found, this function returns
267 <defun name="mime-insert-decoded-header">
268 <args> entity <opts> invisible-fields visible-fields
270 Insert before point a decoded contents of header of <var>entity</var>.
272 <var>invisible-fields</var> is list of regexps to match field-name to
273 hide. <var>visible-fields</var> is list of regexps to match
276 If a field-name is matched with some elements of
277 <var>invisible-fields</var> and matched with none of
278 <var>visible-fields</var>, this function don't insert the field.
282 <h2> Contents of Entity
283 <node> Entity-content
285 <defun name="mime-entity-content">
288 Return content of <var>entity</var> as byte sequence.
291 <defun name="mime-write-entity-content">
292 <args> entity filename
294 Write content of <var>entity</var> into <var>filename</var>.
297 <defun name="mime-write-entity">
298 <args> entity filename
300 Write representation of <var>entity</var> into <var>filename</var>.
303 <defun name="mime-write-entity-body">
304 <args> entity filename
306 Write body of <var>entity</var> into <var>filename</var>.
310 <h2> Entity as buffer representation
313 <defun name="mime-entity-buffer">
316 Return buffer, which contains <var>entity</var>.
319 <defun name="mime-entity-point-min">
322 Return the start point of <var>entity</var> in the buffer which
323 contains <var>entity</var>.
326 <defun name="mime-entity-point-max">
329 Return the end point of <var>entity</var> in the buffer which
330 contains <var>entity</var>.
333 <defun name="mime-entity-header-start">
336 Return the start point of header of <var>entity</var> in the buffer
337 which contains <var>entity</var>.
340 <defun name="mime-entity-header-end">
343 Return the end point of header of <var>entity</var> in the buffer
344 which contains <var>entity</var>.
347 <defun name="mime-entity-body-start">
350 Return the start point of body of <var>entity</var> in the buffer
351 which contains <var>entity</var>.
354 <defun name="mime-entity-body-end">
357 Return the end point of body of <var>entity</var> in the buffer which
358 contains <var>entity</var>.
362 <h2> Entity representations and implementations
365 Entity is an abstraction. It is designed to use various data
366 representations for their purposes.
368 Each entity has <concept>representation-type</concept>. It must be
369 specified when an entity is created. <cf node="Entity Creation">
371 Functions about entity are implemented by request processing to the
372 entity. Each entity knows its representation-type. Each entity calls
373 processing function corresponding with the representation-type. Such
374 kind of function is called <concept>entity processing
375 method</concept>. A module, consists of them corresponding with a
376 representation-type, is called <concept>mm-backend</concept>.
378 Module name of each mm-backend consists of the prefix <code>mm</code>
379 and its representation-type. The module is required automatically
380 when its entity is created at first.
383 <h3> Message-passing for entity
384 <node> Request for entity
386 <defun name="mime-entity-send">
387 <args> entity message <rest> args
389 Send <var>message</var> to <var>entity</var> with <var>args</var>, and
392 <var>args</var> is arguments of the <var>message</var>.
396 <h3> How to make mm-backend
397 <node> mm-backend module
399 (It is not written yet, sorry. (^_^;)
404 <h1> Information of Content-Type field
407 <concept>Content-Type field</concept> is a field to indicate kind of
408 contents or data format, such as <dref>media-type</dref> and MIME
409 charset. It is defined in <dref>RFC 2045</dref>.
413 Historically, Content-Type field was proposed in RFC 1049. In it,
414 Content-Type did not distinguish type and subtype, and there are no
415 mechanism to represent kind of character code like MIME charset.
419 FLIM provides parser for Content-Type field and structure
420 <concept>mime-content-type</concept> to store information of
424 <h2> Format of Content-Type field
425 <node> Content-Type field
427 Format of Content-Type field is defined as follows:
430 ``Content-Type'' ``:'' <concept>type</concept> ``/''
431 <concept>subtype</concept> *( ``;'' <concept>parameter</concept> )
438 Content-Type: image/jpeg
444 Content-Type: text/plain; charset=iso-2022-jp
448 `type' and `subtype' indicate format of an entity. In this document,
449 pair of them is called `media-type'. `image/jpeg' or `text/plain' is
454 If an entity does not have Content-Type field, it is regarded as
459 Content-Type: text/plain; charset=us-ascii
468 <h2> mime-content-type structure
469 <node> mime-content-type
471 <define type="Structure" name="mime-content-type">
473 Structure to store information of a Content-Type field.
475 Applications should use reference functions
476 <code>mime-content-type-SLOT</code> to refer information of the
479 Slots of the structure are following:
482 <dt>primary-type<dd>primary type of media-type (symbol).
484 <dt>subtype<dd>subtype of media-type (symbol).
486 <dt>parameters<dd>parameters of Content-Type field (association-list).
491 <defun name="make-mime-content-type">
494 <p>Constructor of content-type.
497 <defun name="mime-content-type-parameter">
498 <args> content-type parameter
500 Return value of <var>parameter</var> of <var>content-type</var>.
505 <node> Content-Type parser
507 <defun name="mime-parse-Content-Type">
510 Parse <var>string</var> as field-body of Content-Type field.
513 <defun name="mime-read-Content-Type">
515 Read field-body of Content-Type field from current-buffer,
516 and return parsed it.
518 Return <code>nil</code> if Content-Type field is not found.
522 <h2> Utility functions
523 <node> Content-Type utility
525 <defun name="mime-type/subtype-string">
526 <args> type <opts> subtype
528 Return type/subtype string from <var>type</var> and
533 <h1> Information of Content-Disposition field
534 <node> Content-Disposition
536 <concept>Content-Disposition field</concept> is an optional field to
537 specify presentation of an entity or attributes of an entity, such as
540 <rfc number="2183" type="Standards Track"
541 author="S. Dorner, K. Moore and R. Troost"
542 title="Communicating Presentation Information in
543 Internet Messages: The Content-Disposition Header"
546 FLIM provides parser for Content-Disposition field and structure
547 <concept>mime-content-disposition</concept> to store information of
548 Content-Disposition field.
551 <h2> mime-content-disposition structure
552 <node> mime-content-disposition
554 <define type="Structure" name="mime-content-disposition">
556 Structure to store information of a Content-Disposition field.
558 Applications should use reference functions
559 <code>mime-content-disposition-SLOT</code> to refer information of the
562 Slots of the structure are following:
565 <dt>disposition-type<dd>disposition-type (symbol).
567 <dt>parameters<dd>parameters of Content-Disposition field
573 <defun name="mime-content-disposition-parameter">
574 <args> content-disposition parameter
576 Return value of <var>parameter</var> of
577 <var>content-disposition</var>.
580 <defun name="mime-content-disposition-filename">
581 <args> content-disposition
583 Return filename of <var>content-disposition</var>.
587 <h2> Parser for Content-Disposition field
588 <node> Content-Disposition parser
590 <defun name="mime-parse-Content-Disposition">
593 Parse <var>string</var> as field-body of Content-Disposition field,
594 and return the result.
597 <defun name="mime-read-Content-Disposition">
599 Read field-body of Content-Disposition field from current-buffer,
601 Return nil if Content-Disposition field is not found.
606 <node> Content-Transfer-Encoding
608 <concept>Content-Transfer-Encoding field</concept> is a header field
609 to indicate body encoding of a entity.
611 FLIM provides parser functions for Content-Transfer-Encoding field.
612 They represent information of Content-Transfer-Encoding field as
615 In addition, FLIM provides encoder/decoder functions by
616 Content-Transfer-Encoding.
620 <node> Content-Transfer-Encoding parser
622 <defun name="mime-parse-Content-Transfer-Encoding">
625 <var>string</var>
\e$B$r
\e(B content-transfer-encoding
\e$B$H$7$F2r@O$7$?7k2L$rJV$9!#
\e(B
628 <defun name="mime-read-Content-Transfer-Encoding">
629 <opts>default-encoding
631 \e$B8=:_$N
\e(B buffer
\e$B$N
\e(B Content-Transfer-Encoding
\e$BMs$rFI$_<h$j!"2r@O$7$?7k2L$r
\e(B
634 Content-Transfer-Encoding
\e$BMs$,B8:_$7$J$$>l9g$O
\e(B
635 <var>default-encoding</var>
\e$B$rJV$9!#
\e(B
639 <h2> Region encoding/decoding
640 <node> Region encoder/decoder
642 <defun name="mime-encode-region">
643 <args> start end encoding
645 Encode region <var>start</var> to <var>end</var> of current buffer
646 using <var>encoding</var>.
649 <defun name="mime-decode-region">
650 <args> start end encoding
652 Decode region <var>start</var> to <var>end</var> of current buffer
653 using <var>encoding</var>.
656 <defvar name="mime-encoding-method-alist">
658 Alist of encoding vs. corresponding method to encode region.
660 Each element looks like <code>(STRING . FUNCTION)</code> or
661 <code>(STRING . nil)</code>. <var>string</var> is
662 content-transfer-encoding. <code>function</code> is region encoder
663 and <code>nil</code> means not to encode.
666 <defvar name="mime-decoding-method-alist">
668 Alist of encoding vs. corresponding method to decode region.
670 Each element looks like <code>(STRING . FUNCTION)</code> or
671 <code>(STRING . nil)</code>. <var>string</var> is
672 content-transfer-encoding. <code>function</code> is region decoder
673 and <code>nil</code> means not to decode.
677 <h2> String encoding/decoding
678 <node> String encoder/decoder
680 <defun name="mime-decode-string">
681 <args> string encoding
683 <var>string</var>
\e$B$r
\e(B <var>encoding</var>
\e$B$H$7$FI|9f$7$?7k2L$rJV$7$^$9!#
\e(B
686 <defvar name="mime-string-decoding-method-alist">
688 Alist of encoding vs. corresponding method to decode string.
690 Each element looks like <code>(STRING . FUNCTION)</code>.
691 STRING is content-transfer-encoding.
692 FUNCTION is string decoder.
696 <h2> File encoding/decoding
697 <node> File encoder/decoder
699 <defun name="mime-insert-encoded-file">
700 <args> filename encoding
702 Insert file <var>FILENAME</var> encoded by <var>ENCODING</var> format.
705 <defun name="mime-write-decoded-region">
706 <args> start end filename encoding
708 Decode and write current region encoded by <var>encoding</var> into
711 <var>start</var> and <var>end</var> are buffer positions.
714 <defvar name="mime-file-encoding-method-alist">
716 Alist of encoding vs. corresponding method to insert encoded file.
718 Each element looks like <code>(STRING . FUNCTION)</code>. STRING is
719 content-transfer-encoding. FUNCTION is function to insert encoded
723 <defvar name="mime-file-decoding-method-alist">
725 Alist of encoding vs. corresponding method to write decoded region to
728 Each element looks like <code>(STRING . FUNCTION)</code>. STRING is
729 content-transfer-encoding. FUNCTION is function to write decoded
734 <h1> Network representation of header
737 encoded-word
\e$B$O
\e(B header
\e$B$GHs
\e(B <dref>ASCII</dref>
\e$BJ8;z$rI=8=$9$k$?$a$N7A
\e(B
738 \e$B<0$G!"
\e(B<concept>RFC 2047</concept>
\e$B$GDj5A$5$l$F$$$^$9!#
\e(B
740 <rfc number="2047" type="Standards Track" author="K. Moore"
741 title="MIME (Multipurpose Internet Mail Extensions) Part
742 Three: Message Header Extensions for Non-ASCII Text"
743 date="November 1996" obsolete="1521,1522,1590">
745 \e$B$^$?!"9T57$N0-$$$3$H$@$H8@$($^$9$,!"
\e(Bencoded-word
\e$B$rMQ$$$:$KHs
\e(B
746 <dref>ASCII</dref>
\e$BJ8;z$r
\e(B header
\e$B$KF~$l$?5-;v$bB8:_$7$^$9!#
\e(B
748 FLIM
\e$B$O$3$l$i$rId9f2=!&I|9f2=$9$k5!G=$rDs6!$7$^$9!#
\e(B
751 <h2> Header encoding/decoding
752 <node> Header encoder/decoder
754 <defun name="eword-encode-header">
755 <opts> code-conversion separator
757 Decode MIME encoded-words in header fields.
759 If <var>code-conversion</var> is <code>nil</code>, it decodes only
760 encoded-words. If it is mime-charset, it decodes non-ASCII bit
761 patterns as the mime-charset. Otherwise it decodes non-ASCII bit
762 patterns as the default-mime-charset.
764 If <var>separator</var> is not nil, it is used as header separator.
767 <defun name="eword-encode-header">
768 <opts> code-conversion
770 Encode header fields to network representation, such as MIME
773 It refer variable <code>eword-field-encoding-method-alist</code>.
777 <h1> Various Customization
780 <define type="group" name="mime">
782 MIME
\e$B4XO"5!G=$K4X$9$k
\e(B group.
784 <code>mail</code>
\e$B$H
\e(B <code>news</code>
\e$B$KB0$9$k!#
\e(B
787 <defvar name="default-mime-charset">
789 \e$BE,@Z$J
\e(B <dref>MIME charset</dref>
\e$B$,8+$D$+$i$J$+$C$?>l9g$KMQ$$$i$l$k
\e(B
792 \e$BK\Mh$O
\e(B APEL
\e$B$NJQ?t$G$"$k!#
\e(B
795 <defvar name="mime-temp-directory">
797 MIME
\e$B5!G=$K4X$9$k<BAu$,0l;~E*$K;HMQ$9$k
\e(B file
\e$B$r:n@.$9$k
\e(B directory.
799 \e$B4D6-JQ?t
\e(B <code>MIME_TMP_DIR</code>, <code>TM_TMP_DIR</code>,
800 <code>TMPDIR</code>, <code>TMP</code>
\e$B$b$7$/$O
\e(B <code>TEMP</code>
\e$B$,@_Dj
\e(B
801 \e$B$5$l$F$$$?>l9g!"$=$l$r=i4|CM$H$7$FMQ$$$k!#2?$b@_Dj$5$l$F$$$J$$>l9g!"
\e(B
802 <code>"/tmp/"</code>
\e$B$rMQ$$$k!#
\e(B
815 <concept>7bit</concept> means any integer between 0 .. 127.
817 Any data represented by 7bit integers is called <concept>7bit
820 Textual string consisted of Control characters between 0 .. 31 and
821 127, and space represented by 32, and graphic characters between 33
822 .. 236 are called <concept>7bit (textual) string</concept>.
824 Conventional Internet <a node="MTA">MTA</a> can translate 7bit data,
825 so it is no need to translate by <a
826 node="Quoted-Printable">Quoted-Printable</a> or <a
827 node="Base64">Base64</a> for 7bit data.
829 However if there are too long lines, it can not translate by 7bit MTA
830 even if it is 7bit data. <dref>RFC 821</dref> and <dref>RFC
831 2045</dref> require lines in 7bit data must be less than 998 bytes.
832 So if a ``7bit data'' has a line more than 999 bytes, it is regarded
833 as <dref>binary</dref>. For example, Postscript file should be
834 encoded by Quoted-Printable.
840 <concept>8bit</concept> means any integer between 0 .. 255.
842 Any data represented by 8bit integers is called <concept>8bit
845 Textual string consisted of Control characters between 0 .. 31, 127,
846 and 128 .. 159, and space represented by 32, and graphic characters
847 between 33 .. 236 and 160 .. 255 are called <concept>8bit (textual)
850 For example, <dref>iso-8859-1</dref> or <dref>euc-kr</dref> are
851 coded-character-set represented by 8bit textual string.
853 Traditional Internet <a node="MTA">MTA</a> can translate only
854 <dref>7bit</dref> data, so if a 8bit data will be translated such MTA,
855 it must be encoded by <dref>Quoted-Printable</dref> or
858 However 8bit MTA are increasing today.
860 However if there are too long lines, it can not translate by 8bit MTA
861 even if it is 8bit data. <dref>RFC 2045</dref> require lines in 8bit
862 data must be less than 998 bytes. So if a ``8bit data'' has a line
863 more than 999 bytes, it is regarded as <dref>binary</dref>, so it must
864 be encoded by Base64 or Quoted-Printable.
870 <concept>ASCII</concept> is a 94-character set contains primary latin
871 characters (A-Z, a-z), numbers and some characters. It is a standard
872 of the United States of America. It is a variant of <a node="ISO
875 <standard abbrev="ASCII" title-en="Coded Character Set -- 7-Bit
876 American Standard Code for Information Interchange"
877 number="ANSI X3.4" year="1986">
883 <concept>Base64</concept> is a transfer encoding method of
884 <dref>MIME</dref> defined in <dref>RFC 2045</dref>.
886 The encoding process represents 24-bit groups of input bits as output
887 strings of 4 encoded characters. Encoded characters represent integer
888 0 .. 63 or <concept>pad</concept>. Base64 data must be 4 * n bytes,
889 so pad is used to adjust size.
891 These 65 characters are subset of all versions of ISO 646, including
892 US-ASCII, and all versions of EBCDIC. So it is safe even if it is
893 translated by non-Internet gateways.
899 Any byte stream is called <concept>binary</concept>.
901 It does not require structureof lines. It differs from from <a
902 node="8bit">8bit</a>.
904 In addition, if line structured data contain too long line (more than
905 998 bytes), it is regarded as binary.
908 <h3> Coded character set, Character code
909 <node> coded character set
911 A set of unambiguous rules that establishes a character set and the
912 one-to-one relationship between the characters of the set and their
919 <concept>media-type</concept> specifies the nature of the data in the
920 body of <dref>MIME</dref> <dref>entity</dref>. It consists of
921 <concept>type</concept> and <concept>subtype</concept>. It is defined
922 in <dref>RFC 2046</dref>.
924 Currently there are following standard primary-types:
927 <li><concept>text</concept>
929 <li><concept>image</concept>
931 <li><concept>audio</concept>
933 <li><concept>video</concept>
935 <li><concept>application</concept>
937 <li><a node="multipart"><concept>multipart</concept></a>
939 <li><concept>message</concept>
943 And there are various subtypes, for example, application/octet-stream,
944 audio/basic, image/jpeg, <dref>multipart/mixed</dref>,
945 <dref>text/plain</dref>, video/mpeg...
948 You can refer registered media types at <a
949 href="ftp://ftp.isi.edu/in-notes/iana/assignments/media-types">MEDIA
952 In addition, you can use private type or subtype using
953 <concept>x-token</concept>, which as the prefix `x-'. However you can
954 not use them in public.
956 <cf node="Content-Type field">
962 In this document, it means mail defined in <dref>RFC 822</dref> and
963 news message defined in <dref>RFC 1036</dref>.
969 MIME stands for <concept>Multipurpose Internet Mail
970 Extensions</concept>, it is an extension for <dref>RFC 822</dref>.
972 According to RFC 2045:
974 STD 11, RFC 822, defines a message representation protocol specifying
975 considerable detail about US-ASCII message headers, and leaves the
976 message content, or message body, as flat US-ASCII text. This set of
977 documents, collectively called the Multipurpose Internet Mail
978 Extensions, or MIME, redefines the format of messages to allow for
981 <li>textual message bodies in character sets other than US-ASCII,
983 <li>an extensible set of different formats for non-textual message
986 <li>multi-part message bodies, and
988 <li>textual header information in character sets other than US-ASCII.
992 It is defined in <dref>RFC 2045</dref>, <dref>RFC 2046</dref>, <a
993 node="encoded-word">RFC 2047</a>, <dref>RFC 2048</dref> and <dref>RFC
1000 <a node="coded character set">Coded character set</a> used in
1001 <dref>Content-Type field</dref> or charset parameter of <a
1002 node="encoded-word">encoded-word</a>.
1004 It is defined in <dref>RFC 2045</dref>.
1006 <dref>iso-2022-jp</dref> or <dref>euc-kr</dref> are kinds of it. (In
1007 this document, MIME charsets are written by small letters to
1008 distinguish <dref>graphic character set</dref>. For example, ISO
1009 8859-1 is a graphic character set, and iso-8859-1 is a MIME charset)
1015 <concept>Message Transfer Agent</concept>. It means mail transfer
1016 programs (ex. sendmail) and news servers.
1024 <concept>Message User Agent</concept>. It means mail readers and news
1030 <h3> Quoted-Printable
1031 <node> Quoted-Printable
1033 <concept>Quoted-Printable</concept> is a transfer encoding method of
1034 <dref>MIME</dref> defined in <dref>RFC 2045</dref>.
1036 If the data being encoded are mostly US-ASCII text, the encoded form
1037 of the data remains largely recognizable by humans.
1045 A RFC defines format of Internet mail message, mainly <concept>message
1050 news message is based on RFC 822, so <concept>Internet
1051 message</concept> may be more suitable than <concept>Internet
1055 <rfc number="822" type="STD 11" author="D. Crocker" title="Standard
1056 for the Format of ARPA Internet Text Messages"
1063 A RFC defines format of USENET message. It is a subset of <dref>RFC
1064 822</dref>. It is not Internet standard, but a lot of netnews
1065 excepting Usenet uses it.
1067 <rfc name="USENET" number="1036" author="M. Horton and R. Adams"
1068 title="Standard for Interchange of USENET Messages"
1069 date="December 1987" obsolete="850">
1075 <rfc number="2045" type="Standards Track" author="N. Freed and
1076 N. Borenstein" title="Multipurpose Internet Mail
1077 Extensions (MIME) Part One: Format of Internet Message
1078 Bodies" date="November 1996" obsolete="1521, 1522,
1085 <rfc number="2046" type="Standards Track" author="N. Freed and
1086 N. Borenstein" title="Multipurpose Internet Mail
1087 Extensions (MIME) Part Two: Media Types"
1088 date="November 1996" obsolete="1521, 1522, 1590">
1094 <rfc number="2048" type="Standards Track" author="N. Freed, J. Klensin
1095 and J. Postel" title="Multipurpose Internet Mail
1096 Extensions (MIME) Part Four: Registration Procedures"
1097 date="November 1996" obsolete="1521, 1522, 1590">
1103 <rfc number="2049" type="Standards Track" author="N. Freed and
1104 N. Borenstein" title="Multipurpose Internet Mail
1105 Extensions (MIME) Part Five: Conformance Criteria and
1106 Examples" date="November 1996" obsolete="1521, 1522,
1113 A textual data represented by only <dref>coded character set</dref>.
1114 It does not have information about font or typesetting.
1115 <cf node="text/plain">
1121 A <a node="MIME charset">MIME charset</a> for primary Latin script
1122 mainly written by English or other languages.
1124 It is a 7bit <dref>coded character set</dref> based on <dref>ISO
1125 2022</dref>, it contains only
1126 <dref>ASCII</dref> and <dref>code extension</dref> is not allowed.
1128 It is standard coded character set of Internet mail. If MIME charset
1129 is not specified, <concept>us-ascii</concept> is used as default.
1131 In addition, <concept>ASCII</concept> of <dref>RFC 822</dref> should
1132 be interpreted as us-ascii.
1135 <h2> How to report bugs
1138 If you write bug-reports and/or suggestions for improvement, please
1139 send them to the tm Mailing List:
1142 <li> Japanese <mail>bug-tm-ja@chamonix.jaist.ac.jp</mail>
1143 <li> English <mail>bug-tm-en@chamonix.jaist.ac.jp</mail>
1147 Notice that, we do not welcome bug reports about too old version.
1148 Bugs in old version might be fixed. So please try latest version at
1151 You should write <concept>good bug report</concept>. If you write
1152 only ``FLIM does not work'', we can not find such situations. At
1153 least, you should write name, type, variants and version of OS, emacs,
1154 APEL, FLIM, SEMI and MUA, and setting. In addition, if error occurs,
1155 to send backtrace is very important. <cf file="emacs" node="Bugs">
1157 Bug may not appear only your environment, but also in a lot of
1158 environment (otherwise it might not bug). Therefor if you send mail
1159 to author directly, we must write a lot of mails. So please send mail
1160 to address for tm bugs instead of author.
1163 Via the tm ML, you can report FLIM bugs, obtain the latest release of
1164 FLIM, and discuss future enhancements to FLIM. To join the tm ML,
1165 send empty e-mail to:
1168 <li> Japanese <mail>tm-ja-help@chamonix.jaist.ac.jp</mail>
1169 <li> English <mail>tm-en-help@chamonix.jaist.ac.jp</mail>
1173 <h2> CVS based development
1176 FLIM
\e$B$N
\e(B file
\e$B$O
\e(B CVS
\e$B$r;H$C$F4IM}$5$l$F$$$^$9!#$3$N$?$a!"0J2<$NJ}K!$G:G
\e(B
1177 \e$B?7$N
\e(B FLIM
\e$B$rF~<j$9$k$3$H$,$G$-$^$9!'
\e(B
1182 % cvs -d :pserver:anonymous@chamonix.jaist.ac.jp:/hare/cvs/root \
1185 CVS password: [CR] # NULL string
1189 % cvs -d :pserver:anonymous@chamonix.jaist.ac.jp:/hare/cvs/root \
1190 checkout [-r TAG] flim
1194 CVS
\e$B$rMQ$$$?3+H/$K;22C$7$?$$J}$O
\e(B
1197 <li> <mail>cvs@chamonix.jaist.ac.jp</mail>
1201 \e$B$^$G!"
\e(Baccount
\e$BL>$H
\e(B UNIX
\e$B$N
\e(B passwd
\e$B$HF1$87A<0$N
\e(B crypt
\e$B2=$5$l$?
\e(B password
1202 \e$B$r1h$($F8fO"Mm$/$@$5$$!#
\e(B
1205 <h2> History of FLIM
1208 FLIM
\e$B$N
\e(B code
\e$B$N:G8E$NItJ,$O
\e(B
\e$B1]JB
\e(B
\e$B;LCR
\e(B
\e$B;a$,=q$$$?
\e(B <file>mime.el</file>
1209 \e$B$K5/8;$7$^$9!#$3$N>.$5$J
\e(B program
\e$B$O
\e(B Nemacs
\e$B$GF0:n$9$k
\e(B iso-2022-jp
\e$B$N
\e(B
1210 B-encoding
\e$B@lMQ$N
\e(B encoded-word
\e$B$NI|9f2=%W%m%0%i%`$G$7$?!#
\e(B
1212 \e$B$=$N8e!"<i2,
\e(B
\e$BCNI'
\e(B
\e$B$O
\e(B <file>mime.el</file>
\e$B$r85$K
\e(B
1213 <file>tiny-mime.el</file>
\e$B$H$$$&%W%m%0%i%`$r=q$-$^$9!#$3$l$O!"
\e(BNemacs
1214 \e$B$H
\e(B Mule
\e$B$GF0:n$9$k
\e(B encoded-word
\e$B$NId9f2=!&I|9f2=%W%m%0%i%`$G$7$?!#
\e(B
1215 <file>tiny-mime.el</file>
\e$B$O
\e(B B-encoding
\e$B$@$1$G$J$/
\e(B Q-encoding
\e$B$b
\e(B
1216 support
\e$B$7!"$^$?!"
\e(BMULE
\e$B$G07$&$3$H$,$G$-$k$5$^$6$^$J
\e(B <dref>MIME
1217 charset</dref>
\e$B$rF1;~$K;H$&$3$H$,$G$-$^$7$?!#$3$N;~!"
\e(BNemacs
\e$B$H
\e(B Mule
\e$B$N
\e(B
1218 \e$BAPJ}$r
\e(B support
\e$B$9$k$?$a$KMQ$$$i$l$?%F%/%K%C%/$O8e$K
\e(B emu package
\e$B$K$^$H
\e(B
1219 \e$B$a$i$l$^$9!#
\e(B
1221 \e$B$3$N:"!"<i2,
\e(B
\e$BCNI'
\e(B
\e$B$O
\e(B <file>tiny-mime.el</file>
\e$B$r$5$^$6$^$J
\e(B MUA
\e$B$G;H$&
\e(B
1222 \e$B$?$a$N@_Dj=8$bG[I[$7$F$$$^$7$?$,!"$=$l$i$O8e$K
\e(B
1223 <file>tiny-mime.el</file>
\e$B$H$H$b$K#1$D$N
\e(B package
\e$B$K$^$H$a$i$l!"
\e(Btm
\e$B$H$$
\e(B
1224 \e$B$&L>A0$GG[I[$5$l$^$9!#
\e(B
1226 \e$B<i2,
\e(B
\e$BCNI'
\e(B
\e$B$O$d$,$F!"
\e(BMIME message
\e$B$r1\Mw$9$k$?$a$N%W%m%0%i%`$G$"$k
\e(B
1227 <file>tm-body.el</file>
\e$B$r=q$-$^$9!#$3$l$O!"$9$0$K
\e(B
1228 <file>tm-view.el</file>
\e$B$H$$$&L>A0$KJQ$o$j$^$7$?$,!"$d$,$F!"$3$l$,
\e(B
1229 <file>tiny-mime.el</file>
\e$B$KBe$o$C$F!"
\e(Btm
\e$B$NCf3K$H$J$j$^$9!#
\e(B
1231 <file>tm-view.el</file>
\e$B$OEvA3!"
\e(BContent-Transfer-Encoding
\e$B$r07$&I,MW$,
\e(B
1232 \e$B$"$j$^$9!#$3$NL\E*$N$?$a$K!"
\e(BMEL
\e$B$,@0Hw$5$l$O$8$a$^$7$?!#
\e(BBase64
\e$B$K4X$7
\e(B
1233 \e$B$F$O
\e(B <file>tiny-mime.el</file>
\e$B$N
\e(B code
\e$B$,0\$5$l!"$^$?!"?7$?$K
\e(B
1234 Quoted-Printable
\e$B$N
\e(B code
\e$B$,DI2C$5$l$^$7$?!#$3$l$i$,
\e(B
1235 <file>mel-b.el</file>
\e$B$H
\e(B <file>mel-q.el</file>
\e$B$K$J$j$^$7$?!#
\e(B
1237 \e$B$^$?!"8e$K!"<i2,
\e(B
\e$BCNI'
\e(B
\e$B$K$h$C$F
\e(B uuencode
\e$BMQ$N
\e(B <file>mel-u.el</file>
\e$B$,
\e(B
1238 \e$BDI2C$5$l!"$=$N8e$K!">.NS
\e(B
\e$B=$J?
\e(B
\e$B;a$K$h$C$F
\e(B x-gzip64
\e$BMQ$N
\e(B
1239 <file>mel-g.el</file>
\e$B$,DI2C$5$l$^$7$?!#
\e(B
1241 tm
\e$B$G$O8e$K!"<i2,
\e(B
\e$BCNI'
\e(B
\e$B$K$h$C$F
\e(B <file>tiny-mime.el</file>
\e$B$N:F<BAu$,9T
\e(B
1242 \e$B$o$l!"$3$N2aDx$G!"
\e(BSTD 11
\e$B$N
\e(B parser
\e$B$,=q$+$l$^$7$?!#$3$l$O!"8=:_$N
\e(B
1243 <file>std11.el</file>
\e$B$KEv$?$j$^$9!#$^$?!"$3$N2aDx$G
\e(B
1244 <file>tiny-mime.el</file>
\e$B$OI|9f2=$r9T$&
\e(B <file>tm-ew-d.el</file>
\e$B$HId
\e(B
1245 \e$B9f2=$r9T$&
\e(B <file>tm-ew-e.el</file>
\e$B$KJ,$1$i$l$^$7$?!#$3$NN><T$,8=:_$N
\e(B
1246 <file>eword-decode.el</file>
\e$B$H
\e(B <file>eword-encode.el</file>
\e$B$N@hAD$K
\e(B
1247 \e$BEv$?$j$^$9!#
\e(B
1249 \e$B8e$K!"<i2,
\e(B
\e$BCNI'
\e(B
\e$B$i$K$h$C$F
\e(B tm
\e$B$NA4LL=q$-49$(:n6H$,9T$o$l!"$3$N2aDx$G!"
\e(B
1250 tm
\e$B$O
\e(B APEL, MEL, SEMI, EMH, RMAIL-MIME, Gnus-MIME
\e$B$J$I$KJ,$1$i$l$^$7$?!#
\e(B
1251 \e$B$3$N$&$A$N
\e(B MEL
\e$B$,
\e(B FLIM
\e$B$ND>@\$N@hAD$KEv$?$j$^$9!#
\e(B
1253 \e$B8e$K!"
\e(BAPEL
\e$B$+$i
\e(B <file>std11.el</file>
\e$B$,0\$5$l!"$^$?!"
\e(B
1254 <file>mailcap.el</file>, <file>eword-decode.el</file>
\e$B$*$h$S
\e(B
1255 <file>eword-encode.el</file>
\e$B$,
\e(B SEMI
\e$B$+$i0\$5$l!"
\e(Bpackage
\e$B$NL>A0$,
\e(B FLIM
1256 \e$B$H$J$j$^$9!#
\e(B
1258 \e$B$3$ND>A0$+$iEDCf
\e(B
\e$BE/
\e(B
\e$B;a$,$h$j
\e(B RFC
\e$B$KCi<B$J<BAu$r=q$-;O$a!"$3$l$O!"8=:_!"
\e(B
1259 FLIM
\e$B$N;^$G$"$k
\e(B ``FLIM-FLAM''
\e$B$H$J$C$F$$$^$9!#
\e(B
1263 <node> Concept Index
1269 <node> Function Index
1275 <node> Variable Index