Gnus development mailing list
 help / color / mirror / Atom feed
From: morioka@jaist.ac.jp (守岡 知彦 / MORIOKA Tomohiko)
Subject: Re: Malformed MIME quoted-printable message
Date: 19 Nov 1996 02:02:58 +0900	[thread overview]
Message-ID: <s1ck9rjwd31.fsf@jaist.ac.jp> (raw)
In-Reply-To: Steinar Bang's message of 18 Nov 1996 08:20:55 +0100

[-- Attachment #1: Type: text/plain, Size: 2155 bytes --]

>>>>> In <whpw1blvhk.fsf@norne.metis.no> 
>>>>>	Steinar Bang <sb@metis.no> wrote:

Steinar> >>>>> Hrvoje Niksic <hniksic@srce.hr>:

Steinar> > Lars Magne Ingebrigtsen (larsi@ifi.uio.no) wrote:
Steinar> >> I've included `gnus-article-de-quoted-unreadable' in
Steinar> >> `gnus-article-display-hook' by default.  If you're using
Steinar> >> tm, you should probably take that function out of the
Steinar> >> hook.

Steinar> > Or tm should do it by itself.

Steinar> Sounds like a better idea.  Who makes a patch to the latest
Steinar> tm, and send it to
Steinar> <URL:mailto:bug-tm-en@chamonix.jaist.ac.jp>?

  I don't want to modify gnus-mime for this case.

  I think `gnus-article-display-hook' is not suitable for
`gnus-article-de-quoted-unreadable'.

  Such pseudo MIME feature is used when real MIME feature is not
available or don't want to do MIME processing.  So I propose new
method called when `gnus-show-mime' is nil.

  Current MIME processing code of `gnus-article-prepare' is following:

		;; Decode MIME message.
		(when gnus-show-mime
		  (if (or (not gnus-strict-mime)
			  (gnus-fetch-field "Mime-Version"))
		      (funcall gnus-show-mime-method)
		    (funcall gnus-decode-encoded-word-method)))
		;; Perform the article display hooks.
		(run-hooks 'gnus-article-display-hook))

I propose to modify to following:

		;; Decode MIME message.
		(if gnus-show-mime
		    (if (or (not gnus-strict-mime)
			    (gnus-fetch-field "Mime-Version"))
			(funcall gnus-show-mime-method)
		      (funcall gnus-decode-encoded-word-method))
		  (funcall gnus-show-traditional-method)
		  )
		;; Perform the article display hooks.
		(run-hooks 'gnus-article-display-hook))

And set `gnus-article-de-quoted-unreadable' to
`gnus-show-traditional-method'.

  Thanks,
-- 
----------------------------------------------------------------------
Morioka Tomohiko <morioka@jaist.ac.jp>
(`Morioka' is my family name, `Tomohiko' is my personal name.)
--- I protest Chinese nuclear testing --------------------------------
----------------- and virtual testing of United States and France. ---
# PGP public key: http://www-ks.jaist.ac.jp/~morioka/tomohiko/pgp.key

[-- Attachment #2: Type: application/pgp-signature, Size: 346 bytes --]

  reply	other threads:[~1996-11-18 17:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-11-17  3:05 Steven L Baur
1996-11-17 10:59 ` Lars Magne Ingebrigtsen
1996-11-17 19:44   ` Steven L Baur
1996-11-17 20:04     ` Lars Magne Ingebrigtsen
1996-11-17 20:16     ` Per Abrahamsen
1996-11-17 21:33       ` Steven L Baur
1996-11-19  9:37         ` Wesley.Hardaker
1996-11-19 15:45           ` Per Abrahamsen
1996-11-17 19:48   ` Hrvoje Niksic
1996-11-18  7:20     ` Steinar Bang
1996-11-18 17:02       ` 守岡 知彦 / MORIOKA Tomohiko [this message]
1996-11-18  7:16   ` 守岡 知彦 / MORIOKA Tomohiko
1996-11-18 17:48     ` Lars Magne Ingebrigtsen

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=s1ck9rjwd31.fsf@jaist.ac.jp \
    --to=morioka@jaist.ac.jp \
    /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).