Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: Gaetan Leurent <gaetan.leurent@ens.fr>
Subject: Fixes for nnrss.el (and rfc2047.el) in the v5-10 branch (was: Patch: Allow nnrss to be verbose)
Date: Wed, 02 Mar 2005 17:48:13 +0100	[thread overview]
Message-ID: <v93bveouya.fsf_-_@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b9ybradv84l.fsf@jpl.org> (Katsumi Yamaoka's message of "Tue, 22 Feb 2005 07:52:10 +0900")

On Mon, Feb 21 2005, Katsumi Yamaoka wrote:

>>>>>> In <v93bvpyk3d.fsf@marauder.physik.uni-ulm.de> Reiner Steib wrote:
>> I think such changes should go in the v5-10 branch, too.  But applying
>> the patch (cvs diff -r7.24 -r7.26) fails on v5-10.
>
> I can make it support multilingual text as in the trunk (it
> includes the verbose patch, of course), although it might not be
> a bugfix.  Am I able to do it?  Actually, nnrss in the v5-10
> branch cannot be used at least for Japanese sites, for example:
>
> http://www3.asahi.com/rss/index.rdf
[...]

On Tue, Feb 22 2005, Katsumi Yamaoka wrote:

> Ouch!  It requires an overall replacing of rfc2047.el with the
> one in the trunk.  The main load to me is to write the ChangeLog,
> though.

Katsumi told me that he will try to look into this after releasing the
next version of emacs-w3m.

But if anyone else want to work on it, here are some remarks when
trying to sync `rfc2047.el' and `nnrss.el':

- It seems that nobody has merged the bugfixes from the trunk yet.  We
  should surely do this[1].  Jesper Harder has committed most of them
  on the trunk, but probably he didn't have time for merging them to
  v5-10 (the stable branch) yet.

- We cannot apply all changes blindly (see: "cvs diff -r7.1 -r7.26
  nnrss.el" or better `C-u C-x v = nnrss.el RET 7.1 RET 7.26 RET')
  since we want to keep the v5-10 compatible with Emacs 20.7 and
  XEmacs 21.1.  (E.g. `make-hash-table' is not available in Emacs
  20.7.)

  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?

Bye, Reiner.

[1] See a recent bug report from Gaetan Leurent on emacs-devel:
    http://thread.gmane.org/qlkoee2ernr.fsf%40clipper.ens.fr
    <news:qlkoee2ernr.fsf@clipper.ens.fr>
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



  parent reply	other threads:[~2005-03-02 16:48 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             ` Reiner Steib [this message]
2005-04-05  0:43               ` Fixes for nnrss.el (and rfc2047.el) in the v5-10 branch Katsumi Yamaoka
2005-04-06  8:37                 ` 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=v93bveouya.fsf_-_@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=gaetan.leurent@ens.fr \
    /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).