|Currently nmh doesn't have any method to allow you to specify the
|Content-Transfer-Encoding.
There is a patch in the MH patch archive to do this for the old mhn
that I did, but I was never terribly happy with how it worked (you
can specify the c-t-e on each mhn directive, but there was not a
general way to say, for instance, `use 8bit over q-p').
I've been reorganizing the code that determines the transfer
encoding in mhbuild (formerly mhn -build). I've been doing this
with the idea of allowing more flexible determination of transfer
encodings.
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).
What form should this take? Do people want the ability to specify
the encoding inside a mhbuild directive like this?
#<text/plain; charset=iso-8859-5 {8bit}
And when I add the ability to encode header fields (via RFC-2047)
in outgoing mail, this will require more configurability.
As you can see, sorting all this out will take some time.
--
Richard Coleman
coleman(_at_)math(_dot_)gatech(_dot_)edu