From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Problem with attachment filename.
Date: Fri, 07 Dec 2001 15:41:45 +0100 [thread overview]
Message-ID: <iluoflbnlcm.fsf@dhcp128.extundo.com> (raw)
In-Reply-To: <3joflbzf3z.fsf@www.okpos.com> (Jinhyok Heo's message of "Fri, 07 Dec 2001 16:03:28 +0900")
Jinhyok Heo <novembreN0$PAM@ournature.org> writes:
> I'm using cvs gnus with XEmacs 21.4.5 now.
>
> I don't have any problem with filenames with latin characters, but I
> have with Korean characters. I cannot figure out the filenames, so I
> have to save it in a latin character filename after renaming them.
>
> I think gnus has some problems with charset of attachments.
>
> Can it be fixed?
Can you send a example mail (to bugs@gnus.org perhaps)? What do you
mean you cannot figure out the filename? Gnus should decode the
filename and offer you to save the attachment using that filename.
(Maybe the problem is that the sender is violating the MIME RFC's and
sends the filename using 8bit, QP or something instead of RFC 2231.)
prev parent reply other threads:[~2001-12-07 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 7:03 Jinhyok Heo
2001-12-07 14:41 ` Simon Josefsson [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=iluoflbnlcm.fsf@dhcp128.extundo.com \
--to=jas@extundo.com \
--cc=ding@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).