X-Git-Url: https://git.deb.at/w?p=pkg%2Ft-prot.git;a=blobdiff_plain;f=TODO;h=6174205cc0f104de3ea0e1d58269ae5384cc6416;hp=9422bb322cdb768a7ad4e7f69371a981e17653ba;hb=e1deb8f8c6b5f5c1cc5c2281166a51a4b9554ca8;hpb=67cb7c5d2dc193713d0a7d9d44070e5c7471ab8a diff --git a/TODO b/TODO index 9422bb3..6174205 100644 --- a/TODO +++ b/TODO @@ -16,18 +16,24 @@ Known Bugs (more severe ones come first) Wishlist -------- - * Better heuristics for M$ style TOFU. The actual algorithm still -is just too greedy (actually, it simply snips most things down to the -signature). User ignorance makes it tricky to detect gold inside the -crap, though. As always, comments and ideas are welcome. - - * New option to block-align lines of text. Should be especially -pleasing when used together with -k (you could re-align a whole para- -graph using these both). + * Support for gpg2. Please send an email to +if you want this feature in vanilla t-prot. + * Now Quoted-printable and the lot in Subject, To and From header +fields is done by --sani, but UTF-8 is still out there. Rejected issues --------------- + * Improving heuristics for M$ style TOFU is way tricky. In the end, +it's just plain guessing what is newly added text and what is quoted, +in particular with most "modern" MUAs disgustingly trying to invent some +new way of (not machine-parseable, of course) quoting that makes guessing +even harder. + + * Block-align lines of text. Same problem as above: It's really hard +guesswork to figure out what is intentional formatting and what is just +user laziness. Patches solving this issue are greatly welcome, of course. + * If you set mutt's display_filter to "tee foo" when viewing a pgp signed message and attach the resulting file to a pgp signed message, the result is confusion when displaying this new message with t-prot. @@ -53,7 +59,7 @@ article currently displayed (just on those processed later on). It would be nice to have an alternative taking effect immediately. -Please remember that t-prot.sl is an *example* script (for you to get +Please keep in mind that t-prot.sl is an *example* script (for you to get an idea on how to integrate t-prot into other software), so these are really low priority. However, patches in unified diff format are always -welcome. ;) +welcome.