From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Another problem with rfc2047 encoding
Date: Fri, 02 May 2003 18:10:04 +0200 [thread overview]
Message-ID: <m34r4dmisj.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <hv4r4ehk3f.fsf@rasputin.ws.nextra.no>
Bjørn Mork <bmork@dod.no> writes:
> And isn't it wrong to decode the local-part when displaying the
> message Thomas referred to?
Yes, it is. On the other hand, making the decoder much slower for
pretty marginal gain isn't really a good idea, either.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2003-05-02 16:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 17:20 Reiner Steib
2003-04-28 20:47 ` Reiner Steib
2003-05-01 6:38 ` Lars Magne Ingebrigtsen
2003-05-01 6:49 ` Thomas Hühn
2003-05-01 7:14 ` Lars Magne Ingebrigtsen
2003-05-01 7:39 ` Thomas Hühn
2003-05-01 14:48 ` Lars Magne Ingebrigtsen
2003-05-04 19:42 ` Christoph Garbers
2003-05-08 22:49 ` Dave Love
2003-05-15 17:26 ` Christoph Garbers
2003-05-16 16:42 ` Dave Love
2003-05-20 12:42 ` Christoph Garbers
2003-05-22 17:01 ` Dave Love
2003-05-01 8:15 ` Bjørn Mork
2003-05-01 8:42 ` Lars Magne Ingebrigtsen
2003-05-01 12:46 ` Simon Josefsson
2003-05-01 13:28 ` Bjørn Mork
2003-05-02 16:10 ` Lars Magne Ingebrigtsen [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=m34r4dmisj.fsf@quimbies.gnus.org \
--to=larsi@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).