6 ** dynamic configuration for 'mime-preview-condition
11 ** WYSIWYG editing support
13 ** Use MIME-Preview like tag and display
15 ** Redesign to use two buffers for one message
17 MIME-View is based on "Multiple Representation Space (layer) Model".
18 In this model, network representation and its presentation are
19 distinguished. Thus MIME-View uses two buffers for one message,
20 'mime-raw-buffer (for network representation) and
21 'mime-preview-buffer. MIME-View manages them based on information of
22 entities. According to experience of MIME-View, this model is good to
23 treat complex structured data, such as MIME.
25 MIME-Edit was designed to use one buffer for one message. So it is
26 hard to edit like WYSIWYG style. Format of tag is limited by
27 translation. Content of forwarded message is unreadable. It is
28 better to introduce "Multiple Representation Space Model" to resolve
31 ** Check available MIME-charset
33 MIME-charset
\e$B0J30$,@8@.$5$l$k>l9g$N=hM}$r;XDj$G$-$k$h$&$K$9$k!#
\e(B
37 (a) translate problematic characters to similar representation
38 (b) display warning message
39 (e.g. "`x-ctext' is generated. Do you send it? (yes/no)")
42 ** Don't use buffer-local variables
44 Don't use buffer-local variables to control behavior about
45 translating to network representation, such as 'mime-transfer-level,
46 'mime-transfer-level-string,
47 'mime-edit-charset-default-encoding-alist, 'mime-edit-pgp-processing.
48 Because they have problem with Semi-gnus.
62 ** Content-ID is mandatory for message/external-body