Bugs item #831156, was opened at 2003-10-27 17:17
Message generated for change (Comment added) made by epaepa
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=424135&aid=831156&group_id=39046
Category: None
Group: None
>Status: Closed
>Resolution: Out of Date
Priority: 5
Submitted By: Gregor Jasny (gjasny)
Assigned to: Ed Avis (epaepa)
Summary: xmltv doesn't use local timezone
Initial Comment:
Hi,
I've just tried to use an nxtvepg exported database with
tvtime. Basicly it works. But there is an offset of 1 hour. at
the displayed time.
Database entry:
<programme start="20031027184000 +0000"
stop="20031027191500 +0000" channel="CNI0DAB">
[snipped]
</programme>
tv_to_text output:
18:40--19:15 Gute Zeiten, schlechte Zeiten RTL
TVTIME OSD: 18.40-19.15
My timezone is CET.
I hope you can help!
Regards,
-G. Jasny
----------------------------------------------------------------------
>Comment By: Ed Avis (epaepa)
Date: 2004-01-23 19:54
Message:
Logged In: YES
user_id=10769
Given no user response, the fact that timezone output has
been changed in xmltv since November, and the comment about
a now-fixed bug in tvtime, I'm closing this bug.
----------------------------------------------------------------------
Comment By: Ed Avis (epaepa)
Date: 2003-11-01 13:51
Message:
Logged In: YES
user_id=10769
Can you post a way to reproduce this - the commands you
typed and the files you used? What exactly is the bug?
>From what you say above it seems that tv_to_text is doing
its job properly, since the file contained a time '18:40'
and that's what it printed in the output. tv_to_text does
not convert to the local timezone (and shouldn't - eg if you
print out some listings that cross two timezones).
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2003-10-28 08:36
Message:
Logged In: NO
I'll add the same comment here as in the other BUG-report.
Before turning back the one hour last weekend the TVData.xml
file had this time format:
"20031020161500 +0200"
After last weekend:
"20031027144500 CET"
But even before we turned back the clock we was in the same
timezone as the rest of europe, that means in CET.
I'm using XMLTV together with TVHolic. The source of data is
http://www.dagenstv.com and I live in Sweden.
/monshi
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2003-10-28 08:36
Message:
Logged In: NO
I'll add the same comment here as in the other BUG-report.
Before turning back the one hour last weekend the TVData.xml
file had this time format:
"20031020161500 +0200"
After last weekend:
"20031027144500 CET"
But even before we turned back the clock we was in the same
timezone as the rest of europe, that means in CET.
I'm using XMLTV together with TVHolic. The source of data is
http://www.dagenstv.com and I live in Sweden.
/monshi
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2003-10-27 21:29
Message:
Logged In: NO
I experience the smae problem when using XMLTV together with
TVHolic.
Just happened now when the clock was turned back one hour,
adjusting to "normal" time again.
----------------------------------------------------------------------
Comment By: Billy Biggs (vektor)
Date: 2003-10-27 17:21
Message:
Logged In: YES
user_id=153320
This is not a bug in xmltv, it's a bug in tvtime that has
been fixed for tvtime 0.9.11.
See tvtime bug 810167.
http://sourceforge.net/tracker/index.php?func=detail&aid=810167&group_id=64301&atid=506987
-Billy
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=424135&aid=831156&group_id=39046
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
|
