From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Gnus and international attachment names
Date: Mon, 31 Dec 2001 00:42:53 +0100 [thread overview]
Message-ID: <m3ofkgb7gi.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m34rvgfuhu.fsf@SnowWhite.Janik.cz>
Pavel@Janik.cz (Pavel Janík) writes:
> Gnus 5.9.0 and Oort too allow to attach a file which has ISO 8859-2
> characters in its name. Oort will attach it as:
>
> Content-Disposition: attachment;
> filename*=iso-8859-2''%ec%b9%e8%f8%be%fd%e1%ed%e9.txt
> So, does this really mean that I'm not able to send the file with this name
> via attachment if I do want to be compliant with all MIME RFCs?
No, this is actually compliant. Only with RFC2231, and not RFC2047.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2001-12-30 23:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3y9t3mhhw.fsf@SnowWhite.Janik.cz>
[not found] ` <rzqvgo3m98q.fsf@djlvig.dl.ac.uk>
2001-04-17 23:46 ` Pavel Janík
2001-04-22 18:00 ` Dave Love
2001-04-22 19:26 ` Pavel Janík
2001-04-22 20:01 ` Bjørn Mork
2001-04-23 7:41 ` Pavel Janík
2001-12-30 23:42 ` Lars Magne Ingebrigtsen [this message]
2001-04-23 10:42 ` Eli Zaretskii
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=m3ofkgb7gi.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).