Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Tim Landscheidt <tim@tim-landscheidt.de>
To: info-gnus-english@gnu.org
Subject: Re: Charset hiccups with HTML mails display
Date: Sun, 20 Jun 2010 20:12:52 +0000	[thread overview]
Message-ID: <m3zkyp4g57.fsf@passepartout.tim-landscheidt.de> (raw)
In-Reply-To: <m31vcdgsmn.fsf@passepartout.tim-landscheidt.de>

I wrote:

> I have been having for quite some time the problem of HTML
> mails not properly displaying due to charset hiccups (Gnus
> v5.13/GNU Emacs 23.1.1 here) that I need to tackle now.

>   The issue is easily explained: A message consisting of
> (only relevant header lines):

> | MIME-Version: 1.0
> | Content-Transfer-Encoding: 8bit
> | Content-type: text/html; charset="iso-8859-1"

> | <html>
> |   <body>
> |     <p>Test: &Auml;</p>
> |   </body>
> | </html>

> should display "Test: Ä" in some way, but instead it says:
> "Test: \303\204" (i. e. "Ä" encoded in UTF-8).

>   mm-text-html-renderer is lynx,
> mm-text-html-renderer-alist's lynx entry is (lynx
> mm-inline-render-with-stdin nil "lynx" "-dump" "-force_html"
> "-stdin" "-nolist"). If I prepend the latter argument list
> with "-display_charset=iso-8859-1", instead of "\303\204"
> "\304" is rendered (i. e. "Ä" encoded in ISO 8859-1).

>   So the problem seems to be that Gnus doesn't accept Lynx's
> output as UTF-8 but as some raw binary. I use shell-command/
> shell-command-on-region on a daily basis, so the source of
> the problem does not lie with Emacs in this case.

>   Any ideas?

Isn't there even a single kind soul out there who could tem-
porarily set his mm-text-html-renderer to lynx, view an HTML
mail and confirm my report or not? :-)

Tim

      reply	other threads:[~2010-06-20 20:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-11 21:35 Tim Landscheidt
2010-06-20 20:12 ` Tim Landscheidt [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=m3zkyp4g57.fsf@passepartout.tim-landscheidt.de \
    --to=tim@tim-landscheidt.de \
    --cc=info-gnus-english@gnu.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).