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