For lack of content...

[Michael Welsh Duggan <md5i@cs.cmu.edu>]

There are some posts which I read which contain characters in
non-default coding-systems, which don't include a proper Content-Type
header.  As a result, these messages end up in my buffer as the raw
bytes of the coding method.  There are a couple of possible solutions
that I can think of:

1) A decoding alist of some sort, such as an alist of regexps
   (matching a newsgroup name) to a list of coding-systems.  If the
   visited newsgroup matches that regexp, then it should try to decode
   the body using the mehods in the associated list,m in order.

2) A washing method, for which the user can supply a coding-system
   with which to decode the article.  I actually wrote a prototype of
   such myself, but ran into the problem that decode-coding-region
   trashes text-properties.

If something already exists to cover this, I apologize for not having
found it yet.

-- 
Michael Duggan
(md5i@cs.cmu.edu)

.