Mercurial > emacs
annotate doc/misc/emacs-mime.texi @ 99012:1672f297f7ed
* files.texi (Diff Mode): Document diff-show-trailing-whitespaces.
author | Chong Yidong <cyd@stupidchicken.com> |
---|---|
date | Tue, 21 Oct 2008 23:16:21 +0000 |
parents | 6f0fce2c3559 |
children | 6de181810d0f |
rev | line source |
---|---|
84292 | 1 \input texinfo |
2 | |
84329
3d431f1997d8
(setfilename): Go up one more level to ../../info.
Glenn Morris <rgm@gnu.org>
parents:
84292
diff
changeset
|
3 @setfilename ../../info/emacs-mime |
84292 | 4 @settitle Emacs MIME Manual |
5 @synindex fn cp | |
6 @synindex vr cp | |
7 @synindex pg cp | |
8 | |
9 @copying | |
10 This file documents the Emacs MIME interface functionality. | |
11 | |
12 Copyright @copyright{} 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, | |
87903 | 13 2006, 2007, 2008 Free Software Foundation, Inc. |
84292 | 14 |
15 @quotation | |
16 Permission is granted to copy, distribute and/or modify this document | |
17 under the terms of the GNU Free Documentation License, Version 1.2 or | |
18 any later version published by the Free Software Foundation; with no | |
95937
6f0fce2c3559
Remove references to external license, since doclicense is included.
Glenn Morris <rgm@gnu.org>
parents:
95874
diff
changeset
|
19 Invariant Sections, with the Front-Cover texts being ``A GNU Manual'', |
6f0fce2c3559
Remove references to external license, since doclicense is included.
Glenn Morris <rgm@gnu.org>
parents:
95874
diff
changeset
|
20 and with the Back-Cover Texts as in (a) below. A copy of the license |
6f0fce2c3559
Remove references to external license, since doclicense is included.
Glenn Morris <rgm@gnu.org>
parents:
95874
diff
changeset
|
21 is included in the section entitled ``GNU Free Documentation License''. |
84292 | 22 |
95874
eafbd7a5c9be
Update Back-Cover Text as per maintain.info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
23 (a) The FSF's Back-Cover Text is: ``You have the freedom to copy and |
eafbd7a5c9be
Update Back-Cover Text as per maintain.info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
24 modify this GNU manual. Buying copies from the FSF supports it in |
eafbd7a5c9be
Update Back-Cover Text as per maintain.info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
25 developing GNU and promoting software freedom.'' |
84292 | 26 @end quotation |
27 @end copying | |
28 | |
29 @c Node ``Interface Functions'' uses Latin-1 characters | |
30 @documentencoding ISO-8859-1 | |
31 | |
32 @dircategory Emacs | |
33 @direntry | |
34 * Emacs MIME: (emacs-mime). Emacs MIME de/composition library. | |
35 @end direntry | |
36 @iftex | |
37 @finalout | |
38 @end iftex | |
39 @setchapternewpage odd | |
40 | |
41 @titlepage | |
42 @title Emacs MIME Manual | |
43 | |
44 @author by Lars Magne Ingebrigtsen | |
45 @page | |
46 @vskip 0pt plus 1filll | |
47 @insertcopying | |
48 @end titlepage | |
49 | |
50 @node Top | |
51 @top Emacs MIME | |
52 | |
53 This manual documents the libraries used to compose and display | |
54 @acronym{MIME} messages. | |
55 | |
56 This manual is directed at users who want to modify the behavior of | |
57 the @acronym{MIME} encoding/decoding process or want a more detailed | |
58 picture of how the Emacs @acronym{MIME} library works, and people who want | |
59 to write functions and commands that manipulate @acronym{MIME} elements. | |
60 | |
61 @acronym{MIME} is short for @dfn{Multipurpose Internet Mail Extensions}. | |
62 This standard is documented in a number of RFCs; mainly RFC2045 (Format | |
63 of Internet Message Bodies), RFC2046 (Media Types), RFC2047 (Message | |
64 Header Extensions for Non-@acronym{ASCII} Text), RFC2048 (Registration | |
65 Procedures), RFC2049 (Conformance Criteria and Examples). It is highly | |
66 recommended that anyone who intends writing @acronym{MIME}-compliant software | |
67 read at least RFC2045 and RFC2047. | |
68 | |
69 @menu | |
70 * Decoding and Viewing:: A framework for decoding and viewing. | |
71 * Composing:: @acronym{MML}; a language for describing @acronym{MIME} parts. | |
72 * Interface Functions:: An abstraction over the basic functions. | |
73 * Basic Functions:: Utility and basic parsing functions. | |
74 * Standards:: A summary of RFCs and working documents used. | |
75 * GNU Free Documentation License:: The license for this documentation. | |
76 * Index:: Function and variable index. | |
77 @end menu | |
78 | |
79 | |
80 @node Decoding and Viewing | |
81 @chapter Decoding and Viewing | |
82 | |
83 This chapter deals with decoding and viewing @acronym{MIME} messages on a | |
84 higher level. | |
85 | |
86 The main idea is to first analyze a @acronym{MIME} article, and then allow | |
87 other programs to do things based on the list of @dfn{handles} that are | |
88 returned as a result of this analysis. | |
89 | |
90 @menu | |
91 * Dissection:: Analyzing a @acronym{MIME} message. | |
92 * Non-MIME:: Analyzing a non-@acronym{MIME} message. | |
93 * Handles:: Handle manipulations. | |
94 * Display:: Displaying handles. | |
95 * Display Customization:: Variables that affect display. | |
96 * Files and Directories:: Saving and naming attachments. | |
97 * New Viewers:: How to write your own viewers. | |
98 @end menu | |
99 | |
100 | |
101 @node Dissection | |
102 @section Dissection | |
103 | |
104 The @code{mm-dissect-buffer} is the function responsible for dissecting | |
105 a @acronym{MIME} article. If given a multipart message, it will recursively | |
106 descend the message, following the structure, and return a tree of | |
107 @acronym{MIME} handles that describes the structure of the message. | |
108 | |
109 @node Non-MIME | |
110 @section Non-MIME | |
111 @vindex mm-uu-configure-list | |
112 | |
113 Gnus also understands some non-@acronym{MIME} attachments, such as | |
114 postscript, uuencode, binhex, yenc, shar, forward, gnatsweb, pgp, | |
115 diff. Each of these features can be disabled by add an item into | |
116 @code{mm-uu-configure-list}. For example, | |
117 | |
118 @lisp | |
119 (require 'mm-uu) | |
120 (add-to-list 'mm-uu-configure-list '(pgp-signed . disabled)) | |
121 @end lisp | |
122 | |
123 @table @code | |
124 @item postscript | |
125 @findex postscript | |
126 PostScript file. | |
127 | |
128 @item uu | |
129 @findex uu | |
130 Uuencoded file. | |
131 | |
132 @item binhex | |
133 @findex binhex | |
134 Binhex encoded file. | |
135 | |
136 @item yenc | |
137 @findex yenc | |
138 Yenc encoded file. | |
139 | |
140 @item shar | |
141 @findex shar | |
142 Shar archive file. | |
143 | |
144 @item forward | |
145 @findex forward | |
146 Non-@acronym{MIME} forwarded message. | |
147 | |
148 @item gnatsweb | |
149 @findex gnatsweb | |
150 Gnatsweb attachment. | |
151 | |
152 @item pgp-signed | |
153 @findex pgp-signed | |
154 @acronym{PGP} signed clear text. | |
155 | |
156 @item pgp-encrypted | |
157 @findex pgp-encrypted | |
158 @acronym{PGP} encrypted clear text. | |
159 | |
160 @item pgp-key | |
161 @findex pgp-key | |
162 @acronym{PGP} public keys. | |
163 | |
164 @item emacs-sources | |
165 @findex emacs-sources | |
166 @vindex mm-uu-emacs-sources-regexp | |
167 Emacs source code. This item works only in the groups matching | |
168 @code{mm-uu-emacs-sources-regexp}. | |
169 | |
170 @item diff | |
171 @vindex diff | |
172 @vindex mm-uu-diff-groups-regexp | |
173 Patches. This is intended for groups where diffs of committed files | |
174 are automatically sent to. It only works in groups matching | |
175 @code{mm-uu-diff-groups-regexp}. | |
176 | |
85712
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
177 @item verbatim-marks |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
178 @cindex verbatim-marks |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
179 Slrn-style verbatim marks. |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
180 |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
181 @item LaTeX |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
182 @cindex LaTeX |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
183 LaTeX documents. It only works in groups matching |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
184 @code{mm-uu-tex-groups-regexp}. |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
185 |
84292 | 186 @end table |
187 | |
85712
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
188 @cindex text/x-verbatim |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
189 @c Is @vindex suitable for a face? |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
190 @vindex mm-uu-extract |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
191 Some inlined non-@acronym{MIME} attachments are displayed using the face |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
192 @code{mm-uu-extract}. By default, no @acronym{MIME} button for these |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
193 parts is displayed. You can force displaying a button using @kbd{K b} |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
194 (@code{gnus-summary-display-buttonized}) or add @code{text/x-verbatim} |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
195 to @code{gnus-buttonized-mime-types}, @xref{MIME Commands, ,MIME |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
196 Commands, gnus, Gnus Manual}. |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
197 |
84292 | 198 @node Handles |
199 @section Handles | |
200 | |
201 A @acronym{MIME} handle is a list that fully describes a @acronym{MIME} | |
202 component. | |
203 | |
204 The following macros can be used to access elements in a handle: | |
205 | |
206 @table @code | |
207 @item mm-handle-buffer | |
208 @findex mm-handle-buffer | |
209 Return the buffer that holds the contents of the undecoded @acronym{MIME} | |
210 part. | |
211 | |
212 @item mm-handle-type | |
213 @findex mm-handle-type | |
214 Return the parsed @code{Content-Type} of the part. | |
215 | |
216 @item mm-handle-encoding | |
217 @findex mm-handle-encoding | |
218 Return the @code{Content-Transfer-Encoding} of the part. | |
219 | |
220 @item mm-handle-undisplayer | |
221 @findex mm-handle-undisplayer | |
222 Return the object that can be used to remove the displayed part (if it | |
223 has been displayed). | |
224 | |
225 @item mm-handle-set-undisplayer | |
226 @findex mm-handle-set-undisplayer | |
227 Set the undisplayer object. | |
228 | |
229 @item mm-handle-disposition | |
230 @findex mm-handle-disposition | |
231 Return the parsed @code{Content-Disposition} of the part. | |
232 | |
233 @item mm-get-content-id | |
234 Returns the handle(s) referred to by @code{Content-ID}. | |
235 | |
236 @end table | |
237 | |
238 | |
239 @node Display | |
240 @section Display | |
241 | |
242 Functions for displaying, removing and saving. | |
243 | |
244 @table @code | |
245 @item mm-display-part | |
246 @findex mm-display-part | |
247 Display the part. | |
248 | |
249 @item mm-remove-part | |
250 @findex mm-remove-part | |
251 Remove the part (if it has been displayed). | |
252 | |
253 @item mm-inlinable-p | |
254 @findex mm-inlinable-p | |
255 Say whether a @acronym{MIME} type can be displayed inline. | |
256 | |
257 @item mm-automatic-display-p | |
258 @findex mm-automatic-display-p | |
259 Say whether a @acronym{MIME} type should be displayed automatically. | |
260 | |
261 @item mm-destroy-part | |
262 @findex mm-destroy-part | |
263 Free all resources occupied by a part. | |
264 | |
265 @item mm-save-part | |
266 @findex mm-save-part | |
267 Offer to save the part in a file. | |
268 | |
269 @item mm-pipe-part | |
270 @findex mm-pipe-part | |
271 Offer to pipe the part to some process. | |
272 | |
273 @item mm-interactively-view-part | |
274 @findex mm-interactively-view-part | |
275 Prompt for a mailcap method to use to view the part. | |
276 | |
277 @end table | |
278 | |
279 | |
280 @node Display Customization | |
281 @section Display Customization | |
282 | |
283 @table @code | |
284 | |
285 @item mm-inline-media-tests | |
286 @vindex mm-inline-media-tests | |
287 This is an alist where the key is a @acronym{MIME} type, the second element | |
288 is a function to display the part @dfn{inline} (i.e., inside Emacs), and | |
289 the third element is a form to be @code{eval}ed to say whether the part | |
290 can be displayed inline. | |
291 | |
292 This variable specifies whether a part @emph{can} be displayed inline, | |
293 and, if so, how to do it. It does not say whether parts are | |
294 @emph{actually} displayed inline. | |
295 | |
296 @item mm-inlined-types | |
297 @vindex mm-inlined-types | |
298 This, on the other hand, says what types are to be displayed inline, if | |
299 they satisfy the conditions set by the variable above. It's a list of | |
300 @acronym{MIME} media types. | |
301 | |
302 @item mm-automatic-display | |
303 @vindex mm-automatic-display | |
304 This is a list of types that are to be displayed ``automatically'', but | |
305 only if the above variable allows it. That is, only inlinable parts can | |
306 be displayed automatically. | |
307 | |
308 @item mm-automatic-external-display | |
309 @vindex mm-automatic-external-display | |
310 This is a list of types that will be displayed automatically in an | |
311 external viewer. | |
312 | |
313 @item mm-keep-viewer-alive-types | |
314 @vindex mm-keep-viewer-alive-types | |
315 This is a list of media types for which the external viewer will not | |
316 be killed when selecting a different article. | |
317 | |
318 @item mm-attachment-override-types | |
319 @vindex mm-attachment-override-types | |
320 Some @acronym{MIME} agents create parts that have a content-disposition of | |
321 @samp{attachment}. This variable allows overriding that disposition and | |
322 displaying the part inline. (Note that the disposition is only | |
323 overridden if we are able to, and want to, display the part inline.) | |
324 | |
325 @item mm-discouraged-alternatives | |
326 @vindex mm-discouraged-alternatives | |
327 List of @acronym{MIME} types that are discouraged when viewing | |
328 @samp{multipart/alternative}. Viewing agents are supposed to view the | |
329 last possible part of a message, as that is supposed to be the richest. | |
330 However, users may prefer other types instead, and this list says what | |
331 types are most unwanted. If, for instance, @samp{text/html} parts are | |
332 very unwanted, and @samp{text/richtext} parts are somewhat unwanted, | |
333 you could say something like: | |
334 | |
335 @lisp | |
336 (setq mm-discouraged-alternatives | |
337 '("text/html" "text/richtext") | |
338 mm-automatic-display | |
339 (remove "text/html" mm-automatic-display)) | |
340 @end lisp | |
341 | |
342 Adding @code{"image/.*"} might also be useful. Spammers use images as | |
343 the preferred part of @samp{multipart/alternative} messages, so you might | |
344 not notice there are other parts. See also | |
345 @code{gnus-buttonized-mime-types}, @ref{MIME Commands, ,MIME Commands, | |
346 gnus, Gnus Manual}. After adding @code{"multipart/alternative"} to | |
347 @code{gnus-buttonized-mime-types} you can choose manually which | |
348 alternative you'd like to view. For example, you can set those | |
349 variables like: | |
350 | |
351 @lisp | |
352 (setq gnus-buttonized-mime-types | |
353 '("multipart/alternative" "multipart/signed") | |
354 mm-discouraged-alternatives | |
355 '("text/html" "image/.*")) | |
356 @end lisp | |
357 | |
358 In this case, Gnus will display radio buttons for such a kind of spam | |
359 message as follows: | |
360 | |
361 @example | |
362 1. (*) multipart/alternative ( ) image/gif | |
363 | |
364 2. (*) text/plain ( ) text/html | |
365 @end example | |
366 | |
367 @item mm-inline-large-images | |
368 @vindex mm-inline-large-images | |
369 When displaying inline images that are larger than the window, Emacs | |
370 does not enable scrolling, which means that you cannot see the whole | |
371 image. To prevent this, the library tries to determine the image size | |
372 before displaying it inline, and if it doesn't fit the window, the | |
373 library will display it externally (e.g. with @samp{ImageMagick} or | |
374 @samp{xv}). Setting this variable to @code{t} disables this check and | |
375 makes the library display all inline images as inline, regardless of | |
376 their size. | |
377 | |
378 @item mm-inline-override-types | |
379 @vindex mm-inline-override-types | |
380 @code{mm-inlined-types} may include regular expressions, for example to | |
381 specify that all @samp{text/.*} parts be displayed inline. If a user | |
382 prefers to have a type that matches such a regular expression be treated | |
383 as an attachment, that can be accomplished by setting this variable to a | |
384 list containing that type. For example assuming @code{mm-inlined-types} | |
385 includes @samp{text/.*}, then including @samp{text/html} in this | |
386 variable will cause @samp{text/html} parts to be treated as attachments. | |
387 | |
388 @item mm-text-html-renderer | |
389 @vindex mm-text-html-renderer | |
390 This selects the function used to render @acronym{HTML}. The predefined | |
391 renderers are selected by the symbols @code{w3}, | |
392 @code{w3m}@footnote{See @uref{http://emacs-w3m.namazu.org/} for more | |
393 information about emacs-w3m}, @code{links}, @code{lynx}, | |
394 @code{w3m-standalone} or @code{html2text}. If @code{nil} use an | |
395 external viewer. You can also specify a function, which will be | |
396 called with a @acronym{MIME} handle as the argument. | |
397 | |
398 @item mm-inline-text-html-with-images | |
399 @vindex mm-inline-text-html-with-images | |
400 Some @acronym{HTML} mails might have the trick of spammers using | |
401 @samp{<img>} tags. It is likely to be intended to verify whether you | |
402 have read the mail. You can prevent your personal informations from | |
403 leaking by setting this option to @code{nil} (which is the default). | |
404 It is currently ignored by Emacs/w3. For emacs-w3m, you may use the | |
405 command @kbd{t} on the image anchor to show an image even if it is | |
406 @code{nil}.@footnote{The command @kbd{T} will load all images. If you | |
407 have set the option @code{w3m-key-binding} to @code{info}, use @kbd{i} | |
408 or @kbd{I} instead.} | |
409 | |
410 @item mm-w3m-safe-url-regexp | |
411 @vindex mm-w3m-safe-url-regexp | |
412 A regular expression that matches safe URL names, i.e. URLs that are | |
413 unlikely to leak personal information when rendering @acronym{HTML} | |
414 email (the default value is @samp{\\`cid:}). If @code{nil} consider | |
415 all URLs safe. | |
416 | |
417 @item mm-inline-text-html-with-w3m-keymap | |
418 @vindex mm-inline-text-html-with-w3m-keymap | |
419 You can use emacs-w3m command keys in the inlined text/html part by | |
420 setting this option to non-@code{nil}. The default value is @code{t}. | |
421 | |
422 @item mm-external-terminal-program | |
423 @vindex mm-external-terminal-program | |
424 The program used to start an external terminal. | |
425 | |
426 @item mm-enable-external | |
427 @vindex mm-enable-external | |
428 Indicate whether external @acronym{MIME} handlers should be used. | |
429 | |
430 If @code{t}, all defined external @acronym{MIME} handlers are used. If | |
431 @code{nil}, files are saved to disk (@code{mailcap-save-binary-file}). | |
432 If it is the symbol @code{ask}, you are prompted before the external | |
433 @acronym{MIME} handler is invoked. | |
434 | |
435 When you launch an attachment through mailcap (@pxref{mailcap}) an | |
436 attempt is made to use a safe viewer with the safest options---this isn't | |
437 the case if you save it to disk and launch it in a different way | |
438 (command line or double-clicking). Anyhow, if you want to be sure not | |
439 to launch any external programs, set this variable to @code{nil} or | |
440 @code{ask}. | |
441 | |
442 @end table | |
443 | |
444 @node Files and Directories | |
445 @section Files and Directories | |
446 | |
447 @table @code | |
448 | |
449 @item mm-default-directory | |
450 @vindex mm-default-directory | |
451 The default directory for saving attachments. If @code{nil} use | |
452 @code{default-directory}. | |
453 | |
454 @item mm-tmp-directory | |
455 @vindex mm-tmp-directory | |
456 Directory for storing temporary files. | |
457 | |
458 @item mm-file-name-rewrite-functions | |
459 @vindex mm-file-name-rewrite-functions | |
460 A list of functions used for rewriting file names of @acronym{MIME} | |
461 parts. Each function is applied successively to the file name. | |
462 Ready-made functions include | |
463 | |
464 @table @code | |
465 @item mm-file-name-delete-control | |
466 @findex mm-file-name-delete-control | |
467 Delete all control characters. | |
468 | |
469 @item mm-file-name-delete-gotchas | |
470 @findex mm-file-name-delete-gotchas | |
471 Delete characters that could have unintended consequences when used | |
472 with flawed shell scripts, i.e. @samp{|}, @samp{>} and @samp{<}; and | |
473 @samp{-}, @samp{.} as the first character. | |
474 | |
475 @item mm-file-name-delete-whitespace | |
476 @findex mm-file-name-delete-whitespace | |
477 Remove all whitespace. | |
478 | |
479 @item mm-file-name-trim-whitespace | |
480 @findex mm-file-name-trim-whitespace | |
481 Remove leading and trailing whitespace. | |
482 | |
483 @item mm-file-name-collapse-whitespace | |
484 @findex mm-file-name-collapse-whitespace | |
485 Collapse multiple whitespace characters. | |
486 | |
487 @item mm-file-name-replace-whitespace | |
488 @findex mm-file-name-replace-whitespace | |
489 @vindex mm-file-name-replace-whitespace | |
490 Replace whitespace with underscores. Set the variable | |
491 @code{mm-file-name-replace-whitespace} to any other string if you do | |
492 not like underscores. | |
493 @end table | |
494 | |
495 The standard Emacs functions @code{capitalize}, @code{downcase}, | |
496 @code{upcase} and @code{upcase-initials} might also prove useful. | |
497 | |
498 @item mm-path-name-rewrite-functions | |
499 @vindex mm-path-name-rewrite-functions | |
500 List of functions used for rewriting the full file names of @acronym{MIME} | |
501 parts. This is used when viewing parts externally, and is meant for | |
502 transforming the absolute name so that non-compliant programs can find | |
503 the file where it's saved. | |
504 | |
505 @end table | |
506 | |
507 @node New Viewers | |
508 @section New Viewers | |
509 | |
510 Here's an example viewer for displaying @code{text/enriched} inline: | |
511 | |
512 @lisp | |
513 (defun mm-display-enriched-inline (handle) | |
514 (let (text) | |
515 (with-temp-buffer | |
516 (mm-insert-part handle) | |
517 (save-window-excursion | |
518 (enriched-decode (point-min) (point-max)) | |
519 (setq text (buffer-string)))) | |
520 (mm-insert-inline handle text))) | |
521 @end lisp | |
522 | |
523 We see that the function takes a @acronym{MIME} handle as its parameter. It | |
524 then goes to a temporary buffer, inserts the text of the part, does some | |
525 work on the text, stores the result, goes back to the buffer it was | |
526 called from and inserts the result. | |
527 | |
528 The two important helper functions here are @code{mm-insert-part} and | |
529 @code{mm-insert-inline}. The first function inserts the text of the | |
530 handle in the current buffer. It handles charset and/or content | |
531 transfer decoding. The second function just inserts whatever text you | |
532 tell it to insert, but it also sets things up so that the text can be | |
533 ``undisplayed'' in a convenient manner. | |
534 | |
535 | |
536 @node Composing | |
537 @chapter Composing | |
538 @cindex Composing | |
539 @cindex MIME Composing | |
540 @cindex MML | |
541 @cindex MIME Meta Language | |
542 | |
543 Creating a @acronym{MIME} message is boring and non-trivial. Therefore, | |
544 a library called @code{mml} has been defined that parses a language | |
545 called @acronym{MML} (@acronym{MIME} Meta Language) and generates | |
546 @acronym{MIME} messages. | |
547 | |
548 @findex mml-generate-mime | |
549 The main interface function is @code{mml-generate-mime}. It will | |
550 examine the contents of the current (narrowed-to) buffer and return a | |
551 string containing the @acronym{MIME} message. | |
552 | |
553 @menu | |
554 * Simple MML Example:: An example @acronym{MML} document. | |
555 * MML Definition:: All valid @acronym{MML} elements. | |
556 * Advanced MML Example:: Another example @acronym{MML} document. | |
557 * Encoding Customization:: Variables that affect encoding. | |
558 * Charset Translation:: How charsets are mapped from @sc{mule} to @acronym{MIME}. | |
559 * Conversion:: Going from @acronym{MIME} to @acronym{MML} and vice versa. | |
560 * Flowed text:: Soft and hard newlines. | |
561 @end menu | |
562 | |
563 | |
564 @node Simple MML Example | |
565 @section Simple MML Example | |
566 | |
567 Here's a simple @samp{multipart/alternative}: | |
568 | |
569 @example | |
570 <#multipart type=alternative> | |
571 This is a plain text part. | |
572 <#part type=text/enriched> | |
573 <center>This is a centered enriched part</center> | |
574 <#/multipart> | |
575 @end example | |
576 | |
577 After running this through @code{mml-generate-mime}, we get this: | |
578 | |
579 @example | |
580 Content-Type: multipart/alternative; boundary="=-=-=" | |
581 | |
582 | |
583 --=-=-= | |
584 | |
585 | |
586 This is a plain text part. | |
587 | |
588 --=-=-= | |
589 Content-Type: text/enriched | |
590 | |
591 | |
592 <center>This is a centered enriched part</center> | |
593 | |
594 --=-=-=-- | |
595 @end example | |
596 | |
597 | |
598 @node MML Definition | |
599 @section MML Definition | |
600 | |
601 The @acronym{MML} language is very simple. It looks a bit like an SGML | |
602 application, but it's not. | |
603 | |
604 The main concept of @acronym{MML} is the @dfn{part}. Each part can be of a | |
605 different type or use a different charset. The way to delineate a part | |
606 is with a @samp{<#part ...>} tag. Multipart parts can be introduced | |
607 with the @samp{<#multipart ...>} tag. Parts are ended by the | |
608 @samp{<#/part>} or @samp{<#/multipart>} tags. Parts started with the | |
609 @samp{<#part ...>} tags are also closed by the next open tag. | |
610 | |
611 There's also the @samp{<#external ...>} tag. These introduce | |
612 @samp{external/message-body} parts. | |
613 | |
614 Each tag can contain zero or more parameters on the form | |
615 @samp{parameter=value}. The values may be enclosed in quotation marks, | |
616 but that's not necessary unless the value contains white space. So | |
617 @samp{filename=/home/user/#hello$^yes} is perfectly valid. | |
618 | |
619 The following parameters have meaning in @acronym{MML}; parameters that have no | |
620 meaning are ignored. The @acronym{MML} parameter names are the same as the | |
621 @acronym{MIME} parameter names; the things in the parentheses say which | |
622 header it will be used in. | |
623 | |
624 @table @samp | |
625 @item type | |
626 The @acronym{MIME} type of the part (@code{Content-Type}). | |
627 | |
628 @item filename | |
629 Use the contents of the file in the body of the part | |
630 (@code{Content-Disposition}). | |
631 | |
632 @item charset | |
633 The contents of the body of the part are to be encoded in the character | |
634 set specified (@code{Content-Type}). @xref{Charset Translation}. | |
635 | |
636 @item name | |
637 Might be used to suggest a file name if the part is to be saved | |
638 to a file (@code{Content-Type}). | |
639 | |
640 @item disposition | |
641 Valid values are @samp{inline} and @samp{attachment} | |
642 (@code{Content-Disposition}). | |
643 | |
644 @item encoding | |
645 Valid values are @samp{7bit}, @samp{8bit}, @samp{quoted-printable} and | |
646 @samp{base64} (@code{Content-Transfer-Encoding}). @xref{Charset | |
647 Translation}. | |
648 | |
649 @item description | |
650 A description of the part (@code{Content-Description}). | |
651 | |
652 @item creation-date | |
653 RFC822 date when the part was created (@code{Content-Disposition}). | |
654 | |
655 @item modification-date | |
656 RFC822 date when the part was modified (@code{Content-Disposition}). | |
657 | |
658 @item read-date | |
659 RFC822 date when the part was read (@code{Content-Disposition}). | |
660 | |
661 @item recipients | |
662 Who to encrypt/sign the part to. This field is used to override any | |
663 auto-detection based on the To/CC headers. | |
664 | |
665 @item sender | |
666 Identity used to sign the part. This field is used to override the | |
667 default key used. | |
668 | |
669 @item size | |
670 The size (in octets) of the part (@code{Content-Disposition}). | |
671 | |
672 @item sign | |
673 What technology to sign this @acronym{MML} part with (@code{smime}, @code{pgp} | |
674 or @code{pgpmime}) | |
675 | |
676 @item encrypt | |
677 What technology to encrypt this @acronym{MML} part with (@code{smime}, | |
678 @code{pgp} or @code{pgpmime}) | |
679 | |
680 @end table | |
681 | |
682 Parameters for @samp{text/plain}: | |
683 | |
684 @table @samp | |
685 @item format | |
686 Formatting parameter for the text, valid values include @samp{fixed} | |
687 (the default) and @samp{flowed}. Normally you do not specify this | |
688 manually, since it requires the textual body to be formatted in a | |
689 special way described in RFC 2646. @xref{Flowed text}. | |
690 @end table | |
691 | |
692 Parameters for @samp{application/octet-stream}: | |
693 | |
694 @table @samp | |
695 @item type | |
696 Type of the part; informal---meant for human readers | |
697 (@code{Content-Type}). | |
698 @end table | |
699 | |
700 Parameters for @samp{message/external-body}: | |
701 | |
702 @table @samp | |
703 @item access-type | |
704 A word indicating the supported access mechanism by which the file may | |
705 be obtained. Values include @samp{ftp}, @samp{anon-ftp}, @samp{tftp}, | |
706 @samp{localfile}, and @samp{mailserver}. (@code{Content-Type}.) | |
707 | |
708 @item expiration | |
709 The RFC822 date after which the file may no longer be fetched. | |
710 (@code{Content-Type}.) | |
711 | |
712 @item size | |
713 The size (in octets) of the file. (@code{Content-Type}.) | |
714 | |
715 @item permission | |
716 Valid values are @samp{read} and @samp{read-write} | |
717 (@code{Content-Type}). | |
718 | |
719 @end table | |
720 | |
721 Parameters for @samp{sign=smime}: | |
722 | |
723 @table @samp | |
724 | |
725 @item keyfile | |
726 File containing key and certificate for signer. | |
727 | |
728 @end table | |
729 | |
730 Parameters for @samp{encrypt=smime}: | |
731 | |
732 @table @samp | |
733 | |
734 @item certfile | |
735 File containing certificate for recipient. | |
736 | |
737 @end table | |
738 | |
739 | |
740 @node Advanced MML Example | |
741 @section Advanced MML Example | |
742 | |
743 Here's a complex multipart message. It's a @samp{multipart/mixed} that | |
744 contains many parts, one of which is a @samp{multipart/alternative}. | |
745 | |
746 @example | |
747 <#multipart type=mixed> | |
748 <#part type=image/jpeg filename=~/rms.jpg disposition=inline> | |
749 <#multipart type=alternative> | |
750 This is a plain text part. | |
751 <#part type=text/enriched name=enriched.txt> | |
752 <center>This is a centered enriched part</center> | |
753 <#/multipart> | |
754 This is a new plain text part. | |
755 <#part disposition=attachment> | |
756 This plain text part is an attachment. | |
757 <#/multipart> | |
758 @end example | |
759 | |
760 And this is the resulting @acronym{MIME} message: | |
761 | |
762 @example | |
763 Content-Type: multipart/mixed; boundary="=-=-=" | |
764 | |
765 | |
766 --=-=-= | |
767 | |
768 | |
769 | |
770 --=-=-= | |
771 Content-Type: image/jpeg; | |
772 filename="~/rms.jpg" | |
773 Content-Disposition: inline; | |
774 filename="~/rms.jpg" | |
775 Content-Transfer-Encoding: base64 | |
776 | |
777 /9j/4AAQSkZJRgABAQAAAQABAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRof | |
778 Hh0aHBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/wAALCAAwADABAREA/8QAHwAA | |
779 AQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQR | |
780 BRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q0RF | |
781 RkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ip | |
782 qrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/9oACAEB | |
783 AAA/AO/rifFHjldNuGsrDa0qcSSHkA+gHrXKw+LtWLrMb+RgTyhbr+HSug07xNqV9fQtZrNI | |
784 AyiaE/NuBPOOOP0rvRNE880KOC8TbXXGCv1FPqjrF4LDR7u5L7SkTFT/ALWOP1xXgTuXfc7E | |
785 sx6nua6rwp4IvvEM8chCxWxOdzn7wz6V9AaB4S07w9p5itow0rDLSY5Pt9K43xO66P4xs71m | |
786 2QXiGCbA4yOVJ9+1aYORkdK434lyNH4ahCnG66VT9Nj15JFbPdX0MS43M4VQf5/yr2vSpLnw | |
787 5ZW8dlCZ8KFXjOPX0/mK6rSPEGt3Angu44fNEReHYNvIH3TzXDeKNO8RX+kSX2ouZkicTIOc | |
788 L+g7E810ulFjpVtv3bwgB3HJyK5L4quY/C9sVxk3ij/xx6850u7t1mtp/wDlpEw3An3Jr3Dw | |
789 34gsbWza4nBlhC5LDsaW6+IFgupQyCF3iHH7gA7c9R9ay7zx6t7aX9jHC4smhfBkGCvHGfrm | |
790 tLQ7hbnRrV1GPkAP1x1/Hr+Ncr8Vzjwrbf8AX6v/AKA9eQRyYlQk8Yx9K6XTNbkgia2ciSIn | |
791 7p5Ga9Atte0LTLKO6it4i7dVRFJDcZ4PvXN+JvEMF9bILVGXJLSZ4zkjivRPDaeX4b08HOTC | |
792 pOffmua+KkbS+GLVUGT9tT/0B68eeIpIFYjB70+OOVXyoOM9+M1eaWeCLzHPyHGO/NVWvJJm | |
793 jQ8KGH1NfQWhXSXmh2c8eArRLwO3HSv/2Q== | |
794 | |
795 --=-=-= | |
796 Content-Type: multipart/alternative; boundary="==-=-=" | |
797 | |
798 | |
799 --==-=-= | |
800 | |
801 | |
802 This is a plain text part. | |
803 | |
804 --==-=-= | |
805 Content-Type: text/enriched; | |
806 name="enriched.txt" | |
807 | |
808 | |
809 <center>This is a centered enriched part</center> | |
810 | |
811 --==-=-=-- | |
812 | |
813 --=-=-= | |
814 | |
815 This is a new plain text part. | |
816 | |
817 --=-=-= | |
818 Content-Disposition: attachment | |
819 | |
820 | |
821 This plain text part is an attachment. | |
822 | |
823 --=-=-=-- | |
824 @end example | |
825 | |
826 @node Encoding Customization | |
827 @section Encoding Customization | |
828 | |
829 @table @code | |
830 | |
831 @item mm-body-charset-encoding-alist | |
832 @vindex mm-body-charset-encoding-alist | |
833 Mapping from @acronym{MIME} charset to encoding to use. This variable is | |
834 usually used except, e.g., when other requirements force a specific | |
835 encoding (digitally signed messages require 7bit encodings). The | |
836 default is | |
837 | |
838 @lisp | |
839 ((iso-2022-jp . 7bit) | |
840 (iso-2022-jp-2 . 7bit) | |
841 (utf-16 . base64) | |
842 (utf-16be . base64) | |
843 (utf-16le . base64)) | |
844 @end lisp | |
845 | |
846 As an example, if you do not want to have ISO-8859-1 characters | |
847 quoted-printable encoded, you may add @code{(iso-8859-1 . 8bit)} to | |
848 this variable. You can override this setting on a per-message basis | |
849 by using the @code{encoding} @acronym{MML} tag (@pxref{MML Definition}). | |
850 | |
851 @item mm-coding-system-priorities | |
852 @vindex mm-coding-system-priorities | |
853 Prioritize coding systems to use for outgoing messages. The default | |
854 is @code{nil}, which means to use the defaults in Emacs, but is | |
855 @code{(iso-8859-1 iso-2022-jp iso-2022-jp-2 shift_jis utf-8)} when | |
856 running Emacs in the Japanese language environment. It is a list of | |
857 coding system symbols (aliases of coding systems are also allowed, use | |
858 @kbd{M-x describe-coding-system} to make sure you are specifying correct | |
859 coding system names). For example, if you have configured Emacs | |
860 to prefer UTF-8, but wish that outgoing messages should be sent in | |
861 ISO-8859-1 if possible, you can set this variable to | |
862 @code{(iso-8859-1)}. You can override this setting on a per-message | |
863 basis by using the @code{charset} @acronym{MML} tag (@pxref{MML Definition}). | |
864 | |
85712
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
865 As different hierarchies prefer different charsets, you may want to set |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
866 @code{mm-coding-system-priorities} according to the hierarchy in Gnus. |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
867 Here's an example: |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
868 |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
869 @c Corrections about preferred charsets are welcome. de, fr and fj |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
870 @c should be correct, I don't know about the rest (so these are only |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
871 @c examples): |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
872 @lisp |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
873 (add-to-list 'gnus-newsgroup-variables 'mm-coding-system-priorities) |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
874 (setq gnus-parameters |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
875 (nconc |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
876 ;; Some charsets are just examples! |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
877 '(("^cn\\." ;; Chinese |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
878 (mm-coding-system-priorities |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
879 '(iso-8859-1 cn-big5 chinese-iso-7bit utf-8))) |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
880 ("^cz\\.\\|^pl\\." ;; Central and Eastern European |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
881 (mm-coding-system-priorities '(iso-8859-2 utf-8))) |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
882 ("^de\\." ;; German language |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
883 (mm-coding-system-priorities '(iso-8859-1 iso-8859-15 utf-8))) |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
884 ("^fr\\." ;; French |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
885 (mm-coding-system-priorities '(iso-8859-15 iso-8859-1 utf-8))) |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
886 ("^fj\\." ;; Japanese |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
887 (mm-coding-system-priorities |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
888 '(iso-8859-1 iso-2022-jp iso-2022-jp-2 shift_jis utf-8))) |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
889 ("^ru\\." ;; Cyrillic |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
890 (mm-coding-system-priorities |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
891 '(koi8-r iso-8859-5 iso-8859-1 utf-8)))) |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
892 gnus-parameters)) |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
893 @end lisp |
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
894 |
84292 | 895 @item mm-content-transfer-encoding-defaults |
896 @vindex mm-content-transfer-encoding-defaults | |
897 Mapping from @acronym{MIME} types to encoding to use. This variable is usually | |
898 used except, e.g., when other requirements force a safer encoding | |
899 (digitally signed messages require 7bit encoding). Besides the normal | |
900 @acronym{MIME} encodings, @code{qp-or-base64} may be used to indicate that for | |
901 each case the most efficient of quoted-printable and base64 should be | |
902 used. | |
903 | |
904 @code{qp-or-base64} has another effect. It will fold long lines so that | |
905 MIME parts may not be broken by MTA. So do @code{quoted-printable} and | |
906 @code{base64}. | |
907 | |
908 Note that it affects body encoding only when a part is a raw forwarded | |
909 message (which will be made by @code{gnus-summary-mail-forward} with the | |
910 arg 2 for example) or is neither the @samp{text/*} type nor the | |
911 @samp{message/*} type. Even though in those cases, you can override | |
912 this setting on a per-message basis by using the @code{encoding} | |
913 @acronym{MML} tag (@pxref{MML Definition}). | |
914 | |
915 @item mm-use-ultra-safe-encoding | |
916 @vindex mm-use-ultra-safe-encoding | |
917 When this is non-@code{nil}, it means that textual parts are encoded as | |
918 quoted-printable if they contain lines longer than 76 characters or | |
919 starting with "From " in the body. Non-7bit encodings (8bit, binary) | |
920 are generally disallowed. This reduce the probability that a non-8bit | |
921 clean MTA or MDA changes the message. This should never be set | |
922 directly, but bound by other functions when necessary (e.g., when | |
923 encoding messages that are to be digitally signed). | |
924 | |
925 @end table | |
926 | |
927 @node Charset Translation | |
928 @section Charset Translation | |
929 @cindex charsets | |
930 | |
931 During translation from @acronym{MML} to @acronym{MIME}, for each | |
932 @acronym{MIME} part which has been composed inside Emacs, an appropriate | |
933 charset has to be chosen. | |
934 | |
935 @vindex mail-parse-charset | |
936 If you are running a non-@sc{mule} Emacs, this process is simple: If the | |
937 part contains any non-@acronym{ASCII} (8-bit) characters, the @acronym{MIME} charset | |
938 given by @code{mail-parse-charset} (a symbol) is used. (Never set this | |
939 variable directly, though. If you want to change the default charset, | |
940 please consult the documentation of the package which you use to process | |
941 @acronym{MIME} messages. | |
942 @xref{Various Message Variables, , Various Message Variables, message, | |
943 Message Manual}, for example.) | |
944 If there are only @acronym{ASCII} characters, the @acronym{MIME} charset US-ASCII is | |
945 used, of course. | |
946 | |
947 @cindex MULE | |
948 @cindex UTF-8 | |
949 @cindex Unicode | |
950 @vindex mm-mime-mule-charset-alist | |
951 Things are slightly more complicated when running Emacs with @sc{mule} | |
952 support. In this case, a list of the @sc{mule} charsets used in the | |
953 part is obtained, and the @sc{mule} charsets are translated to | |
954 @acronym{MIME} charsets by consulting the table provided by Emacs itself | |
955 or the variable @code{mm-mime-mule-charset-alist} for XEmacs. | |
956 If this results in a single @acronym{MIME} charset, this is used to encode | |
957 the part. But if the resulting list of @acronym{MIME} charsets contains more | |
958 than one element, two things can happen: If it is possible to encode the | |
959 part via UTF-8, this charset is used. (For this, Emacs must support | |
960 the @code{utf-8} coding system, and the part must consist entirely of | |
961 characters which have Unicode counterparts.) If UTF-8 is not available | |
962 for some reason, the part is split into several ones, so that each one | |
963 can be encoded with a single @acronym{MIME} charset. The part can only be | |
964 split at line boundaries, though---if more than one @acronym{MIME} charset is | |
965 required to encode a single line, it is not possible to encode the part. | |
966 | |
967 When running Emacs with @sc{mule} support, the preferences for which | |
968 coding system to use is inherited from Emacs itself. This means that | |
969 if Emacs is set up to prefer UTF-8, it will be used when encoding | |
970 messages. You can modify this by altering the | |
971 @code{mm-coding-system-priorities} variable though (@pxref{Encoding | |
972 Customization}). | |
973 | |
974 The charset to be used can be overridden by setting the @code{charset} | |
975 @acronym{MML} tag (@pxref{MML Definition}) when composing the message. | |
976 | |
977 The encoding of characters (quoted-printable, 8bit etc) is orthogonal | |
978 to the discussion here, and is controlled by the variables | |
979 @code{mm-body-charset-encoding-alist} and | |
980 @code{mm-content-transfer-encoding-defaults} (@pxref{Encoding | |
981 Customization}). | |
982 | |
983 @node Conversion | |
984 @section Conversion | |
985 | |
986 @findex mime-to-mml | |
987 A (multipart) @acronym{MIME} message can be converted to @acronym{MML} | |
988 with the @code{mime-to-mml} function. It works on the message in the | |
989 current buffer, and substitutes @acronym{MML} markup for @acronym{MIME} | |
990 boundaries. Non-textual parts do not have their contents in the buffer, | |
991 but instead have the contents in separate buffers that are referred to | |
992 from the @acronym{MML} tags. | |
993 | |
994 @findex mml-to-mime | |
995 An @acronym{MML} message can be converted back to @acronym{MIME} by the | |
996 @code{mml-to-mime} function. | |
997 | |
998 These functions are in certain senses ``lossy''---you will not get back | |
999 an identical message if you run @code{mime-to-mml} and then | |
1000 @code{mml-to-mime}. Not only will trivial things like the order of the | |
1001 headers differ, but the contents of the headers may also be different. | |
1002 For instance, the original message may use base64 encoding on text, | |
1003 while @code{mml-to-mime} may decide to use quoted-printable encoding, and | |
1004 so on. | |
1005 | |
1006 In essence, however, these two functions should be the inverse of each | |
1007 other. The resulting contents of the message should remain equivalent, | |
1008 if not identical. | |
1009 | |
1010 | |
1011 @node Flowed text | |
1012 @section Flowed text | |
1013 @cindex format=flowed | |
1014 | |
1015 The Emacs @acronym{MIME} library will respect the @code{use-hard-newlines} | |
1016 variable (@pxref{Hard and Soft Newlines, ,Hard and Soft Newlines, | |
1017 emacs, Emacs Manual}) when encoding a message, and the | |
1018 ``format=flowed'' Content-Type parameter when decoding a message. | |
1019 | |
1020 On encoding text, regardless of @code{use-hard-newlines}, lines | |
1021 terminated by soft newline characters are filled together and wrapped | |
1022 after the column decided by @code{fill-flowed-encode-column}. | |
1023 Quotation marks (matching @samp{^>* ?}) are respected. The variable | |
1024 controls how the text will look in a client that does not support | |
1025 flowed text, the default is to wrap after 66 characters. If hard | |
1026 newline characters are not present in the buffer, no flow encoding | |
1027 occurs. | |
1028 | |
1029 On decoding flowed text, lines with soft newline characters are filled | |
1030 together and wrapped after the column decided by | |
1031 @code{fill-flowed-display-column}. The default is to wrap after | |
1032 @code{fill-column}. | |
1033 | |
1034 @table @code | |
1035 @item mm-fill-flowed | |
1036 @vindex mm-fill-flowed | |
1037 If non-@code{nil} a format=flowed article will be displayed flowed. | |
1038 @end table | |
1039 | |
1040 | |
1041 @node Interface Functions | |
1042 @chapter Interface Functions | |
1043 @cindex interface functions | |
1044 @cindex mail-parse | |
1045 | |
1046 The @code{mail-parse} library is an abstraction over the actual | |
1047 low-level libraries that are described in the next chapter. | |
1048 | |
1049 Standards change, and so programs have to change to fit in the new | |
1050 mold. For instance, RFC2045 describes a syntax for the | |
1051 @code{Content-Type} header that only allows @acronym{ASCII} characters in the | |
1052 parameter list. RFC2231 expands on RFC2045 syntax to provide a scheme | |
1053 for continuation headers and non-@acronym{ASCII} characters. | |
1054 | |
1055 The traditional way to deal with this is just to update the library | |
1056 functions to parse the new syntax. However, this is sometimes the wrong | |
1057 thing to do. In some instances it may be vital to be able to understand | |
1058 both the old syntax as well as the new syntax, and if there is only one | |
1059 library, one must choose between the old version of the library and the | |
1060 new version of the library. | |
1061 | |
1062 The Emacs @acronym{MIME} library takes a different tack. It defines a | |
1063 series of low-level libraries (@file{rfc2047.el}, @file{rfc2231.el} | |
1064 and so on) that parses strictly according to the corresponding | |
1065 standard. However, normal programs would not use the functions | |
1066 provided by these libraries directly, but instead use the functions | |
1067 provided by the @code{mail-parse} library. The functions in this | |
1068 library are just aliases to the corresponding functions in the latest | |
1069 low-level libraries. Using this scheme, programs get a consistent | |
1070 interface they can use, and library developers are free to create | |
1071 write code that handles new standards. | |
1072 | |
1073 The following functions are defined by this library: | |
1074 | |
1075 @table @code | |
1076 @item mail-header-parse-content-type | |
1077 @findex mail-header-parse-content-type | |
1078 Parse a @code{Content-Type} header and return a list on the following | |
1079 format: | |
1080 | |
1081 @lisp | |
1082 ("type/subtype" | |
1083 (attribute1 . value1) | |
1084 (attribute2 . value2) | |
1085 ...) | |
1086 @end lisp | |
1087 | |
1088 Here's an example: | |
1089 | |
1090 @example | |
1091 (mail-header-parse-content-type | |
1092 "image/gif; name=\"b980912.gif\"") | |
1093 @result{} ("image/gif" (name . "b980912.gif")) | |
1094 @end example | |
1095 | |
1096 @item mail-header-parse-content-disposition | |
1097 @findex mail-header-parse-content-disposition | |
1098 Parse a @code{Content-Disposition} header and return a list on the same | |
1099 format as the function above. | |
1100 | |
1101 @item mail-content-type-get | |
1102 @findex mail-content-type-get | |
1103 Takes two parameters---a list on the format above, and an attribute. | |
1104 Returns the value of the attribute. | |
1105 | |
1106 @example | |
1107 (mail-content-type-get | |
1108 '("image/gif" (name . "b980912.gif")) 'name) | |
1109 @result{} "b980912.gif" | |
1110 @end example | |
1111 | |
1112 @item mail-header-encode-parameter | |
1113 @findex mail-header-encode-parameter | |
1114 Takes a parameter string and returns an encoded version of the string. | |
1115 This is used for parameters in headers like @code{Content-Type} and | |
1116 @code{Content-Disposition}. | |
1117 | |
1118 @item mail-header-remove-comments | |
1119 @findex mail-header-remove-comments | |
1120 Return a comment-free version of a header. | |
1121 | |
1122 @example | |
1123 (mail-header-remove-comments | |
1124 "Gnus/5.070027 (Pterodactyl Gnus v0.27) (Finnish Landrace)") | |
1125 @result{} "Gnus/5.070027 " | |
1126 @end example | |
1127 | |
1128 @item mail-header-remove-whitespace | |
1129 @findex mail-header-remove-whitespace | |
1130 Remove linear white space from a header. Space inside quoted strings | |
1131 and comments is preserved. | |
1132 | |
1133 @example | |
1134 (mail-header-remove-whitespace | |
1135 "image/gif; name=\"Name with spaces\"") | |
1136 @result{} "image/gif;name=\"Name with spaces\"" | |
1137 @end example | |
1138 | |
1139 @item mail-header-get-comment | |
1140 @findex mail-header-get-comment | |
1141 Return the last comment in a header. | |
1142 | |
1143 @example | |
1144 (mail-header-get-comment | |
1145 "Gnus/5.070027 (Pterodactyl Gnus v0.27) (Finnish Landrace)") | |
1146 @result{} "Finnish Landrace" | |
1147 @end example | |
1148 | |
1149 @item mail-header-parse-address | |
1150 @findex mail-header-parse-address | |
1151 Parse an address and return a list containing the mailbox and the | |
1152 plaintext name. | |
1153 | |
1154 @example | |
1155 (mail-header-parse-address | |
1156 "Hrvoje Niksic <hniksic@@srce.hr>") | |
1157 @result{} ("hniksic@@srce.hr" . "Hrvoje Niksic") | |
1158 @end example | |
1159 | |
1160 @item mail-header-parse-addresses | |
1161 @findex mail-header-parse-addresses | |
1162 Parse a string with list of addresses and return a list of elements like | |
1163 the one described above. | |
1164 | |
1165 @example | |
1166 (mail-header-parse-addresses | |
1167 "Hrvoje Niksic <hniksic@@srce.hr>, Steinar Bang <sb@@metis.no>") | |
1168 @result{} (("hniksic@@srce.hr" . "Hrvoje Niksic") | |
1169 ("sb@@metis.no" . "Steinar Bang")) | |
1170 @end example | |
1171 | |
1172 @item mail-header-parse-date | |
1173 @findex mail-header-parse-date | |
1174 Parse a date string and return an Emacs time structure. | |
1175 | |
1176 @item mail-narrow-to-head | |
1177 @findex mail-narrow-to-head | |
1178 Narrow the buffer to the header section of the buffer. Point is placed | |
1179 at the beginning of the narrowed buffer. | |
1180 | |
1181 @item mail-header-narrow-to-field | |
1182 @findex mail-header-narrow-to-field | |
1183 Narrow the buffer to the header under point. Understands continuation | |
1184 headers. | |
1185 | |
1186 @item mail-header-fold-field | |
1187 @findex mail-header-fold-field | |
1188 Fold the header under point. | |
1189 | |
1190 @item mail-header-unfold-field | |
1191 @findex mail-header-unfold-field | |
1192 Unfold the header under point. | |
1193 | |
1194 @item mail-header-field-value | |
1195 @findex mail-header-field-value | |
1196 Return the value of the field under point. | |
1197 | |
1198 @item mail-encode-encoded-word-region | |
1199 @findex mail-encode-encoded-word-region | |
1200 Encode the non-@acronym{ASCII} words in the region. For instance, | |
85712
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
1201 @samp{Na@"{@dotless{i}}ve} is encoded as @samp{=?iso-8859-1?q?Na=EFve?=}. |
84292 | 1202 |
1203 @item mail-encode-encoded-word-buffer | |
1204 @findex mail-encode-encoded-word-buffer | |
1205 Encode the non-@acronym{ASCII} words in the current buffer. This function is | |
1206 meant to be called narrowed to the headers of a message. | |
1207 | |
1208 @item mail-encode-encoded-word-string | |
1209 @findex mail-encode-encoded-word-string | |
1210 Encode the words that need encoding in a string, and return the result. | |
1211 | |
1212 @example | |
1213 (mail-encode-encoded-word-string | |
85712
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
1214 "This is na@"{@dotless{i}}ve, baby") |
84292 | 1215 @result{} "This is =?iso-8859-1?q?na=EFve,?= baby" |
1216 @end example | |
1217 | |
1218 @item mail-decode-encoded-word-region | |
1219 @findex mail-decode-encoded-word-region | |
1220 Decode the encoded words in the region. | |
1221 | |
1222 @item mail-decode-encoded-word-string | |
1223 @findex mail-decode-encoded-word-string | |
1224 Decode the encoded words in the string and return the result. | |
1225 | |
1226 @example | |
1227 (mail-decode-encoded-word-string | |
1228 "This is =?iso-8859-1?q?na=EFve,?= baby") | |
85712
a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Miles Bader <miles@gnu.org>
parents:
84329
diff
changeset
|
1229 @result{} "This is na@"{@dotless{i}}ve, baby" |
84292 | 1230 @end example |
1231 | |
1232 @end table | |
1233 | |
1234 Currently, @code{mail-parse} is an abstraction over @code{ietf-drums}, | |
1235 @code{rfc2047}, @code{rfc2045} and @code{rfc2231}. These are documented | |
1236 in the subsequent sections. | |
1237 | |
1238 | |
1239 | |
1240 @node Basic Functions | |
1241 @chapter Basic Functions | |
1242 | |
1243 This chapter describes the basic, ground-level functions for parsing and | |
1244 handling. Covered here is parsing @code{From} lines, removing comments | |
1245 from header lines, decoding encoded words, parsing date headers and so | |
1246 on. High-level functionality is dealt with in the first chapter | |
1247 (@pxref{Decoding and Viewing}). | |
1248 | |
1249 @menu | |
1250 * rfc2045:: Encoding @code{Content-Type} headers. | |
1251 * rfc2231:: Parsing @code{Content-Type} headers. | |
1252 * ietf-drums:: Handling mail headers defined by RFC822bis. | |
1253 * rfc2047:: En/decoding encoded words in headers. | |
1254 * time-date:: Functions for parsing dates and manipulating time. | |
1255 * qp:: Quoted-Printable en/decoding. | |
1256 * base64:: Base64 en/decoding. | |
1257 * binhex:: Binhex decoding. | |
1258 * uudecode:: Uuencode decoding. | |
1259 * yenc:: Yenc decoding. | |
1260 * rfc1843:: Decoding HZ-encoded text. | |
1261 * mailcap:: How parts are displayed is specified by the @file{.mailcap} file | |
1262 @end menu | |
1263 | |
1264 | |
1265 @node rfc2045 | |
1266 @section rfc2045 | |
1267 | |
1268 RFC2045 is the ``main'' @acronym{MIME} document, and as such, one would | |
1269 imagine that there would be a lot to implement. But there isn't, since | |
1270 most of the implementation details are delegated to the subsequent | |
1271 RFCs. | |
1272 | |
1273 So @file{rfc2045.el} has only a single function: | |
1274 | |
1275 @table @code | |
1276 @item rfc2045-encode-string | |
1277 @findex rfc2045-encode-string | |
1278 Takes a parameter and a value and returns a @samp{PARAM=VALUE} string. | |
1279 @var{value} will be quoted if there are non-safe characters in it. | |
1280 @end table | |
1281 | |
1282 | |
1283 @node rfc2231 | |
1284 @section rfc2231 | |
1285 | |
1286 RFC2231 defines a syntax for the @code{Content-Type} and | |
1287 @code{Content-Disposition} headers. Its snappy name is @dfn{MIME | |
1288 Parameter Value and Encoded Word Extensions: Character Sets, Languages, | |
1289 and Continuations}. | |
1290 | |
1291 In short, these headers look something like this: | |
1292 | |
1293 @example | |
1294 Content-Type: application/x-stuff; | |
1295 title*0*=us-ascii'en'This%20is%20even%20more%20; | |
1296 title*1*=%2A%2A%2Afun%2A%2A%2A%20; | |
1297 title*2="isn't it!" | |
1298 @end example | |
1299 | |
1300 They usually aren't this bad, though. | |
1301 | |
1302 The following functions are defined by this library: | |
1303 | |
1304 @table @code | |
1305 @item rfc2231-parse-string | |
1306 @findex rfc2231-parse-string | |
1307 Parse a @code{Content-Type} header and return a list describing its | |
1308 elements. | |
1309 | |
1310 @example | |
1311 (rfc2231-parse-string | |
1312 "application/x-stuff; | |
1313 title*0*=us-ascii'en'This%20is%20even%20more%20; | |
1314 title*1*=%2A%2A%2Afun%2A%2A%2A%20; | |
1315 title*2=\"isn't it!\"") | |
1316 @result{} ("application/x-stuff" | |
1317 (title . "This is even more ***fun*** isn't it!")) | |
1318 @end example | |
1319 | |
1320 @item rfc2231-get-value | |
1321 @findex rfc2231-get-value | |
1322 Takes one of the lists on the format above and returns | |
1323 the value of the specified attribute. | |
1324 | |
1325 @item rfc2231-encode-string | |
1326 @findex rfc2231-encode-string | |
1327 Encode a parameter in headers likes @code{Content-Type} and | |
1328 @code{Content-Disposition}. | |
1329 | |
1330 @end table | |
1331 | |
1332 | |
1333 @node ietf-drums | |
1334 @section ietf-drums | |
1335 | |
1336 @dfn{drums} is an IETF working group that is working on the replacement | |
1337 for RFC822. | |
1338 | |
1339 The functions provided by this library include: | |
1340 | |
1341 @table @code | |
1342 @item ietf-drums-remove-comments | |
1343 @findex ietf-drums-remove-comments | |
1344 Remove the comments from the argument and return the results. | |
1345 | |
1346 @item ietf-drums-remove-whitespace | |
1347 @findex ietf-drums-remove-whitespace | |
1348 Remove linear white space from the string and return the results. | |
1349 Spaces inside quoted strings and comments are left untouched. | |
1350 | |
1351 @item ietf-drums-get-comment | |
1352 @findex ietf-drums-get-comment | |
1353 Return the last most comment from the string. | |
1354 | |
1355 @item ietf-drums-parse-address | |
1356 @findex ietf-drums-parse-address | |
1357 Parse an address string and return a list that contains the mailbox and | |
1358 the plain text name. | |
1359 | |
1360 @item ietf-drums-parse-addresses | |
1361 @findex ietf-drums-parse-addresses | |
1362 Parse a string that contains any number of comma-separated addresses and | |
1363 return a list that contains mailbox/plain text pairs. | |
1364 | |
1365 @item ietf-drums-parse-date | |
1366 @findex ietf-drums-parse-date | |
1367 Parse a date string and return an Emacs time structure. | |
1368 | |
1369 @item ietf-drums-narrow-to-header | |
1370 @findex ietf-drums-narrow-to-header | |
1371 Narrow the buffer to the header section of the current buffer. | |
1372 | |
1373 @end table | |
1374 | |
1375 | |
1376 @node rfc2047 | |
1377 @section rfc2047 | |
1378 | |
1379 RFC2047 (Message Header Extensions for Non-@acronym{ASCII} Text) specifies how | |
1380 non-@acronym{ASCII} text in headers are to be encoded. This is actually rather | |
1381 complicated, so a number of variables are necessary to tweak what this | |
1382 library does. | |
1383 | |
1384 The following variables are tweakable: | |
1385 | |
1386 @table @code | |
1387 @item rfc2047-header-encoding-alist | |
1388 @vindex rfc2047-header-encoding-alist | |
1389 This is an alist of header / encoding-type pairs. Its main purpose is | |
1390 to prevent encoding of certain headers. | |
1391 | |
1392 The keys can either be header regexps, or @code{t}. | |
1393 | |
1394 The values can be @code{nil}, in which case the header(s) in question | |
1395 won't be encoded, @code{mime}, which means that they will be encoded, or | |
1396 @code{address-mime}, which means the header(s) will be encoded carefully | |
1397 assuming they contain addresses. | |
1398 | |
1399 @item rfc2047-charset-encoding-alist | |
1400 @vindex rfc2047-charset-encoding-alist | |
1401 RFC2047 specifies two forms of encoding---@code{Q} (a | |
1402 Quoted-Printable-like encoding) and @code{B} (base64). This alist | |
1403 specifies which charset should use which encoding. | |
1404 | |
1405 @item rfc2047-encode-function-alist | |
1406 @vindex rfc2047-encode-function-alist | |
1407 This is an alist of encoding / function pairs. The encodings are | |
1408 @code{Q}, @code{B} and @code{nil}. | |
1409 | |
1410 @item rfc2047-encoded-word-regexp | |
1411 @vindex rfc2047-encoded-word-regexp | |
1412 When decoding words, this library looks for matches to this regexp. | |
1413 | |
87097 | 1414 @item rfc2047-encoded-word-regexp-loose |
1415 @vindex rfc2047-encoded-word-regexp-loose | |
1416 This is a version from which the regexp for the Q encoding pattern of | |
1417 @code{rfc2047-encoded-word-regexp} is made loose. | |
1418 | |
84292 | 1419 @item rfc2047-encode-encoded-words |
1420 @vindex rfc2047-encode-encoded-words | |
1421 The boolean variable specifies whether encoded words | |
87097 | 1422 (e.g. @samp{=?us-ascii?q?hello?=}) should be encoded again. |
1423 @code{rfc2047-encoded-word-regexp} is used to look for such words. | |
1424 | |
1425 @item rfc2047-allow-irregular-q-encoded-words | |
1426 @vindex rfc2047-allow-irregular-q-encoded-words | |
1427 The boolean variable specifies whether irregular Q encoded words | |
1428 (e.g. @samp{=?us-ascii?q?hello??=}) should be decoded. If it is | |
1429 non-@code{nil}, @code{rfc2047-encoded-word-regexp-loose} is used instead | |
1430 of @code{rfc2047-encoded-word-regexp} to look for encoded words. | |
84292 | 1431 |
1432 @end table | |
1433 | |
1434 Those were the variables, and these are this functions: | |
1435 | |
1436 @table @code | |
1437 @item rfc2047-narrow-to-field | |
1438 @findex rfc2047-narrow-to-field | |
1439 Narrow the buffer to the header on the current line. | |
1440 | |
1441 @item rfc2047-encode-message-header | |
1442 @findex rfc2047-encode-message-header | |
1443 Should be called narrowed to the header of a message. Encodes according | |
1444 to @code{rfc2047-header-encoding-alist}. | |
1445 | |
1446 @item rfc2047-encode-region | |
1447 @findex rfc2047-encode-region | |
1448 Encodes all encodable words in the region specified. | |
1449 | |
1450 @item rfc2047-encode-string | |
1451 @findex rfc2047-encode-string | |
1452 Encode a string and return the results. | |
1453 | |
1454 @item rfc2047-decode-region | |
1455 @findex rfc2047-decode-region | |
1456 Decode the encoded words in the region. | |
1457 | |
1458 @item rfc2047-decode-string | |
1459 @findex rfc2047-decode-string | |
1460 Decode a string and return the results. | |
1461 | |
1462 @item rfc2047-encode-parameter | |
1463 @findex rfc2047-encode-parameter | |
1464 Encode a parameter in the RFC2047-like style. This is a replacement for | |
1465 the @code{rfc2231-encode-string} function. @xref{rfc2231}. | |
1466 | |
1467 When attaching files as @acronym{MIME} parts, we should use the RFC2231 | |
1468 encoding to specify the file names containing non-@acronym{ASCII} | |
1469 characters. However, many mail softwares don't support it in practice | |
1470 and recipients won't be able to extract files with correct names. | |
1471 Instead, the RFC2047-like encoding is acceptable generally. This | |
1472 function provides the very RFC2047-like encoding, resigning to such a | |
1473 regrettable trend. To use it, put the following line in your | |
1474 @file{~/.gnus.el} file: | |
1475 | |
1476 @lisp | |
1477 (defalias 'mail-header-encode-parameter 'rfc2047-encode-parameter) | |
1478 @end lisp | |
1479 | |
1480 @end table | |
1481 | |
1482 | |
1483 @node time-date | |
1484 @section time-date | |
1485 | |
1486 While not really a part of the @acronym{MIME} library, it is convenient to | |
1487 document this library here. It deals with parsing @code{Date} headers | |
1488 and manipulating time. (Not by using tesseracts, though, I'm sorry to | |
1489 say.) | |
1490 | |
1491 These functions convert between five formats: A date string, an Emacs | |
1492 time structure, a decoded time list, a second number, and a day number. | |
1493 | |
1494 Here's a bunch of time/date/second/day examples: | |
1495 | |
1496 @example | |
1497 (parse-time-string "Sat Sep 12 12:21:54 1998 +0200") | |
1498 @result{} (54 21 12 12 9 1998 6 nil 7200) | |
1499 | |
1500 (date-to-time "Sat Sep 12 12:21:54 1998 +0200") | |
1501 @result{} (13818 19266) | |
1502 | |
1503 (time-to-seconds '(13818 19266)) | |
1504 @result{} 905595714.0 | |
1505 | |
1506 (seconds-to-time 905595714.0) | |
1507 @result{} (13818 19266 0) | |
1508 | |
1509 (time-to-days '(13818 19266)) | |
1510 @result{} 729644 | |
1511 | |
1512 (days-to-time 729644) | |
1513 @result{} (961933 65536) | |
1514 | |
1515 (time-since '(13818 19266)) | |
1516 @result{} (0 430) | |
1517 | |
1518 (time-less-p '(13818 19266) '(13818 19145)) | |
1519 @result{} nil | |
1520 | |
1521 (subtract-time '(13818 19266) '(13818 19145)) | |
1522 @result{} (0 121) | |
1523 | |
1524 (days-between "Sat Sep 12 12:21:54 1998 +0200" | |
1525 "Sat Sep 07 12:21:54 1998 +0200") | |
1526 @result{} 5 | |
1527 | |
1528 (date-leap-year-p 2000) | |
1529 @result{} t | |
1530 | |
1531 (time-to-day-in-year '(13818 19266)) | |
1532 @result{} 255 | |
1533 | |
1534 (time-to-number-of-days | |
1535 (time-since | |
1536 (date-to-time "Mon, 01 Jan 2001 02:22:26 GMT"))) | |
1537 @result{} 4.146122685185185 | |
1538 @end example | |
1539 | |
1540 And finally, we have @code{safe-date-to-time}, which does the same as | |
1541 @code{date-to-time}, but returns a zero time if the date is | |
1542 syntactically malformed. | |
1543 | |
1544 The five data representations used are the following: | |
1545 | |
1546 @table @var | |
1547 @item date | |
1548 An RFC822 (or similar) date string. For instance: @code{"Sat Sep 12 | |
1549 12:21:54 1998 +0200"}. | |
1550 | |
1551 @item time | |
1552 An internal Emacs time. For instance: @code{(13818 26466)}. | |
1553 | |
1554 @item seconds | |
1555 A floating point representation of the internal Emacs time. For | |
1556 instance: @code{905595714.0}. | |
1557 | |
1558 @item days | |
1559 An integer number representing the number of days since 00000101. For | |
1560 instance: @code{729644}. | |
1561 | |
1562 @item decoded time | |
1563 A list of decoded time. For instance: @code{(54 21 12 12 9 1998 6 t | |
1564 7200)}. | |
1565 @end table | |
1566 | |
1567 All the examples above represent the same moment. | |
1568 | |
1569 These are the functions available: | |
1570 | |
1571 @table @code | |
1572 @item date-to-time | |
1573 Take a date and return a time. | |
1574 | |
1575 @item time-to-seconds | |
1576 Take a time and return seconds. | |
1577 | |
1578 @item seconds-to-time | |
1579 Take seconds and return a time. | |
1580 | |
1581 @item time-to-days | |
1582 Take a time and return days. | |
1583 | |
1584 @item days-to-time | |
1585 Take days and return a time. | |
1586 | |
1587 @item date-to-day | |
1588 Take a date and return days. | |
1589 | |
1590 @item time-to-number-of-days | |
1591 Take a time and return the number of days that represents. | |
1592 | |
1593 @item safe-date-to-time | |
1594 Take a date and return a time. If the date is not syntactically valid, | |
1595 return a ``zero'' time. | |
1596 | |
1597 @item time-less-p | |
1598 Take two times and say whether the first time is less (i. e., earlier) | |
1599 than the second time. | |
1600 | |
1601 @item time-since | |
1602 Take a time and return a time saying how long it was since that time. | |
1603 | |
1604 @item subtract-time | |
1605 Take two times and subtract the second from the first. I. e., return | |
1606 the time between the two times. | |
1607 | |
1608 @item days-between | |
1609 Take two days and return the number of days between those two days. | |
1610 | |
1611 @item date-leap-year-p | |
1612 Take a year number and say whether it's a leap year. | |
1613 | |
1614 @item time-to-day-in-year | |
1615 Take a time and return the day number within the year that the time is | |
1616 in. | |
1617 | |
1618 @end table | |
1619 | |
1620 | |
1621 @node qp | |
1622 @section qp | |
1623 | |
1624 This library deals with decoding and encoding Quoted-Printable text. | |
1625 | |
1626 Very briefly explained, qp encoding means translating all 8-bit | |
1627 characters (and lots of control characters) into things that look like | |
1628 @samp{=EF}; that is, an equal sign followed by the byte encoded as a hex | |
1629 string. | |
1630 | |
1631 The following functions are defined by the library: | |
1632 | |
1633 @table @code | |
1634 @item quoted-printable-decode-region | |
1635 @findex quoted-printable-decode-region | |
1636 QP-decode all the encoded text in the specified region. | |
1637 | |
1638 @item quoted-printable-decode-string | |
1639 @findex quoted-printable-decode-string | |
1640 Decode the QP-encoded text in a string and return the results. | |
1641 | |
1642 @item quoted-printable-encode-region | |
1643 @findex quoted-printable-encode-region | |
1644 QP-encode all the encodable characters in the specified region. The third | |
1645 optional parameter @var{fold} specifies whether to fold long lines. | |
1646 (Long here means 72.) | |
1647 | |
1648 @item quoted-printable-encode-string | |
1649 @findex quoted-printable-encode-string | |
1650 QP-encode all the encodable characters in a string and return the | |
1651 results. | |
1652 | |
1653 @end table | |
1654 | |
1655 | |
1656 @node base64 | |
1657 @section base64 | |
1658 @cindex base64 | |
1659 | |
1660 Base64 is an encoding that encodes three bytes into four characters, | |
1661 thereby increasing the size by about 33%. The alphabet used for | |
1662 encoding is very resistant to mangling during transit. | |
1663 | |
1664 The following functions are defined by this library: | |
1665 | |
1666 @table @code | |
1667 @item base64-encode-region | |
1668 @findex base64-encode-region | |
1669 base64 encode the selected region. Return the length of the encoded | |
1670 text. Optional third argument @var{no-line-break} means do not break | |
1671 long lines into shorter lines. | |
1672 | |
1673 @item base64-encode-string | |
1674 @findex base64-encode-string | |
1675 base64 encode a string and return the result. | |
1676 | |
1677 @item base64-decode-region | |
1678 @findex base64-decode-region | |
1679 base64 decode the selected region. Return the length of the decoded | |
1680 text. If the region can't be decoded, return @code{nil} and don't | |
1681 modify the buffer. | |
1682 | |
1683 @item base64-decode-string | |
1684 @findex base64-decode-string | |
1685 base64 decode a string and return the result. If the string can't be | |
1686 decoded, @code{nil} is returned. | |
1687 | |
1688 @end table | |
1689 | |
1690 | |
1691 @node binhex | |
1692 @section binhex | |
1693 @cindex binhex | |
1694 @cindex Apple | |
1695 @cindex Macintosh | |
1696 | |
1697 @code{binhex} is an encoding that originated in Macintosh environments. | |
1698 The following function is supplied to deal with these: | |
1699 | |
1700 @table @code | |
1701 @item binhex-decode-region | |
1702 @findex binhex-decode-region | |
1703 Decode the encoded text in the region. If given a third parameter, only | |
1704 decode the @code{binhex} header and return the filename. | |
1705 | |
1706 @end table | |
1707 | |
1708 @node uudecode | |
1709 @section uudecode | |
1710 @cindex uuencode | |
1711 @cindex uudecode | |
1712 | |
1713 @code{uuencode} is probably still the most popular encoding of binaries | |
1714 used on Usenet, although @code{base64} rules the mail world. | |
1715 | |
1716 The following function is supplied by this package: | |
1717 | |
1718 @table @code | |
1719 @item uudecode-decode-region | |
1720 @findex uudecode-decode-region | |
1721 Decode the text in the region. | |
1722 @end table | |
1723 | |
1724 | |
1725 @node yenc | |
1726 @section yenc | |
1727 @cindex yenc | |
1728 | |
1729 @code{yenc} is used for encoding binaries on Usenet. The following | |
1730 function is supplied by this package: | |
1731 | |
1732 @table @code | |
1733 @item yenc-decode-region | |
1734 @findex yenc-decode-region | |
1735 Decode the encoded text in the region. | |
1736 | |
1737 @end table | |
1738 | |
1739 | |
1740 @node rfc1843 | |
1741 @section rfc1843 | |
1742 @cindex rfc1843 | |
1743 @cindex HZ | |
1744 @cindex Chinese | |
1745 | |
1746 RFC1843 deals with mixing Chinese and @acronym{ASCII} characters in messages. In | |
1747 essence, RFC1843 switches between @acronym{ASCII} and Chinese by doing this: | |
1748 | |
1749 @example | |
1750 This sentence is in @acronym{ASCII}. | |
1751 The next sentence is in GB.~@{<:Ky2;S@{#,NpJ)l6HK!#~@}Bye. | |
1752 @end example | |
1753 | |
1754 Simple enough, and widely used in China. | |
1755 | |
1756 The following functions are available to handle this encoding: | |
1757 | |
1758 @table @code | |
1759 @item rfc1843-decode-region | |
1760 Decode HZ-encoded text in the region. | |
1761 | |
1762 @item rfc1843-decode-string | |
1763 Decode a HZ-encoded string and return the result. | |
1764 | |
1765 @end table | |
1766 | |
1767 | |
1768 @node mailcap | |
1769 @section mailcap | |
1770 | |
1771 The @file{~/.mailcap} file is parsed by most @acronym{MIME}-aware message | |
1772 handlers and describes how elements are supposed to be displayed. | |
1773 Here's an example file: | |
1774 | |
1775 @example | |
1776 image/*; gimp -8 %s | |
1777 audio/wav; wavplayer %s | |
1778 application/msword; catdoc %s ; copiousoutput ; nametemplate=%s.doc | |
1779 @end example | |
1780 | |
1781 This says that all image files should be displayed with @code{gimp}, | |
1782 that WAVE audio files should be played by @code{wavplayer}, and that | |
1783 MS-WORD files should be inlined by @code{catdoc}. | |
1784 | |
1785 The @code{mailcap} library parses this file, and provides functions for | |
1786 matching types. | |
1787 | |
1788 @table @code | |
1789 @item mailcap-mime-data | |
1790 @vindex mailcap-mime-data | |
1791 This variable is an alist of alists containing backup viewing rules. | |
1792 | |
1793 @end table | |
1794 | |
1795 Interface functions: | |
1796 | |
1797 @table @code | |
1798 @item mailcap-parse-mailcaps | |
1799 @findex mailcap-parse-mailcaps | |
1800 Parse the @file{~/.mailcap} file. | |
1801 | |
1802 @item mailcap-mime-info | |
1803 Takes a @acronym{MIME} type as its argument and returns the matching viewer. | |
1804 | |
1805 @end table | |
1806 | |
1807 | |
1808 | |
1809 | |
1810 @node Standards | |
1811 @chapter Standards | |
1812 | |
1813 The Emacs @acronym{MIME} library implements handling of various elements | |
1814 according to a (somewhat) large number of RFCs, drafts and standards | |
1815 documents. This chapter lists the relevant ones. They can all be | |
1816 fetched from @uref{http://quimby.gnus.org/notes/}. | |
1817 | |
1818 @table @dfn | |
1819 @item RFC822 | |
1820 @itemx STD11 | |
1821 Standard for the Format of ARPA Internet Text Messages. | |
1822 | |
1823 @item RFC1036 | |
1824 Standard for Interchange of USENET Messages | |
1825 | |
1826 @item RFC2045 | |
1827 Format of Internet Message Bodies | |
1828 | |
1829 @item RFC2046 | |
1830 Media Types | |
1831 | |
1832 @item RFC2047 | |
1833 Message Header Extensions for Non-@acronym{ASCII} Text | |
1834 | |
1835 @item RFC2048 | |
1836 Registration Procedures | |
1837 | |
1838 @item RFC2049 | |
1839 Conformance Criteria and Examples | |
1840 | |
1841 @item RFC2231 | |
1842 @acronym{MIME} Parameter Value and Encoded Word Extensions: Character Sets, | |
1843 Languages, and Continuations | |
1844 | |
1845 @item RFC1843 | |
1846 HZ - A Data Format for Exchanging Files of Arbitrarily Mixed Chinese and | |
1847 @acronym{ASCII} characters | |
1848 | |
1849 @item draft-ietf-drums-msg-fmt-05.txt | |
1850 Draft for the successor of RFC822 | |
1851 | |
1852 @item RFC2112 | |
1853 The @acronym{MIME} Multipart/Related Content-type | |
1854 | |
1855 @item RFC1892 | |
1856 The Multipart/Report Content Type for the Reporting of Mail System | |
1857 Administrative Messages | |
1858 | |
1859 @item RFC2183 | |
1860 Communicating Presentation Information in Internet Messages: The | |
1861 Content-Disposition Header Field | |
1862 | |
1863 @item RFC2646 | |
1864 Documentation of the text/plain format parameter for flowed text. | |
1865 | |
1866 @end table | |
1867 | |
1868 @node GNU Free Documentation License | |
1869 @chapter GNU Free Documentation License | |
1870 @include doclicense.texi | |
1871 | |
1872 @node Index | |
1873 @chapter Index | |
1874 @printindex cp | |
1875 | |
1876 @summarycontents | |
1877 @contents | |
1878 @bye | |
1879 | |
1880 | |
1881 @c Local Variables: | |
1882 @c mode: texinfo | |
1883 @c coding: iso-8859-1 | |
1884 @c End: | |
1885 | |
1886 @ignore | |
1887 arch-tag: c7ef2fd0-a91c-4e10-aa52-c1a2b11b1a8d | |
1888 @end ignore |