From: Dave Love <d.love@dl.ac.uk>
Subject: Re: something decodes my headers...
Date: Tue, 17 Jun 2003 23:17:35 +0100 [thread overview]
Message-ID: <rzqbrww2vsw.fsf@albion.dl.ac.uk> (raw)
In-Reply-To: <iluvfvalbz1.fsf@latte.josefsson.org>
jas@extundo.com (Simon Josefsson) writes:
> What does "works" mean?
It doesn't fail in the way that's being complained about.
> I'm not aware of any standards that define
> how non-ASCII email address phrases should work (RFC (2)822 even
> forbid them) except MIME, so any implementation claiming to support it
> if it doesn't use MIME is ad-hoc at best.
It's obviously intended for use with decoded addresses, which is how
it's being used.
> In that case, I wish the way it works was documented.
You'll need to make a bug report if you're not happy. I haven't
actually touched it, though I'd have guessed I made the relevant
change.
> It is not clear to me how to go from the RFC 822 address phrase to
> multilingual names, if you are not using MIME.
It's clear you can't pick apart a single MIME encoded word in the way
mail-extr tries to. It must be decoded, and the exact (2)822 grammar
is irrelevant.
> Of course, mail-extr doesn't
> understand the RFC 822 BNF at all, so it is not easy to realize that
> whatever mail-extr implement is according to any standard derived from
> the BNF.
I don't understand that. The BNF is largely irrelevant for extracting
personal names from addresses as far as I can tell.
prev parent reply other threads:[~2003-06-17 22:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 19:01 Jan Rychter
2003-06-05 21:53 ` Simon Josefsson
2003-06-11 0:20 ` Jan Rychter
2003-06-11 4:38 ` Simon Josefsson
2003-06-11 4:53 ` Jan Rychter
2003-06-11 10:13 ` Simon Josefsson
2003-06-11 18:38 ` Jan Rychter
2003-06-12 22:30 ` Dave Love
2003-06-12 22:38 ` Dave Love
2003-06-13 6:37 ` Simon Josefsson
2003-06-16 0:12 ` Jan Rychter
2003-06-17 22:26 ` Dave Love
2003-06-18 8:30 ` Jan Rychter
2003-06-17 22:17 ` Dave Love [this message]
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=rzqbrww2vsw.fsf@albion.dl.ac.uk \
--to=d.love@dl.ac.uk \
/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).