From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: v.98 pdf decoding broken?
Date: 03 Dec 1999 00:15:22 +0100 [thread overview]
Message-ID: <m3so1lc4tx.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <uli12n1rtwtb9.fsf@erdw.ethz.ch>
uliw@erdw.ethz.ch writes:
> nope. However, if I _name_ the attachment my_file.zip instead of
> my_file.pdf, all is fine. Does gnus behave diffrently depending on the
> ending? If not, it seems to be an os-depending thing, related to the
> fact how text/binary files are handled.
Hm. Could you attach a PDF file and mail it to me?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1999-12-02 23:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-24 14:46 uliw
1999-12-01 20:42 ` Lars Magne Ingebrigtsen
1999-12-02 5:09 ` Johan Kullstam
1999-12-02 5:18 ` Lars Magne Ingebrigtsen
1999-12-02 9:30 ` uliw
1999-12-02 10:06 ` uliw
1999-12-02 23:15 ` Lars Magne Ingebrigtsen [this message]
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=m3so1lc4tx.fsf@quimbies.gnus.org \
--to=larsi@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).