X-Git-Url: http://git.chise.org/gitweb/?p=elisp%2Fsemi.git;a=blobdiff_plain;f=TODO;h=4be8a0e4d5efebb961d84595826224474826e46e;hp=133b8c7addad9ee94c211a6cdcb876a084dee8d9;hb=HEAD;hpb=b6e27f6c416ebe1b8f19acace81ea81d94a6a3c3 diff --git a/TODO b/TODO index 133b8c7..4be8a0e 100644 --- a/TODO +++ b/TODO @@ -1,18 +1,13 @@ -* MIME-View - -** Unify entity display specifications to 'mime-preview-condition - -** Mother entity should modify preview-situation of children +[TODO] +====== -** Better implementation for multipart/alternative - -** Change 'mime-acting-condition to condition-tree format +* MIME-View ** dynamic configuration for 'mime-preview-condition -** mailcap support +** Don't expect raw-buffer -** dynamic configuration for 'mime-acting-condition +** lazy generating of situations from mime-entity information * MIME-Edit @@ -21,4 +16,51 @@ ** Use MIME-Preview like tag and display -** keymap-prefix +** Redesign to use two buffers for one message + + MIME-View is based on "Multiple Representation Space (layer) Model". +In this model, network representation and its presentation are +distinguished. Thus MIME-View uses two buffers for one message, +'mime-raw-buffer (for network representation) and +'mime-preview-buffer. MIME-View manages them based on information of +entities. According to experience of MIME-View, this model is good to +treat complex structured data, such as MIME. + + MIME-Edit was designed to use one buffer for one message. So it is +hard to edit like WYSIWYG style. Format of tag is limited by +translation. Content of forwarded message is unreadable. It is +better to introduce "Multiple Representation Space Model" to resolve +these problems. + +** Check available MIME-charset + + MIME-charset 以外が生成される場合の処理を指定できるようにする。 + + For example: + + (a) translate problematic characters to similar representation + (b) display warning message + (e.g. "`x-ctext' is generated. Do you send it? (yes/no)") + (c) stop sending + +** Don't use buffer-local variables + + Don't use buffer-local variables to control behavior about +translating to network representation, such as 'mime-transfer-level, +'mime-transfer-level-string, +'mime-edit-charset-default-encoding-alist, 'mime-edit-pgp-processing. +Because they have problem with Semi-gnus. + + +* Etc. + +** Write manual + + + +[Known Bugs] +============ + +* MIME-Edit + +** Content-ID is mandatory for message/external-body