From: wmperry@aventail.com (William M. Perry)
Subject: Re: w3/Gnus/Emacs 20 charset decoding
Date: Wed, 1 Dec 1999 21:58:05 -0500 [thread overview]
Message-ID: <199912020258.VAA29151@megalith.bp.aventail.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "02 Dec 1999 03:09:07 +0100"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> I've installed Emacs 20.4.93 and w3. w3 seems to reliably make Emacs
> dump core (nice to see that Gnus isn't the only package to do that :-),
> so I've backed down to Emacs 20.4 instead.
Come to the bleeding edge lars! 20.5.92.9 is the way to go! Come see the
violence inherent in the new redisplay. :)
> Anyway, the problem is with non-ascii characters in web-based groups. It
> would be nice if w3 could avoid decoding the characters -- is there a way
> to make it do that? That is, some coding-system-for-read in w3 should be
> bound to `binary' by Gnus before calling the w3 functions, but which
> ones? Heeelp.
Since I'm in the midst of revamping Emacs/W3 and URL to use your mm and
mailcap code, you tell me. Is there anything I can do to make this easier?
The URL package has always just used the 'binary' method. Then the w3
parser and friends use the charsets. I'm actually going to be looking at
how Gnus does internationalization, since the way w3 does it sucks.
-Bill P.
next prev parent reply other threads:[~1999-12-02 2:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-02 2:09 Lars Magne Ingebrigtsen
1999-12-02 2:58 ` William M. Perry [this message]
1999-12-02 3:14 ` Lars Magne Ingebrigtsen
1999-12-02 3:56 ` Alan Shutko
1999-12-02 4:08 ` 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=199912020258.VAA29151@megalith.bp.aventail.com \
--to=wmperry@aventail.com \
/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).