From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Other IDN-fixes
Date: Tue, 27 Sep 2005 17:14:56 +0200 [thread overview]
Message-ID: <iluu0g6lez3.fsf@latte.josefsson.org> (raw)
In-Reply-To: <87slvqvb2i.fsf@arnested.dk> (Arne =?iso-8859-1?Q?J=F8rgensen?= =?iso-8859-1?Q?'s?= message of "Tue, 27 Sep 2005 16:29:09 +0200")
Arne Jørgensen <arne@arnested.dk> writes:
> The patch doesn't solve your problem as far as I can tell.
>
> It fixes the following things though:
>
> 1. Decoding articles with more than one IDN-address in the same field
> (i.e. "To: adam@sjøgren.dk, arne@jøssen.dk")
>
> Currently only the last address is decoded, but the patch fixes a
> regexp in `article-decode-idna-rhs' so all are handled.
>
> 2. Also encode and decode address in Reply-To:, Mail-Reply-To: and
> Mail-Followup-To:.
>
> 3. When `message-use-idna is 'ask you will be asked whether to replace
> the same idna domain once for every time it is in a header (i.e.
> twice about jøssen.dk for "To: arne@jøssen.dk, palle@jøssen.dk")
> but the replacement is done the first time for both/all.
>
> The patch only asks once for the same idna domain in each header,
> but will still ask twice about jøssen.dk if it is present in both
> say To: and Reply-To: (that would require a bigger rewrite of the
> idna handling).
Looks good, I installed it, thanks!
next prev parent reply other threads:[~2005-09-27 15:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 13:23 Hashcash-generation/check for IDN-domains Adam Sjøgren
2005-09-27 14:29 ` Other IDN-fixes (was: Hashcash-generation/check for IDN-domains) Arne Jørgensen
2005-09-27 15:14 ` Simon Josefsson [this message]
2005-09-27 15:09 ` Hashcash-generation/check for IDN-domains Simon Josefsson
2005-09-27 15:31 ` Arne Jørgensen
2005-09-27 15:54 ` Adam Sjøgren
2005-09-28 9:40 ` Simon Josefsson
2005-09-28 9:57 ` Adam Sjøgren
2005-09-29 13:36 ` Simon Josefsson
2005-09-29 14:35 ` Adam Sjøgren
2005-09-30 0:19 ` Simon Josefsson
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=iluu0g6lez3.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--cc=ding@gnus.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.
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).