all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: emacs-devel@gnu.org
Subject: Re: rfc2047-decode-region
Date: Sat, 31 Dec 2011 16:32:56 +0200	[thread overview]
Message-ID: <83mxa8stev.fsf@gnu.org> (raw)
In-Reply-To: <87obuoewk3.fsf@uwakimon.sk.tsukuba.ac.jp>

> From: "Stephen J. Turnbull" <stephen@xemacs.org>
> Cc: emacs-devel@gnu.org
> Date: Sat, 31 Dec 2011 21:48:44 +0900
> 
> Eli Zaretskii writes:
>  > This function accepts an optional ADDRESS-MIME argument, which is
>  > described in the doc string thusly:
>  > 
>  >   If ADDRESS-MIME is non-nil, strip backslashes which precede characters
>  >   other than `"' and `\' in quoted strings.
>  > 
>  > This gives absolutely no information about when to use this option and
>  > why.
> 
> It's all in RFC 5322.  Doesn't everybody know that by heart? ;-)

I didn't find a place that would explain how to compute 5322 from
2047.

> I would assume that this argument should be non-nil when decoding a
> header field which is parsed into atoms, such as To or From.  Possibly
> this would apply to Message-ID and References as well (in messages
> conforming to RFC 5322 and maybe 2822, but in 822 References and
> In-Reply-To were just unstructured text).

Thanks.  I needed it to decode a region of the "rmail view buffer",
where we display a single message, which includes all the displayed
headers, including From, To, CC, Subject, etc.  So from your
explanations I understand that the ADDRESS-MIME argument can stay nil
in that case, correct?



  reply	other threads:[~2011-12-31 14:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-31 10:11 rfc2047-decode-region Eli Zaretskii
2011-12-31 12:48 ` rfc2047-decode-region Stephen J. Turnbull
2011-12-31 14:32   ` Eli Zaretskii [this message]
2012-01-02 13:18     ` rfc2047-decode-region Stephen J. Turnbull
2012-01-02 17:33       ` rfc2047-decode-region Eli Zaretskii

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=83mxa8stev.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stephen@xemacs.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.