From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Mime types and attached files
Date: Mon, 17 Apr 2006 13:12:53 +0200 [thread overview]
Message-ID: <m3d5fg5ubu.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <b4m7j5ose2y.fsf@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> The RFC2047-like encoding has not been documented as a standard
> as far as I know. I don't know how it has been decided
> reasonably and democratically. The specification doesn't seem
> to have been unified in mailers that use it.
True. It would be a shame to switch to RFC2047 parameter encoding if
all the other mailers are finally switching to RFC2231.
Has anybody here kept up with IETF discussions on this matter, if any?
What would be the most likely working group dealing with this?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2006-04-17 11:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-28 20:43 Fabrice Popineau
2006-04-14 13:28 ` Lars Magne Ingebrigtsen
2006-04-17 1:54 ` Katsumi Yamaoka
2006-04-17 9:04 ` Lars Magne Ingebrigtsen
2006-04-17 10:15 ` Katsumi Yamaoka
2006-04-17 11:12 ` Lars Magne Ingebrigtsen [this message]
2006-04-17 11:40 ` gdt
2006-04-17 12:32 ` 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=m3d5fg5ubu.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).