unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: emacs-devel@gnu.org
Subject: Supercite and mail-citation-hook
Date: Fri, 30 Oct 2009 23:41:46 +0100	[thread overview]
Message-ID: <19179.27562.403821.797322@a1i15.kph.uni-mainz.de> (raw)

I am trying to debug a problem with Supercite's attribution line
when used with the VM mailreader, and I'm not sure which of the two
programs is to blame. Supercite is called by VM in the standard way,
i.e. via mail-citation-hook and function sc-cite-original.

The problem occurs when replying to an e-mail message with a
QP-encoded "From" header, which will have a broken attribution line
like the following:

   >>>>> On Fri, 30 Oct 2009, =?ISO-8859-1?Q?Ulrich_M=FCller?= wrote:

Now the Supercite Info file says in section 10 "Hints to MUA Authors":

| [...] when setting up a reply or forward buffer, your MUA should
| follow these steps:
| 
|   1. Insert the original message, including the mail headers into the
|      reply buffer. At this point you should not modify the raw text in
|      any way, and you should place all the original headers into the
|      body of the reply. [...]

The wording ("not modify the raw text in any way", "original headers")
seems to indicate that the MUA shouldn't do any decoding here.

However, Supercite also doesn't do any QP decoding, which leads to the
above broken attribution line.

So my question is, who should decode the headers? The MUA (then the
documentation of mail-citation-hook in sc.texi should be changed or
clarified), or Supercite (then it's a bug there)?

Ulrich




             reply	other threads:[~2009-10-30 22:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-30 22:41 Ulrich Mueller [this message]
2009-11-02  8:12 ` Supercite and mail-citation-hook Glenn Morris
2009-11-02 14:18 ` Stefan Monnier

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=19179.27562.403821.797322@a1i15.kph.uni-mainz.de \
    --to=ulm@gentoo.org \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).