From: Barry Margolin <barmar@alum.mit.edu>
Subject: Re: rmail and quoted-printable
Date: Sat, 02 Sep 2006 21:41:09 -0400 [thread overview]
Message-ID: <barmar-B87A90.21410902092006@comcast.dca.giganews.com> (raw)
In-Reply-To: mailman.6172.1157231314.9609.help-gnu-emacs@gnu.org
In article <mailman.6172.1157231314.9609.help-gnu-emacs@gnu.org>,
Eli Zaretskii <eliz@gnu.org> wrote:
> > CC: help-gnu-emacs@gnu.org
> > Jabber-ID: zedek@im.lolica.org
> > From: Xavier Maillard <zedek@gnu.org>
> > Date: Sat, 02 Sep 2006 19:36:41 +0200
> >
> > ``Just work'' in what sense? Can you describe the simplest set of
> > features, from the user point of view, that would satisfy you?
> >
> > The best I can think at, is as simple as automatically decoding just
> > by displaying an rmail message.
>
> You seem to assume that the quoted-printable part is text. But it
> sometimes isn't; and then in some cases that part is base64-encoded,
> not quoted-printable encoded.
I've never seen quoted-printable that wasn't text. The point of
quoted-printable is that it's used for plain text, to just encode
occasional special characters, such as soft line breaks, diacriticals,
fancy quotes, etc.
It's possible that an attachment is base64-encoded, but he's not asking
about that, just about quoted printable.
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***
next prev parent reply other threads:[~2006-09-03 1:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 22:37 rmail and quoted-printable Xavier Maillard
2006-09-01 14:40 ` Kevin Rodgers
[not found] ` <mailman.6139.1157121909.9609.help-gnu-emacs@gnu.org>
2006-09-01 22:05 ` maillaxa
2006-09-02 1:57 ` Barry Margolin
2006-09-02 9:48 ` Eli Zaretskii
2006-09-02 15:58 ` Xavier Maillard
2006-09-02 16:48 ` Eli Zaretskii
2006-09-02 17:36 ` Xavier Maillard
2006-09-02 21:08 ` Eli Zaretskii
2006-09-02 21:50 ` Xavier Maillard
[not found] ` <mailman.6172.1157231314.9609.help-gnu-emacs@gnu.org>
2006-09-03 1:41 ` Barry Margolin [this message]
2006-09-03 21:39 ` Xavier Maillard
2006-09-03 22:37 ` Jesper Harder
[not found] ` <mailman.6223.1157323058.9609.help-gnu-emacs@gnu.org>
2006-09-07 16:04 ` Miles Bader
2006-09-07 20:23 ` Eli Zaretskii
2006-09-05 16:32 ` Kaloian Doganov
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=barmar-B87A90.21410902092006@comcast.dca.giganews.com \
--to=barmar@alum.mit.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).