From: Mark Plaksin <happy@usg.edu>
Cc: ding@gnus.org
Subject: [emacs-w3m:08486] Re: nnrss should borrow nnshibmun's RSS date processor...or something
Date: Tue, 03 Jan 2006 21:50:47 -0500 [thread overview]
Message-ID: <87psn8aepk.fsf@stone.tss.usg.edu> (raw)
In-Reply-To: <b4m3bk4spt3.fsf@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> I think the best way at the present is yours, i.e., to make
> nnrss always provide RFC822 date. However, I still don't know
> the reason why we should not use ISO 8601 date in nnrss
> articles. Though we might not be getting used to seeing it in
> our eyes, I don't think that is so serious.
My original problem was that Gnus showed some RSS articles with a date of
midnight Jan 1 1970. I found the cause to be dc:date being in ISO 8601
format. At that point I assumed Gnus couldn't handle ISO 8601 dates at
all. I saw that sb-rss.el handled them and thought that was a good place
to steal code from.
This feed has ISO 8601 dates: http://del.icio.us/rss/popular/ Does it give
incorrect dates for you too?
>> If Gnus switches to date-to-time, then no change will be needed in nnrss,
>> yes?
>
> It will make several date-oriented features of Gnus, e.g.,
> sorting, expiration, etc., work with ISO 8601 date. However,
> I'm not sure whether all those features actually work and are
> actually used. I can only say with certainty that they will
> work with RFC822 date.
Gotcha.
>> I copied shimbun-rss-process-date, changed the first line from this:
>
>> (luna-define-method shimbun-rss-process-date ((shimbun shimbun-rss) date)
>
>> to this:
>
>> (defun map-shimbun-rss-date (date)
>
>> and then patched nnrss.el with the attached patch.
>
> Thanks. It looks good to me, and I seem to be able to rewrite
> it in nnrss.el if we cannot use the shimbun code directly.
>
>>> 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.
>
>> I don't know enough to prefer either format :) I was just trying to find a
>> way to make nnrss show the correct date all the time. Making nnrss able to
>> do this in both the trunk and v5-10 sounds good to me though I only use
>> trunk.
>
> Does ISO 8601 date actually cause you pain, or give you any
> trouble? If so, we can call it a bug and we should fix it. ;-)
As mentioned above I could live with dates in any format as long as they're
correct :) Inertia makes me prefer RFC822 format but I could adapt. But
the main problem is getting a date of Jan 1 1970 instead of the correct
date.
next prev parent reply other threads:[~2006-01-04 2:50 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 ` [emacs-w3m:08474] " Katsumi Yamaoka
2006-01-02 14:28 ` Mark Plaksin
2006-01-04 2:13 ` [emacs-w3m:08485] " Katsumi Yamaoka
2006-01-04 2:50 ` Mark Plaksin [this message]
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=87psn8aepk.fsf@stone.tss.usg.edu \
--to=happy@usg.edu \
--cc=ding@gnus.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).