From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: emacs-w3m@namazu.org
Subject: [emacs-w3m:08474] Re: nnrss should borrow nnshibmun's RSS date processor...or something
Date: Thu, 22 Dec 2005 14:27:05 +0900 [thread overview]
Message-ID: <b4mirthln12.fsf@jpl.org> (raw)
In-Reply-To: <87y82dokdt.fsf@stone.tss.usg.edu>
>>>>> In [emacs-w3m : No.08473] Mark Plaksin wrote:
> Some RSS feeds provide the date in ISO 8601 date format. sb-rss.el from
> nnshimbun converts from ISO 8601 to a format that Gnus can handle. nnrss
> does no conversion so Gnus ends up saying the date is the start of the Unix
> epoch.
Gnus will be able to handle ISO 8601 date if we replace every
`parse-time-string' that Gnus uses with `date-to-time' which
uses timezone.el. However, it is effective only in Emacs 22,
because timezone.el distributed with Emacs 21 doesn't understand
ISO 8601 date. For instance:
(timezone-parse-date "2005-12-22T13:14:03+09:00")
;; Emacs 22.0.50
=> ["2005" "12" "22" "13:14:03" nil]
;; Emacs 21.4
=> ["0" "0" "0" "0" nil]
> It would be nice if the conversion function from sb-rss.el were put into
> some library that nnrss could easily call. It's not clear to me where the
> best place for that would be.
I think it should be done in nnrss.el since parse-time.el and
time-date.el belong to Emacs, not Gnus.
> For the moment, I hacked my copy of nnrss.el to call an un-shimbuned
> version of shimbun-rss-process-date.
It seems to have to be used before using `message-make-date' in
the `nnrss-check-group' function. Could you present it?
BTW, why do you prefer RFC822 date rather than ISO 8601 date?
If it is for the bugfix, we should apply it to both the Gnus
trunk and the v5-10 branch.
next prev parent reply other threads:[~2005-12-22 5:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 3:55 [emacs-w3m:08473] " Mark Plaksin
2005-12-22 5:27 ` Katsumi Yamaoka [this message]
2006-01-02 14:28 ` [emacs-w3m:08474] " Mark Plaksin
2006-01-04 2:13 ` [emacs-w3m:08485] " Katsumi Yamaoka
2006-01-04 2:50 ` [emacs-w3m:08486] " Mark Plaksin
2006-01-04 3:05 ` Katsumi Yamaoka
2006-01-04 3:17 ` Mark Plaksin
2006-01-05 7:09 ` [emacs-w3m:08489] " Katsumi Yamaoka
2006-01-05 14:48 ` [emacs-w3m:08490] " Mark Plaksin
2006-01-05 23:55 ` [emacs-w3m:08491] " Katsumi Yamaoka
2006-01-06 13:17 ` [emacs-w3m:08492] " Mark Plaksin
2006-01-10 10:13 ` [emacs-w3m:08495] " Katsumi Yamaoka
2006-01-14 16:03 ` [emacs-w3m:08502] " Mark Plaksin
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=b4mirthln12.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=emacs-w3m@namazu.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).