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