Reply to thread

Message

<blockquote data-quote="dvdfreak" data-source="post: 189642" data-attributes="member: 21313">Thanks! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />You raise an interesting problem.&nbsp; The importer will indeed try to do the right thing on its own.&nbsp; Normally all dates and times in an XMLTV file include timezone information.&nbsp; The importer will match this timezone to your own, and do appropriate conversion if needed.&nbsp; For example, I import both a UK guide and a Belgian guide and both are nicely imported into my Belgian timezone.But apparently this system doesn't always work, perhaps your guide data is missing the timezone information?Actually, looking at your own example I see you mention &quot;+0000&quot; being in your guide while Australia is GMT+09:30 (Australia Central Standard), and judging from your posting you are in GMT+10:00.&nbsp; So there will indeed be a 10 hour error since the guide data appears to the importer to come from TV channels in the UK <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />So I guess what's basically needed is an offset-value that is added to (or subtracted from) all imported times?&nbsp; I can easily add that, will put it on my list of TODOs for the next version <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="dvdfreak, post: 189642, member: 21313"] Thanks! :) You raise an interesting problem. The importer will indeed try to do the right thing on its own. Normally all dates and times in an XMLTV file include timezone information. The importer will match this timezone to your own, and do appropriate conversion if needed. For example, I import both a UK guide and a Belgian guide and both are nicely imported into my Belgian timezone. But apparently this system doesn't always work, perhaps your guide data is missing the timezone information? Actually, looking at your own example I see you mention "+0000" being in your guide while Australia is GMT+09:30 (Australia Central Standard), and judging from your posting you are in GMT+10:00. So there will indeed be a 10 hour error since the guide data appears to the importer to come from TV channels in the UK :) So I guess what's basically needed is an offset-value that is added to (or subtracted from) all imported times? I can easily add that, will put it on my list of TODOs for the next version :) [/QUOTE]

Verification