Note that this leaves a bug with written time zones still in the code. See a thread I started on the xmltv-devel list about the problems with interpreting time zone abbreviations:
http://sourceforge.net/mailarchive/forum.php?thread_id=1784917&forum_id=7180
I'm trying to get the xmltv people to make +0100 style time zone specifications mandatory, which would be the only reasonable fix to this bug as I see it.
This is my first patch to freevo, and I'm also new to Pyton so let me know if I messed up somewhere.
Krister Lagerstrom wrote:
Thanks for the tip! I looked at the docs at http://www.lemburg.com/files/python/mxDateTime.html, and it looks to me as though it doesn't handle arbitrary time zones.Actually, I think the Python mx.DateTime module is probably better for stuff like this. It is included in the newer binary Freevo releases. The docs are on the net.
Regards,
Erland
patch_xmltv-tzbug.tar.gz
Description: Unix tar archive
