From: Michael.Cook@cisco.com
Subject: mm-qp-or-base64
Date: Wed, 26 Sep 2001 12:51:32 -0400 [thread overview]
Message-ID: <g088zf1zyi3.fsf@zzz.cisco.com> (raw)
pdf files often seem to look like plain text files because they tend
to contain a lot of "text" characters, especially at the beginning
of the file. but pdf files also usually contain a lot of "binary"
characters. in other words, mm-qp-or-base64 tends to return
'quoted-printable for pdf files, but it should probably return
'base64. should we make mm-qp-or-base64 smarter? maybe use
something like
(goto-char (point-min))
(if (looking-at "%PDF-")
'base64
...)
suitably generalized, of course. maybe with:
(defvar mm-content-transfer-encoding-smart-defaults
'(("\\`%PDF-" base64))
"Alist of regexps to match against the beginning of a buffer
to determine which encoding to use. If none of these regexps
matches, then a heuristic is applied to choose between
quoted-printable and base64.")
or maybe this idea could be folded into
mm-content-transfer-encoding-defaults somehow.
m.
next reply other threads:[~2001-09-26 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 16:51 Michael.Cook [this message]
2001-09-26 20:02 ` mm-qp-or-base64 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=g088zf1zyi3.fsf@zzz.cisco.com \
--to=michael.cook@cisco.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).