From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Fixes for nnrss.el (and rfc2047.el) in the v5-10 branch
Date: Tue, 05 Apr 2005 09:43:17 +0900 [thread overview]
Message-ID: <b9ymzseaw9m.fsf@jpl.org> (raw)
In-Reply-To: <v93bveouya.fsf_-_@marauder.physik.uni-ulm.de>
>>>>> In <v93bveouya.fsf_-_@marauder.physik.uni-ulm.de> Reiner Steib wrote:
> Katsumi told me that he will try to look into this after releasing the
> next version of emacs-w3m.
I'm now working on merging nnrss.el into the v5-10 branch and I
noticed there are some German web sites using the windows-1252
encoding even if they declare that the encoding is iso-8859-1.
For instance, the following rss feed declares
encoding="ISO-8859-1" and uses characters in 0x80-0x9f which are
out of the iso-8859-1 specification.
http://www.laut.de/partner/allgemein/news.rdf
I'm groping for the way (which can be used with old Emacsen too)
to solve the problem.
[...]
> OTOH, `nnrss.el' is comparable to `gnus-registry.el' and
> `spam-stat.el' where we already use `make-hash-table' there in
> v5-10. Opinions?
I've changed nnrss.el for the v5-10 branch so that it may use
`gnus-make-hashtable'. In addition, there are other problems
which I've fixed in the local system:
time-date.el uses `#x10000' and `#xffff' which cannot be read by
Emacs 20.
`rfc2047-decode' won't work in XEmacs because
`mm-subst-char-in-string' doesn't allow the fourth argument.
I will commit those fixes together with nnrss.el and others.
Regards,
next prev parent reply other threads:[~2005-04-05 0:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-19 18:23 Patch: Allow nnrss to be verbose Mark Plaksin
2005-02-20 0:47 ` Katsumi Yamaoka
2005-02-20 10:42 ` Mark Plaksin
2005-02-20 11:43 ` Katsumi Yamaoka
2005-02-21 13:51 ` Arne Jørgensen
2005-02-21 14:34 ` Reiner Steib
2005-02-21 14:42 ` Arne Jørgensen
2005-02-21 14:54 ` Arne Jørgensen
2005-02-21 16:05 ` Reiner Steib
2005-02-21 22:52 ` Katsumi Yamaoka
2005-02-21 23:25 ` Katsumi Yamaoka
2005-03-02 16:48 ` Fixes for nnrss.el (and rfc2047.el) in the v5-10 branch (was: Patch: Allow nnrss to be verbose) Reiner Steib
2005-04-05 0:43 ` Katsumi Yamaoka [this message]
2005-04-06 8:37 ` Fixes for nnrss.el (and rfc2047.el) in the v5-10 branch 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=b9ymzseaw9m.fsf@jpl.org \
--to=yamaoka@jpl.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).