Gnus development mailing list
 help / color / mirror / Atom feed
From: NAKAJI Hiroyuki <nakaji@jp.freebsd.org>
To: ding@gnus.org
Subject: long encoded filename in mime part is truncated and not decoded
Date: Tue, 12 Jun 2007 11:29:45 +0900	[thread overview]
Message-ID: <873b0x3nxi.fsf@roddy.4407.kankyo-u.ac.jp> (raw)

Hi,

Japanese people love to name files using Japanese characters and the
filename is usually looooooooooooooooooooooooooooooooooooooong. And when
a user attached this long-named file, some mail clients truncates the
excoded filename.

For example, when user uses

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; ja-JP; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)

and such a long-named file is attached as mime-multipart, in article
buffer it is shown like this:

[3. application/msword; 44新規学習ニーズ対応プログラム支援経費=?ISO-2022-JP?B?WxskQjpOQnJAKRsoQl0bJEIhS]...

and then, when I typed 'o' at this part, the file is saved as
44新規学習ニーズ対応プログラム支援経費=?ISO-2022-JP?B?WxskQjpOQnJAKRsoQl0bJEIhS 

I don't like it. I want the file to be saved as
44新規学習ニーズ対応プログラム支援経費[採択制]

Is it possible to decode this kind of truncated loooong filename in
Gnus? I got "44新規学習ニーズ対応プログラム支援経費[採択制]" with adding
"=?=" after "...EIhS".

Of cource, I don't mind adding ".doc" after "...[採択制]" by hand when I
save this part.

Regards,
-- 
NAKAJI Hiroyuki



             reply	other threads:[~2007-06-12  2:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12  2:29 NAKAJI Hiroyuki [this message]
2007-06-12  4:27 ` Katsumi Yamaoka
2007-06-12  8:29   ` NAKAJI Hiroyuki
2007-06-12 10:01     ` Katsumi Yamaoka
2007-06-12 13:05       ` NAKAJI Hiroyuki

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=873b0x3nxi.fsf@roddy.4407.kankyo-u.ac.jp \
    --to=nakaji@jp.freebsd.org \
    --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).