From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Display occidental characters in name of files attached
Date: Sat, 11 Jan 2003 22:12:53 +0100 [thread overview]
Message-ID: <m34r8fz8yy.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87bs2n4cu5.fsf@ouvaton.org>
Jean-Philippe Georget <jpgeorget@ouvaton.org> writes:
> I receive some files with occidental characters and Gnus display
> somthing like :
>
> [2. application/zip; =?ISO-8859-1?Q?pr=E9pa=20s=E9ance=204.ZIP?=]...
> ^^^^^^^^^^^^^^^ ^^^ ^^^ ^^^ ^^^^
>
> Is it possible to display the good characters like this ?
>
> [2. application/zip; prépa séance.ZIP]...
Well -- the problem is that that encoding is invalid. RFC2047 does
not allow using "Q" encodings of file names, so interpreting those
would (strictly speaking) be wrong.
(RFC2231 specifies how file names like that should be encoded, and
Gnus supports decoding those.)
On the other hand, Gnus could guess that some broken MUA has
Q-encoded something it shouldn't, but just decode it anyway. That
would be the liberal thing to do. Opinions?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
parent reply other threads:[~2003-01-11 21:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <87bs2n4cu5.fsf@ouvaton.org>]
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=m34r8fz8yy.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).