From: Mark Buda <hermit@clark.net>
Subject: Re: MIME error with pgnus 0.96
Date: 07 Sep 1999 09:03:05 -0400 [thread overview]
Message-ID: <87so4qkh6e.fsf@pazuzu.eudaemonia.org> (raw)
In-Reply-To: Mark Buda's message of "04 Sep 1999 23:13:03 -0400"
>>>>> "Mark" == Mark Buda <hermit@clark.net> writes:
Mark> Both quoted-printable and base64 encodings appear to be
Mark> broken in 0.96.
Furthermore, in 0.95 under Xemacs 20.4 on Debian GNU/Linux 2.1, zip
archives (for example) sent as attachments are corrupted. The cause is
that newlines are replaced with carriage returns, or maybe it was the
other way around. Apparently the raw-text coding system set by
nnheader-file-coding-system was resulting in Xemacs thinking it should
use the no-conversion-mac coding system.
(setq nnheader-file-coding-system 'binary)
appears to fix the problem, but it almost certainly isn't the Right
Solution (tm).
--
I get my monkeys for nothing and my chimps for free.
http://www.clark.net/pub/hermit/
next prev parent reply other threads:[~1999-09-07 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-03 20:26 Thomas H. Olsen
1999-09-05 3:13 ` Mark Buda
1999-09-07 13:03 ` Mark Buda [this message]
1999-09-08 22:17 ` Fix for broken QP-encoding bug Shenghuo ZHU
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87so4qkh6e.fsf@pazuzu.eudaemonia.org \
--to=hermit@clark.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).