Re: How do I adjust the timezone of the EPG with EPG123?
Posted: Thu May 07, 2020 9:39 pm
There is no method because it shouldn't be necessary. Here is the definition in the XMLTV.DTD document which describes how time is to be entered and interpreted.
Whatever program you have that is consuming the XMLTV file is doing it incorrectly. It is translating programme start and end times as local time instead of recognizing that the times are UTC. NextPVR did something similar, though it would respect the timezone offset but would not respect times that did not have an offset should be considered UTC... it would translate the time as local. The best solution between the 2 of us was for me to always include the offset of +0000.
So no, no method to change the times. I don't plan on accommodating every piece of software out there that did not follow the description document and might consume the XMLTV file from EPG123. This is why there is a "standard," that everyone should follow, so that there wouldn't be issues like this.
If you want to modify the file yourself, just search and replace all "+0000" with "+0100" or even "BST" prior to consuming it.
EDIT: scratched out above. If the consuming program doesn't respect +0000, it is not going to respect +0100 or BST either.
Code: Select all
All dates and times in this DTD follow the same format, loosely based
on ISO 8601. They can be 'YYYYMMDDhhmmss' or some initial
substring, for example if you only know the year and month you can
have 'YYYYMM'. You can also append a timezone to the end; if no
explicit timezone is given, UTC is assumed. Examples:
'200007281733 BST', '200209', '19880523083000 +0300'. (BST == +0100.)
So no, no method to change the times. I don't plan on accommodating every piece of software out there that did not follow the description document and might consume the XMLTV file from EPG123. This is why there is a "standard," that everyone should follow, so that there wouldn't be issues like this.
If you want to modify the file yourself, just search and replace all "+0000" with "+0100" or even "BST" prior to consuming it.
EDIT: scratched out above. If the consuming program doesn't respect +0000, it is not going to respect +0100 or BST either.