From: Matt Armstrong <matta@geoworks.com>
Subject: Saving binary attachments no work under WinNT
Date: 14 Sep 1998 16:22:58 -700 [thread overview]
Message-ID: <uvhmquvn1.fsf@ultraman.geoworks.com> (raw)
I'm running rgnus-0.31 under Emacs 23.1 under WinNT.
I get a MS Word document delivered to me as a MIME attachment, base64
encoded.
I cursor down to the document and hit <RET> over the document. An
*mm* buffer pops up with a bunch of binary garbage, I save it. It
isn't a valid MS Word document.
The problem here is that the *mm* buffer's coding system is
undecided-dos (WinNT, remember). If I manually change the coding
system in *mm* to "no-conversion," it saves fine.
Is this a bug, or do I have to configure pgnus so application/msword
is treated as a binary format?
Also, if I mouse-2 click on the attachment, I get prompted for a
filename just as if I hit <ret>. But, the Word doc gets saved in
base64 -- not decoded. Is this the expected behavior? How can I make
it decode before saving?
--
matta
next reply other threads:[~1998-09-14 23:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-14 23:22 Matt Armstrong [this message]
1998-09-15 13:38 ` Ed
[not found] ` <199809151341.GAA26600@ns.geoworks.com>
1998-09-15 18:02 ` Matt Armstrong
1998-09-16 9:20 ` Lars Magne Ingebrigtsen
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=uvhmquvn1.fsf@ultraman.geoworks.com \
--to=matta@geoworks.com \
/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).