From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: gnus sends corrupt attachments
Date: 19 Sep 1999 22:37:56 +0200 [thread overview]
Message-ID: <vafn1uibpsr.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: "Johan Kullstam"'s message of "19 Sep 1999 15:36:37 -0400"
Johan Kullstam <kullstam@ne.mediaone.net> writes:
> in light of the apparent unreliability of quoted-printable, should
> this setup be made the default?
I don't think that QP is unreliable per se. It's just that long lines
are a problem. QP provides a way for dealing with long lines: if a
line ends with `=', a continuation line follows.
Maybe QP encoding should make use of this to restrict maximum line
lengths to 70 characters or so?
But maybe that PDF file was an all-ASCII file. Gnus doesn't do any
encoding when that happens, I think.
kai
--
I like BOTH kinds of music.
next prev parent reply other threads:[~1999-09-19 20:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-19 2:40 kullstam
1999-09-19 8:27 ` Rene H. Larsen
1999-09-19 19:36 ` Johan Kullstam
1999-09-19 20:37 ` Kai Großjohann [this message]
1999-09-19 22:22 ` Johan Kullstam
1999-09-20 10:39 ` Robert Bihlmeyer
1999-09-20 19:49 ` Raja R Harinath
1999-09-22 21:19 ` Shenghuo ZHU
1999-09-25 9:35 ` Lars Magne Ingebrigtsen
1999-09-26 5:52 ` Shenghuo ZHU
1999-09-27 17:40 ` Lars Magne Ingebrigtsen
1999-09-25 9:37 ` 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=vafn1uibpsr.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).