From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: problem with pdf attachment
Date: 04 Mar 2000 17:41:33 +0100 [thread overview]
Message-ID: <vafputay9fm.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: lconrad@world.std.com's message of "03 Mar 2000 14:32:09 -0500"
lconrad@world.std.com writes:
> When I saved the attachment by right-clicking the button, I got a file
> that pdf viewers didn't recognize. It looked like it was still
> encoded -- all the lines were the same length, and consisted entirely
> of ascii characters.
Can you say `C-u g' on that message and show us the headers of that
MIME part? Maybe the Content-transfer-encoding is wrong?
kai
--
~/.signature: No such file or directory
next prev parent reply other threads:[~2000-03-04 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-03 19:32 lconrad
2000-03-04 16:41 ` Kai Großjohann [this message]
2000-03-04 17:51 ` Laura Conrad
2000-03-04 18:39 ` Kai Großjohann
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=vafputay9fm.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.org \
/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).