Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Subject: Re: viewing attachments
Date: Tue, 08 Feb 2005 10:05:27 +1100	[thread overview]
Message-ID: <87acqgnf7s.fsf@zip.com.au> (raw)
In-Reply-To: <b9yd5vczmby.fsf@jpl.org> (Katsumi Yamaoka's message of "Mon, 07 Feb 2005 19:38:41 +0900")

Katsumi Yamaoka <yamaoka@jpl.org> writes:
>
> I had many opportunities to need to see attachments containing
> non-ASCII text or parts which have been compressed by gzip or
> bzip2.

Handa made a change to jka-compr in the emacs cvs (2003-01-24), adding
decode-coding-inserted-region which I believe is meant to do emacs'
usual charset guessing and priorities, like find-file.

I had meant to propose a patch (for gnus-mime-copy-part actually) to
make use of that, either by copying that code from the cvs, or just
using it if emacs is new enough to have it.  Unfortunately I never got
around to working out the details.

> I hit on another idea while considering about it last week.  The
> plan is to add the charset parameter to the MIME header of an
> attachment part automatically if there is a coding cookie in the
> file and the MIME charset corresponding to it exists.

If there's a cookie in the file, can't emacs just use that, without
needing a mime charset parameter?

> I've installed them (including decompressing of compressed parts)

Maybe you can use jka-compr the same way that
gnus-mime-jka-compr-maybe-uncompress does.  Or that function becomes
gnus-mime-copy-part-jka-insert with a patch I'm proposing - see other
message.  That would have the advantage of letting the user customize
compression methods.



  reply	other threads:[~2005-02-07 23:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-07 10:38 Katsumi Yamaoka
2005-02-07 23:05 ` Kevin Ryde [this message]
2005-02-09  2:41   ` Katsumi Yamaoka
2005-02-09  8:19     ` Katsumi Yamaoka
2005-02-10 10:47       ` Katsumi Yamaoka
2005-02-10 23:43         ` Kevin Ryde
2005-02-11  4:00           ` Katsumi Yamaoka
2005-02-12  2:11             ` Katsumi Yamaoka

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=87acqgnf7s.fsf@zip.com.au \
    --to=user42@zip.com.au \
    /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).