From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Is QP bad for binary files?
Date: Thu, 12 Jul 2001 01:00:18 +0200 [thread overview]
Message-ID: <vaf1ynnysu5.fsf@lucy.cs.uni-dortmund.de> (raw)
Suppose I send a binary file as an attachment, and it is encoded in
quoted-printable rather than base64. I'm thinking maybe strange
things might happen to line endings in that file. For if I send it
from a Unix system to a Windows system, \n can become \r\n on the way.
Does this really happen? Can it really happen?
If this really happens, then I think this would be a good reason to
refrain from using QP for binary files. Gnus fairly often uses QP for
PDF files.
kai
--
~/.signature: No such file or directory
next reply other threads:[~2001-07-11 23:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 23:00 Kai Großjohann [this message]
2001-07-12 1:27 ` Daniel Pittman
2001-07-12 1:31 ` ShengHuo ZHU
2001-07-12 1:48 ` Randal L. Schwartz
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=vaf1ynnysu5.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).