1 \input texinfo @c -*-texinfo-*-
3 @setfilename emacs-mime
4 @settitle Emacs MIME Manual
9 @c * Emacs MIME: (emacs-mime). The MIME de/composition library.
14 @setchapternewpage odd
18 This file documents the Emacs MIME interface functionality.
20 Copyright (C) 1996 Free Software Foundation, Inc.
22 Permission is granted to make and distribute verbatim copies of
23 this manual provided the copyright notice and this permission notice
24 are preserved on all copies.
27 Permission is granted to process this file through Tex and print the
28 results, provided the printed document carries copying permission
29 notice identical to this one except for the removal of this paragraph
30 (this paragraph not being relevant to the printed manual).
33 Permission is granted to copy and distribute modified versions of this
34 manual under the conditions for verbatim copying, provided also that the
35 entire resulting derived work is distributed under the terms of a
36 permission notice identical to this one.
38 Permission is granted to copy and distribute translations of this manual
39 into another language, under the above conditions for modified versions.
45 @title Emacs MIME Manual
47 @author by Lars Magne Ingebrigtsen
50 @vskip 0pt plus 1filll
51 Copyright @copyright{} 1998 Free Software Foundation, Inc.
53 Permission is granted to make and distribute verbatim copies of
54 this manual provided the copyright notice and this permission notice
55 are preserved on all copies.
57 Permission is granted to copy and distribute modified versions of this
58 manual under the conditions for verbatim copying, provided that the
59 entire resulting derived work is distributed under the terms of a
60 permission notice identical to this one.
62 Permission is granted to copy and distribute translations of this manual
63 into another language, under the above conditions for modified versions.
73 This manual documents the libraries used to compose and display
76 This is not a manual meant for users; it's a manual directed at people
77 who want to write functions and commands that manipulate @sc{mime}
80 @sc{mime} is short for @dfn{Multipurpose Internet Mail Extensions}.
81 This standard is documented in a number of RFCs; mainly RFC2045 (Format
82 of Internet Message Bodies), RFC2046 (Media Types), RFC2047 (Message
83 Header Extensions for Non-ASCII Text), RFC2048 (Registration
84 Procedures), RFC2049 (Conformance Criteria and Examples). It is highly
85 recommended that anyone who intends writing @sc{mime}-compliant software
86 read at least RFC2045 and RFC2047.
89 * Interface Functions:: An abstraction over the basic functions.
90 * Basic Functions:: Utility and basic parsing functions.
91 * Decoding and Viewing:: A framework for decoding and viewing.
92 * Composing:: MML; a language for describing MIME parts.
93 * Standards:: A summary of RFCs and working documents used.
94 * Index:: Function and variable index.
98 @node Interface Functions
99 @chapter Interface Functions
100 @cindex interface functions
103 The @code{mail-parse} library is an abstraction over the actual
104 low-level libraries that are described in the next chapter.
106 Standards change, and so programs have to change to fit in the new
107 mold. For instance, RFC2045 describes a syntax for the
108 @code{Content-Type} header that only allows ASCII characters in the
109 parameter list. RFC2231 expands on RFC2045 syntax to provide a scheme
110 for continuation headers and non-ASCII characters.
112 The traditional way to deal with this is just to update the library
113 functions to parse the new syntax. However, this is sometimes the wrong
114 thing to do. In some instances it may be vital to be able to understand
115 both the old syntax as well as the new syntax, and if there is only one
116 library, one must choose between the old version of the library and the
117 new version of the library.
119 The Emacs MIME library takes a different tack. It defines a series of
120 low-level libraries (@file{rfc2047.el}, @file{rfc2231.el} and so on)
121 that parses strictly according to the corresponding standard. However,
122 normal programs would not use the functions provided by these libraries
123 directly, but instead use the functions provided by the
124 @code{mail-parse} library. The functions in this library are just
125 aliases to the corresponding functions in the latest low-level
126 libraries. Using this scheme, programs get a consistent interface they
127 can use, and library developers are free to create write code that
128 handles new standards.
130 The following functions are defined by this library:
133 @item mail-header-parse-content-type
134 @findex mail-header-parse-content-type
135 Parse a @code{Content-Type} header and return a list on the following
140 (attribute1 . value1)
141 (attribute2 . value2)
148 (mail-header-parse-content-type
149 "image/gif; name=\"b980912.gif\"")
150 @result{} ("image/gif" (name . "b980912.gif"))
153 @item mail-header-parse-content-disposition
154 @findex mail-header-parse-content-disposition
155 Parse a @code{Content-Disposition} header and return a list on the same
156 format as the function above.
158 @item mail-content-type-get
159 @findex mail-content-type-get
160 Takes two parameters---a list on the format above, and an attribute.
161 Returns the value of the attribute.
164 (mail-content-type-get
165 '("image/gif" (name . "b980912.gif")) 'name)
166 @result{} "b980912.gif"
169 @item mail-header-remove-comments
170 @findex mail-header-remove-comments
171 Return a comment-free version of a header.
174 (mail-header-remove-comments
175 "Gnus/5.070027 (Pterodactyl Gnus v0.27) (Finnish Landrace)")
176 @result{} "Gnus/5.070027 "
179 @item mail-header-remove-whitespace
180 @findex mail-header-remove-whitespace
181 Remove linear white space from a header. Space inside quoted strings
182 and comments is preserved.
185 (mail-header-remove-whitespace
186 "image/gif; name=\"Name with spaces\"")
187 @result{} "image/gif;name=\"Name with spaces\""
190 @item mail-header-get-comment
191 @findex mail-header-get-comment
192 Return the last comment in a header.
195 (mail-header-get-comment
196 "Gnus/5.070027 (Pterodactyl Gnus v0.27) (Finnish Landrace)")
197 @result{} "Finnish Landrace"
200 @item mail-header-parse-address
201 @findex mail-header-parse-address
202 Parse an address and return a list containing the mailbox and the
206 (mail-header-parse-address
207 "Hrvoje Niksic <hniksic@@srce.hr>")
208 @result{} ("hniksic@@srce.hr" . "Hrvoje Niksic")
211 @item mail-header-parse-addresses
212 @findex mail-header-parse-addresses
213 Parse a string with list of addresses and return a list of elements like
214 the one described above.
217 (mail-header-parse-addresses
218 "Hrvoje Niksic <hniksic@@srce.hr>, Steinar Bang <sb@@metis.no>")
219 @result{} (("hniksic@@srce.hr" . "Hrvoje Niksic")
220 ("sb@@metis.no" . "Steinar Bang"))
223 @item mail-header-parse-date
224 @findex mail-header-parse-date
225 Parse a date string and return an Emacs time structure.
227 @item mail-narrow-to-head
228 @findex mail-narrow-to-head
229 Narrow the buffer to the header section of the buffer. Point is placed
230 at the beginning of the narrowed buffer.
232 @item mail-header-narrow-to-field
233 @findex mail-header-narrow-to-field
234 Narrow the buffer to the header under point.
236 @item mail-encode-encoded-word-region
237 @findex mail-encode-encoded-word-region
238 Encode the non-ASCII words in the region. For instance,
239 @samp{Naïve} is encoded as @samp{=?iso-8859-1?q?Na=EFve?=}.
241 @item mail-encode-encoded-word-buffer
242 @findex mail-encode-encoded-word-buffer
243 Encode the non-ASCII words in the current buffer. This function is
244 meant to be called narrowed to the headers of a message.
246 @item mail-encode-encoded-word-string
247 @findex mail-encode-encoded-word-string
248 Encode the words that need encoding in a string, and return the result.
251 (mail-encode-encoded-word-string
252 "This is naïve, baby")
253 @result{} "This is =?iso-8859-1?q?na=EFve,?= baby"
256 @item mail-decode-encoded-word-region
257 @findex mail-decode-encoded-word-region
258 Decode the encoded words in the region.
260 @item mail-decode-encoded-word-string
261 @findex mail-decode-encoded-word-string
262 Decode the encoded words in the string and return the result.
265 (mail-decode-encoded-word-string
266 "This is =?iso-8859-1?q?na=EFve,?= baby")
267 @result{} "This is naïve, baby"
272 Currently, @code{mail-parse} is an abstraction over @code{ietf-drums},
273 @code{rfc2047} and @code{rfc2231}. These are documented in the
278 @node Basic Functions
279 @chapter Basic Functions
281 This chapter describes the basic, ground-level functions for parsing and
282 handling. Covered here is parsing @code{From} lines, removing comments
283 from header lines, decoding encoded words, parsing date headers and so
284 on. High-level functionality is dealt with in the next chapter
285 (@pxref{Decoding and Viewing}).
288 * rfc2231:: Parsing @code{Content-Type} headers.
289 * ietf-drums:: Handling mail headers defined by RFC822bis.
290 * rfc2047:: En/decoding encoded words in headers.
291 * time-date:: Functions for parsing dates and manipulating time.
292 * qp:: Quoted-Printable en/decoding.
293 * base64:: Base64 en/decoding.
294 * binhex:: Binhex decoding.
295 * uudecode:: Uuencode decoding.
296 * rfc1843:: Decoding HZ-encoded text.
297 * mailcap:: How parts are displayed is specified by the @file{.mailcap} file
304 RFC2231 defines a syntax for the @code{Content-Type} and
305 @code{Content-Disposition} headers. Its snappy name is @dfn{MIME
306 Parameter Value and Encoded Word Extensions: Character Sets, Languages,
309 In short, these headers look something like this:
312 Content-Type: application/x-stuff;
313 title*0*=us-ascii'en'This%20is%20even%20more%20;
314 title*1*=%2A%2A%2Afun%2A%2A%2A%20;
318 They usually aren't this bad, though.
320 The following functions are defined by this library:
323 @item rfc2231-parse-string
324 @findex rfc2231-parse-string
325 Parse a @code{Content-Type} header and return a list describing its
329 (rfc2231-parse-string
330 "application/x-stuff;
331 title*0*=us-ascii'en'This%20is%20even%20more%20;
332 title*1*=%2A%2A%2Afun%2A%2A%2A%20;
333 title*2=\"isn't it!\"")
334 @result{} ("application/x-stuff"
335 (title . "This is even more ***fun*** isn't it!"))
338 @item rfc2231-get-value
339 @findex rfc2231-get-value
340 Takes one of the lists on the format above and return
341 the value of the specified attribute.
349 @dfn{drums} is an IETF working group that is working on the replacement
352 The functions provided by this library include:
355 @item ietf-drums-remove-comments
356 @findex ietf-drums-remove-comments
357 Remove the comments from the argument and return the results.
359 @item ietf-drums-remove-whitespace
360 @findex ietf-drums-remove-whitespace
361 Remove linear white space from the string and return the results.
362 Spaces inside quoted strings and comments are left untouched.
364 @item ietf-drums-get-comment
365 @findex ietf-drums-get-comment
366 Return the last most comment from the string.
368 @item ietf-drums-parse-address
369 @findex ietf-drums-parse-address
370 Parse an address string and return a list that contains the mailbox and
373 @item ietf-drums-parse-addresses
374 @findex ietf-drums-parse-addresses
375 Parse a string that contains any number of comma-separated addresses and
376 return a list that contains mailbox/plain text pairs.
378 @item ietf-drums-parse-date
379 @findex ietf-drums-parse-date
380 Parse a date string and return an Emacs time structure.
382 @item ietf-drums-narrow-to-header
383 @findex ietf-drums-narrow-to-header
384 Narrow the buffer to the header section of the current buffer.
392 RFC2047 (Message Header Extensions for Non-ASCII Text) specifies how
393 non-ASCII text in headers are to be encoded. This is actually rather
394 complicated, so a number of variables are necessary to tweak what this
397 The following variables are tweakable:
400 @item rfc2047-default-charset
401 @vindex rfc2047-default-charset
402 Characters in this charset should not be decoded by this library.
403 This defaults to @code{iso-8859-1}.
405 @item rfc2047-header-encoding-list
406 @vindex rfc2047-header-encoding-list
407 This is an alist of header / encoding-type pairs. Its main purpose is
408 to prevent encoding of certain headers.
410 The keys can either be header regexps, or @code{t}.
412 The values can be either @code{nil}, in which case the header(s) in
413 question won't be encoded, or @code{mime}, which means that they will be
416 @item rfc2047-charset-encoding-alist
417 @vindex rfc2047-charset-encoding-alist
418 RFC2047 specifies two forms of encoding---@code{Q} (a
419 Quoted-Printable-like encoding) and @code{B} (base64). This alist
420 specifies which charset should use which encoding.
422 @item rfc2047-encoding-function-alist
423 @vindex rfc2047-encoding-function-alist
424 This is an alist of encoding / function pairs. The encodings are
425 @code{Q}, @code{B} and @code{nil}.
427 @item rfc2047-q-encoding-alist
428 @vindex rfc2047-q-encoding-alist
429 The @code{Q} encoding isn't quite the same for all headers. Some
430 headers allow a narrower range of characters, and that is what this
431 variable is for. It's an alist of header regexps / allowable character
434 @item rfc2047-encoded-word-regexp
435 @vindex rfc2047-encoded-word-regexp
436 When decoding words, this library looks for matches to this regexp.
440 Those were the variables, and these are this functions:
443 @item rfc2047-narrow-to-field
444 @findex rfc2047-narrow-to-field
445 Narrow the buffer to the header on the current line.
447 @item rfc2047-encode-message-header
448 @findex rfc2047-encode-message-header
449 Should be called narrowed to the header of a message. Encodes according
450 to @code{rfc2047-header-encoding-alist}.
452 @item rfc2047-encode-region
453 @findex rfc2047-encode-region
454 Encodes all encodable words in the region specified.
456 @item rfc2047-encode-string
457 @findex rfc2047-encode-string
458 Encode a string and return the results.
460 @item rfc2047-decode-region
461 @findex rfc2047-decode-region
462 Decode the encoded words in the region.
464 @item rfc2047-decode-string
465 @findex rfc2047-decode-string
466 Decode a string and return the results.
474 While not really a part of the @sc{mime} library, it is convenient to
475 document this library here. It deals with parsing @code{Date} headers
476 and manipulating time. (Not by using tesseracts, though, I'm sorry to
479 These functions convert between five formats: A date string, an Emacs
480 time structure, a decoded time list, a second number, and a day number.
482 The functions have quite self-explanatory names, so the following just
483 gives an overview of which functions are available.
486 (parse-time-string "Sat Sep 12 12:21:54 1998 +0200")
487 @result{} (54 21 12 12 9 1998 6 nil 7200)
489 (date-to-time "Sat Sep 12 12:21:54 1998 +0200")
490 @result{} (13818 19266)
492 (time-to-seconds '(13818 19266))
493 @result{} 905595714.0
495 (seconds-to-time 905595714.0)
496 @result{} (13818 19266 0)
498 (time-to-day '(13818 19266))
501 (days-to-time 729644)
502 @result{} (961933 65536)
504 (time-since '(13818 19266))
507 (time-less-p '(13818 19266) '(13818 19145))
510 (subtract-time '(13818 19266) '(13818 19145))
513 (days-between "Sat Sep 12 12:21:54 1998 +0200"
514 "Sat Sep 07 12:21:54 1998 +0200")
517 (date-leap-year-p 2000)
520 (time-to-day-in-year '(13818 19266))
525 And finally, we have @code{safe-date-to-time}, which does the same as
526 @code{date-to-time}, but returns a zero time if the date is
527 syntactically malformed.
534 This library deals with decoding and encoding Quoted-Printable text.
536 Very briefly explained, qp encoding means translating all 8-bit
537 characters (and lots of control characters) into things that look like
538 @samp{=EF}; that is, an equal sign followed by the byte encoded as a hex
541 The following functions are defined by the library:
544 @item quoted-printable-decode-region
545 @findex quoted-printable-decode-region
546 QP-decode all the encoded text in the specified region.
548 @item quoted-printable-decode-string
549 @findex quoted-printable-decode-string
550 Decode the QP-encoded text in a string and return the results.
552 @item quoted-printable-encode-region
553 @findex quoted-printable-encode-region
554 QP-encode all the encodable characters in the specified region. The third
555 optional parameter @var{fold} specifies whether to fold long lines.
556 (Long here means 72.)
558 @item quoted-printable-encode-string
559 @findex quoted-printable-encode-string
560 QP-encode all the encodable characters in a string and return the
570 Base64 is an encoding that encodes three bytes into four characters,
571 thereby increasing the size by about 33%. The alphabet used for
572 encoding is very resistant to mangling during transit.
574 The following functions are defined by this library:
577 @item base64-encode-region
578 @findex base64-encode-region
579 base64 encode the selected region. Return the length of the encoded
580 text. Optional third argument @var{no-line-break} means do not break
581 long lines into shorter lines.
583 @item base64-encode-string
584 @findex base64-encode-string
585 base64 encode a string and return the result.
587 @item base64-decode-region
588 @findex base64-decode-region
589 base64 decode the selected region. Return the length of the decoded
590 text. If the region can't be decoded, return @code{nil} and don't
593 @item base64-decode-string
594 @findex base64-decode-string
595 base64 decode a string and return the result. If the string can't be
596 decoded, @code{nil} is returned.
607 @code{binhex} is an encoding that originated in Macintosh environments.
608 The following function is supplied to deal with these:
611 @item binhex-decode-region
612 @findex binhex-decode-region
613 Decode the encoded text in the region. If given a third parameter, only
614 decode the @code{binhex} header and return the filename.
624 @code{uuencode} is probably still the most popular encoding of binaries
625 used on Usenet, although @code{base64} rules the mail world.
627 The following function is supplied by this package:
630 @item uudecode-decode-region
631 @findex uudecode-decode-region
632 Decode the text in the region.
642 RFC1843 deals with mixing Chinese and ASCII characters in messages. In
643 essence, RFC1843 switches between ASCII and Chinese by doing this:
646 This sentence is in ASCII.
647 The next sentence is in GB.~@{<:Ky2;S@{#,NpJ)l6HK!#~@}Bye.
650 Simple enough, and widely used in China.
652 The following functions are available to handle this encoding:
655 @item rfc1843-decode-region
656 Decode HZ-encoded text in the region.
658 @item rfc1843-decode-string
659 Decode a HZ-encoded string and return the result.
667 The @file{~/.mailcap} file is parsed by most @sc{mime}-aware message
668 handlers and describes how elements are supposed to be displayed.
669 Here's an example file:
673 audio/wav; wavplayer %s
676 This says that all image files should be displayed with @samp{xv}, and
677 that realaudio files should be played by @samp{rvplayer}.
679 The @code{mailcap} library parses this file, and provides functions for
683 @item mailcap-mime-data
684 @vindex mailcap-mime-data
685 This variable is an alist of alists containing backup viewing rules.
692 @item mailcap-parse-mailcaps
693 @findex mailcap-parse-mailcaps
694 Parse the @code{~/.mailcap} file.
696 @item mailcap-mime-info
697 Takes a @sc{mime} type as its argument and returns the matching viewer.
704 @node Decoding and Viewing
705 @chapter Decoding and Viewing
707 This chapter deals with decoding and viewing @sc{mime} messages on a
710 The main idea is to first analyze a @sc{mime} article, and then allow
711 other programs to do things based on the list of @dfn{handles} that are
712 returned as a result of this analysis.
715 * Dissection:: Analyzing a @sc{mime} message.
716 * Handles:: Handle manipulations.
717 * Display:: Displaying handles.
724 The @code{mm-dissect-buffer} is the function responsible for dissecting
725 a @sc{mime} article. If given a multipart message, it will recursively
726 descend the message, following the structure, and return a tree of
727 @sc{mime} handles that describes the structure of the message.
733 A @sc{mime} handle is a list that fully describes a @sc{mime}
736 The following macros can be used to access elements in a handle:
739 @item mm-handle-buffer
740 @findex mm-handle-buffer
741 Return the buffer that holds the contents of the undecoded @sc{mime}
745 @findex mm-handle-type
746 Return the parsed @code{Content-Type} of the part.
748 @item mm-handle-encoding
749 @findex mm-handle-encoding
750 Return the @code{Content-Transfer-Encoding} of the part.
752 @item mm-handle-undisplayer
753 @findex mm-handle-undisplayer
754 Return the object that can be used to remove the displayed part (if it
757 @item mm-handle-set-undisplayer
758 @findex mm-handle-set-undisplayer
759 Set the undisplayer object.
761 @item mm-handle-disposition
762 @findex mm-handle-disposition
763 Return the parsed @code{Content-Disposition} of the part.
765 @item mm-handle-disposition
766 @findex mm-handle-disposition
767 Return the description of the part.
769 @item mm-get-content-id
770 Returns the handle(s) referred to by @code{Content-ID}.
778 Functions for displaying, removing and saving.
781 @item mm-display-part
782 @findex mm-display-part
786 @findex mm-remove-part
787 Remove the part (if it has been displayed).
790 @findex mm-inlinable-p
791 Say whether a @sc{mime} type can be displayed inline.
793 @item mm-automatic-display-p
794 @findex mm-automatic-display-p
795 Say whether a @sc{mime} type should be displayed automatically.
797 @item mm-destroy-part
798 @findex mm-destroy-part
799 Free all resources occupied by a part.
803 Offer to save the part in a file.
807 Offer to pipe the part to some process.
809 @item mm-interactively-view-part
810 @findex mm-interactively-view-part
811 Prompt for a mailcap method to use to view the part.
819 @cindex MIME Composing
821 @cindex MIME Meta Language
823 Creating a @sc{mime} message is boring and non-trivial. Therefore, a
824 library called @code{mml} has been defined that parses a language called
825 MML (@sc{mime} Meta Language) and generates @sc{mime} messages.
827 @findex mml-generate-mime
828 The main interface function is @code{mml-generate-mime}. It will
829 examine the contents of the current (narrowed-to) buffer and return a
830 string containing the @sc{mime} message.
833 * Simple MML Example:: An example MML document.
834 * MML Definition:: All valid MML elements.
835 * Advanced MML Example:: Another example MML document.
839 @node Simple MML Example
840 @section Simple MML Example
842 Here's a simple @samp{multipart/alternative}:
845 <#multipart type=alternative>
846 This is a plain text part.
847 <#part type=text/enriched>
848 <center>This is a centered enriched part</center>
852 After running this through @code{mml-generate-mime}, we get this:
855 Content-Type: multipart/alternative; boundary="=-=-="
861 This is a plain text part.
864 Content-Type: text/enriched
867 <center>This is a centered enriched part</center>
874 @section MML Definition
876 The MML language is very simple. It looks a bit like an SGML
877 application, but it's not.
879 The main concept of MML is the @dfn{part}. Each part can be of a
880 different type or use a different charset. The way to delineate a part
881 is with a @samp{<#part ...>} tag. Multipart parts can be introduced
882 with the @samp{<#multipart ...>} tag. Parts are ended by the
883 @samp{<#/part>} or @samp{<#/multipart>} tags. Parts started with the
884 @samp{<#part ...>} tags are also closed by the next open tag.
886 There's also the @samp{<#external ...>} tag. These introduce
887 @samp{external/message-body} parts.
889 Each tag can contain zero or more parameters on the form
890 @samp{parameter=value}. The values may be enclosed in quotation marks,
891 but that's not necessary unless the value contains white space. So
892 @samp{filename=/home/user/#hello$^yes} is perfectly valid.
894 The following parameters have meaning in MML; parameters that have no
895 meaning are ignored. The MML parameter names are the same as the
896 @sc{mime} parameter names; the things in the parentheses say which
897 header it will be used in.
901 The @sc{mime} type of the part (@code{Content-Type}).
904 Use the contents of the file in the body of the part
905 (@code{Content-Disposition}).
908 The contents of the body of the part are to be encoded in the character
909 set speficied (@code{Content-Type}).
912 Might be used to suggest a file name if the part is to be saved
913 to a file (@code{Content-Type}).
916 Valid values are @samp{inline} and @samp{attachment}
917 (@code{Content-Disposition}).
920 Valid values are @samp{7bit}, @samp{8bit}, @samp{quoted-printable} and
921 @samp{base64} (@code{Content-Transfer-Encoding}).
924 A description of the part (@code{Content-Description}).
927 RFC822 date when the part was created (@code{Content-Disposition}).
929 @item modification-date
930 RFC822 date when the part was modified (@code{Content-Disposition}).
933 RFC822 date when the part was read (@code{Content-Disposition}).
936 The size (in octets) of the part (@code{Content-Disposition}).
940 Parameters for @samp{application/octet-stream}:
944 Type of the part; informal---meant for human readers
945 (@code{Content-Type}).
948 Parameters for @samp{message/external-body}:
952 A word indicating the supported access mechanism by which the file may
953 be obtained. Values include @samp{ftp}, @samp{anon-ftp}, @samp{tftp},
954 @samp{localfile}, and @samp{mailserver}. (@code{Content-Type}.)
957 The RFC822 date after which the file may no longer be fetched.
958 (@code{Content-Type}.)
961 The size (in octets) of the file. (@code{Content-Type}.)
964 Valid values are @samp{read} and @samp{read-write}
965 (@code{Content-Type}).
970 @node Advanced MML Example
971 @section Advanced MML Example
973 Here's a complex multipart message. It's a @samp{multipart/mixed} that
974 contains many parts, one of which is a @samp{multipart/alternative}.
977 <#multipart type=mixed>
978 <#part type=image/jpeg filename=~/rms.jpg disposition=inline>
979 <#multipart type=alternative>
980 This is a plain text part.
981 <#part type=text/enriched name=enriched.txt>
982 <center>This is a centered enriched part</center>
984 This is a new plain text part.
985 <#part disposition=attachment>
986 This plain text part is an attachment.
990 And this is the resulting @sc{mime} message:
993 Content-Type: multipart/mixed; boundary="=-=-="
1001 Content-Type: image/jpeg;
1002 filename="~/rms.jpg"
1003 Content-Disposition: inline;
1004 filename="~/rms.jpg"
1005 Content-Transfer-Encoding: base64
1007 /9j/4AAQSkZJRgABAQAAAQABAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRof
1008 Hh0aHBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/wAALCAAwADABAREA/8QAHwAA
1009 AQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQR
1010 BRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q0RF
1011 RkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ip
1012 qrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/9oACAEB
1013 AAA/AO/rifFHjldNuGsrDa0qcSSHkA+gHrXKw+LtWLrMb+RgTyhbr+HSug07xNqV9fQtZrNI
1014 AyiaE/NuBPOOOP0rvRNE880KOC8TbXXGCv1FPqjrF4LDR7u5L7SkTFT/ALWOP1xXgTuXfc7E
1015 sx6nua6rwp4IvvEM8chCxWxOdzn7wz6V9AaB4S07w9p5itow0rDLSY5Pt9K43xO66P4xs71m
1016 2QXiGCbA4yOVJ9+1aYORkdK434lyNH4ahCnG66VT9Nj15JFbPdX0MS43M4VQf5/yr2vSpLnw
1017 5ZW8dlCZ8KFXjOPX0/mK6rSPEGt3Angu44fNEReHYNvIH3TzXDeKNO8RX+kSX2ouZkicTIOc
1018 L+g7E810ulFjpVtv3bwgB3HJyK5L4quY/C9sVxk3ij/xx6850u7t1mtp/wDlpEw3An3Jr3Dw
1019 34gsbWza4nBlhC5LDsaW6+IFgupQyCF3iHH7gA7c9R9ay7zx6t7aX9jHC4smhfBkGCvHGfrm
1020 tLQ7hbnRrV1GPkAP1x1/Hr+Ncr8Vzjwrbf8AX6v/AKA9eQRyYlQk8Yx9K6XTNbkgia2ciSIn
1021 7p5Ga9Atte0LTLKO6it4i7dVRFJDcZ4PvXN+JvEMF9bILVGXJLSZ4zkjivRPDaeX4b08HOTC
1022 pOffmua+KkbS+GLVUGT9tT/0B68eeIpIFYjB70+OOVXyoOM9+M1eaWeCLzHPyHGO/NVWvJJm
1023 jQ8KGH1NfQWhXSXmh2c8eArRLwO3HSv/2Q==
1026 Content-Type: multipart/alternative; boundary="==-=-="
1032 This is a plain text part.
1035 Content-Type: text/enriched;
1039 <center>This is a centered enriched part</center>
1045 This is a new plain text part.
1048 Content-Disposition: attachment
1051 This plain text part is an attachment.
1061 The Emacs @sc{mime} library implements handling of various elements
1062 according to a (somewhat) large number of RFCs, drafts and standards
1063 documents. This chapter lists the relevant ones. They can all be
1064 fetched from @samp{http://www.stud.ifi.uio.no/~larsi/notes/}.
1069 Standard for the Format of ARPA Internet Text Messages.
1072 Standard for Interchange of USENET Messages
1075 Format of Internet Message Bodies
1081 Message Header Extensions for Non-ASCII Text
1084 Registration Procedures
1087 Conformance Criteria and Examples
1090 MIME Parameter Value and Encoded Word Extensions: Character Sets,
1091 Languages, and Continuations
1094 HZ - A Data Format for Exchanging Files of Arbitrarily Mixed Chinese and
1097 @item draft-ietf-drums-msg-fmt-05.txt
1098 Draft for the successor of RFC822
1101 The MIME Multipart/Related Content-type
1104 The Multipart/Report Content Type for the Reporting of Mail System
1105 Administrative Messages
1108 Communicating Presentation Information in Internet Messages: The
1109 Content-Disposition Header Field