Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: Where to complain?
Date: Tue, 10 Jan 2006 18:36:16 +0900	[thread overview]
Message-ID: <b4mbqyk5srz.fsf@jpl.org> (raw)
In-Reply-To: <85hd8c78rb.fsf@lola.goethe.zz>

>>>>> In <85hd8c78rb.fsf@lola.goethe.zz> David Kastrup wrote:

> Katsumi Yamaoka <yamaoka@jpl.org> writes:

>> I don't know what does it, but such a behavior is performed by
>> the HTML renderer specified in the `mm-text-html-renderer'
>> variable; `w3m', `links' and `lynx' work fine, AFAIK.

> w3m-standalone in my case, which would be the standard setting.  So it
> would appear that the character encoding (which is part of the MIME
> part declaration) is not passed to w3m or something?

> w3m alone used on web pages outside of Emacs appears to work.  Maybe
> something is wrong in mm-view.el?  It would appear that the following
> is responsible for the stuff:

> (defun mm-inline-render-with-stdin (handle post-func cmd &rest args)
>   (let ((source (mm-get-part handle)))
>     (mm-insert-inline
>      handle
>      (mm-with-unibyte-buffer
>        (insert source)
>        (apply 'mm-inline-wash-with-stdin post-func cmd args)
>        (buffer-string)))))

> Now what happens with the unibyte-buffer?  Perhaps the
> mm-inline-wash-with-stdin process filter is not too happy about
> inserting w3m output in utf-8 (the current locale) into a unibyte
> buffer?  Or buffer-string, which likely happens to be unibyte decoded
> into utf-8, then gets interpreted as latin-1, the encoding of the mime
> part?  Or w3m tries interpreting the latin-1 encoded input as utf-8?

I see.  That is just the point.  When w3m is called by way of
emacs-w3m (i.e., mm-text-html-renderer is set to `w3m'),
w3m-input-coding-system and w3m-output-coding-system are used
for exchanging data.

> There seem many ways to get this wrong.  When the locale and language
> environment and part encoding are all latin-1, stuff works.

The locale and the language environment are irrelevant, I think.
We may need to make Gnus provide the following functions:

mm-inline-text-html-render-with-w3m-standalone
gnus-article-wash-html-with-w3m-standalone

However, they will be complicated like emacs-w3m if ones want to
make w3m-standalone work well like emacs-w3m.  Why don't you use
w3m? :)



  reply	other threads:[~2006-01-10  9:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-10  7:31 David Kastrup
2006-01-10  8:36 ` Katsumi Yamaoka
2006-01-10  9:05   ` David Kastrup
2006-01-10  9:36     ` Katsumi Yamaoka [this message]
2006-01-10 10:10       ` David Kastrup
2006-01-10 11:38         ` Katsumi Yamaoka
2006-01-11  8:34           ` w3m-standalone (was Re: Where to complain?) 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=b4mbqyk5srz.fsf@jpl.org \
    --to=yamaoka@jpl.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).