From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: RFC-2231 vs. RFC-2047
Date: Thu, 04 Mar 2004 10:01:42 +0900 [thread overview]
Message-ID: <b9ywu61h1c9.fsf@jpl.org> (raw)
In-Reply-To: <m3wu61ikko.fsf@defun.localdomain>
>>>>> In <m3wu61ikko.fsf@defun.localdomain>
>>>>> Jesper Harder <harder@ifa.au.dk> wrote:
> Matthias Andree <ma@dt.e-technik.uni-dortmund.de> writes:
>> Gnus appears to have some difficulties handling RFC-2231, I haven't even
>> checked if it's supposed to be implemented.
> It wasn't. But I've now added it to `rfc2047-encoded-word-regexp'.
There's a mismatched parenthesis, oops. Fixed.
--
Katsumi Yamaoka <yamaoka@jpl.org>
next prev parent reply other threads:[~2004-03-04 1:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 18:52 Matthias Andree
2004-03-03 23:20 ` Jesper Harder
2004-03-04 1:01 ` Katsumi Yamaoka [this message]
2004-03-04 12:22 ` Matthias Andree
2004-05-16 16:05 ` Lars Magne Ingebrigtsen
2004-05-16 18:06 ` Jesper Harder
2004-05-16 23:58 ` Lars Magne Ingebrigtsen
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=b9ywu61h1c9.fsf@jpl.org \
--to=yamaoka@jpl.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).