In replied-to message John R MacMillan writes
|But the real question is what flexibility do people really need?
|Just the abilities to say "always use 8bit"? Or the ability to
|give a default encoding for every content type? Or both (which
|is complicated).
Being able to say something like {8bit} on the directive is helpful
(which is why I did the original patch that way), but it's not
really enough.
In my current case, for instance, my MTA can do ESMTP 8bit, and
can convert to q-p as it needs to for exchanging with older MTAs
(modulo the usual sendmail bugs), so I'd like to be able to say
in my mts.conf that my MTA can take and handle 8bit. With that,
MH would never encode q-p unless I asked (either with -ebcdicsafe
or a {} directive).
I agree with this! Just a general rule to be overwritten by an
option and the possibility to say {8bit} in the message.
Of course, there's lots more one could do (generalize -ebcdicsafe
to list the unsafe characters, or maximum line length, provide
for specifying {} directives per content-type in the $MHN file,
etc.) I think just having {} and a mts.conf variable would be
enough, at least for me.
^^^^^^^^^^^^^^^^^^^^^^^^^
End of replied-to message
...
Regards
Stefan
Stefan Becker
| Email: Stefan_Becker(_at_)hp(_dot_)com
C S D E | Phone: {49|0}-7031-14-3799 | 778-3799
| Fax: {49|0}-7031-14-1153
Test & Software Load | WWW: http://hpcsmns8.bbn.hp.com/~stbe (HP only)