All of Gary's posts read:
Content-Type: text/plain; charset="utf-8"
And the digest is sent just as "text/plain" (is the default for email ASCII or ISO-8859-1?).
AFAIK, simply recasting UTF-8 as ASCII should only cause problems for two-byte characters. Anything below 128 ought to be the same in either encoding. So in theory, simply recasting the UTF-8 as ASCII should keep anything in the roman alphabet still readable.
I had assumed that the original post was encoded somehow (since the headers are no longer present in the digest), and mailman was just dropping it into the digest raw. But if the post *is* text/plain (albeit in a different character set), then perhaps mailman is converting something incorrectly when it builds the digest?
I've just changed my digest option for the list from plain-text to MIME - I'll see if that improves matters.
Kelson Vibber www.hyperborea.org
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
