http://bugs.gpodder.org/show_bug.cgi?id=227
Summary: <dateCreated> in exported OPML does not follow RFC 822
Product: gPodder
Version: 0.11.3
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: low
Component: Application
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
Estimated Hours: 0.0
When gpodder on Ubuntu (0.11.3) exports its list of feeds to an OPML document,
the <dateCreated> tag is not an RFC822, as mandated by the OPML spec at
<http://www.opml.org/spec1> and <http://www.opml.org/spec2>.
The <dateCreated> tag looks like this:
<dateCreated>
Tue Oct 21 21:15:17 2008
</dateCreated>
That date, if properly formatted as an RFC822-style date-time should like one
of these:
Tue, 21 Oct 08 21:15 EDT
Tue, 21 Oct 08 21:15:17 EDT
21 Oct 08 21:15 EDT
21 Oct 08 21:15:17 EDT
Tue, 21 Oct 08 21:15 -0400
Tue, 21 Oct 08 21:15:17 -0400
21 Oct 08 21:15 EDT -0400
21 Oct 08 21:15:17 EDT -0400
RFC1123 altered RFC822 to allow for 4-digit years and RFC2822 superseded it
with obsoleting named timezones and 2-digit years.
Even though the OPML specification, as already mentioned, mandates RFC822, I
think that having gpodder use RFC2822 would be the best option. Th current
non-standard format requires that a programmer writing an OPML scanner create a
special exception to manually scan for the way gpodder does dates.
--
Configure bugmail: http://bugs.gpodder.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
_______________________________________________
gPodder-Bugs mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/gpodder-bugs
