Gnus development mailing list
 help / color / mirror / Atom feed
From: Shenghuo ZHU <zsh@cs.rochester.edu>
Cc: ding@gnus.org
Subject: Re: Coping with ELM and MIME
Date: 13 Jul 1999 01:20:28 -0400	[thread overview]
Message-ID: <2nk8s5yvkz.fsf@tiger.jia.vnet> (raw)
In-Reply-To: <yc0n1x1js63.fsf@ufleku.daimi.au.dk>

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

>>>>> "Ahe" == Peter von der Ahé <pahe@daimi.au.dk> writes:

Ahe> Hi!
Ahe> Pterodactyl Gnus v0.95

Ahe> Sometimes I get a mail from an ELM user with this header:

Ahe> Content-Type: text

Ahe> No Mime-version or CTE header, just CT with no charset.  The problem
Ahe> is that the mail really is in the iso-8859-1 charset.  Chars like æ
Ahe> are shown as \346.

Ahe> Can I do anything besides editing the headers of the mail to get the
Ahe> \346 shown as æ?

Ahe> Cheers,
Ahe> Peter

The Content-Type is broken. 

This patch will fix broken CT.

1999-07-12  Shenghuo ZHU  <zsh@cs.rochester.edu>

	* gnus-art.el (article-decode-charset): Fix broken CT.



[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 95-zsh5.diff --]
[-- Type: text/x-patch, Size: 353 bytes --]

--- gnus-art.el	1999/07/13 03:02:39	1.1
+++ gnus-art.el	1999/07/13 05:18:37
@@ -1403,6 +1403,8 @@
 	      (save-excursion (set-buffer gnus-summary-buffer)
 			      gnus-newsgroup-ignored-charsets))
 	     buffer-read-only)
+	(if (and ctl (not (string-match "/" (car ctl)))) 
+	    (setq ctl nil))
 	(goto-char (point-max))
 	(widen)
 	(forward-line 1)

[-- Attachment #3: Type: text/plain, Size: 18 bytes --]


-- 
Shenghuo ZHU

  reply	other threads:[~1999-07-13  5:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-13  0:43 Peter von der Ahé
1999-07-13  5:20 ` Shenghuo ZHU [this message]
1999-07-14 11:13   ` Peter von der Ahé

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=2nk8s5yvkz.fsf@tiger.jia.vnet \
    --to=zsh@cs.rochester.edu \
    --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).