-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Flavio S. Glock wrote: | Matthew Buckett wrote: | |>For the strings that are used to create new Date::ICal instances (eg |>Date::ICal->new( ical => '19971024T120000' ); ) does this module follow |>a spec from somewhere else? |> |>There is the Date-Time section (4.3.5) from RFC2445 |>http://www.ietf.org/rfc/rfc2445.txt which gives a formal spec for the |>date-time format. It seems like Date::ICal impliments a relaxed version |>of this Date-Time and a bit of Date. |> |>Am I looking in the right place? | | | Yes, it is based on RFC2445.
It seems to deal correctly with Date-Time values sucessfully but it attempts to parse Date values (eg 20030403) and does so incorrectly.
If I attempt to parse the ICal date 20030403 I get the DateTime of 20030402T230000Z due to currently being in british summer time. To get around this I can append a Z to the Date to give 20030403Z put this is not a legal Date accoring to RFC2445.
| Date::ICal does not implement named timezones. | If you need additional functionality, that would be in the new | "DateTime" module, | or in Net::ICal. | | Net::ICal - Interface to RFC2445 (iCalendar) calendaring and | scheduling protocol.
This is the module that I am looking at and the last CVS commits made seem to hint that Date::ICal should be used instead of Net::ICal::Time
| DateTime - Reference implementation for Perl DateTime objects
Maybe I should look at changing Net::ICal to use DateTime::Format::ICal?
- -- +--Matthew Buckett-----------------------------------------+ | Learning Technology Support Assistant | | Tel: +44 (0) 20 7882 7580 http://www.odl.qmul.ac.uk/ | +------------ODL Unit, Queen Mary, University of London----+
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE+jFAZ5KFl027Pmh0RAoGiAJ9z8HTMMhkzLIn2jdyde6O38PL3NgCgvFTo OtbgSaH6lzNwO1lUqdvnunU= =P/lg -----END PGP SIGNATURE-----
