[mythtv-users] Re: Timezones, wintertime & Timeoffset

[Stefan Frank]

Per Åge Sørvik <peraage at leneogperaage.com> writes:

> Recently my country (Norway), switched to wintertime, adjusting the time
> 1 hour back. And suddenly, all my listings was 1 hour wrong. Not

Same here but without the off-by-one error. :)

> entirely unexpected, so i did a 'delete from program', and ran
> mythfilldatabase again. Nope, same result. So i adjusted the TimeOffset
> setting from +0200 to +0100. Still same result. Hmm, +0500 ? Same
> result. NULL ? Same result. Clock has UTC set to false, and I'm running
> mythfilldatabase from a different machine than the database/backend.
>
> So, does anybody know if this setting is used for anything ? If so, what
> would be the correct procedure for using it ?

The TimeOffset only matters while running mythfilldatabase. It will
compare this setting with the timezone spec in the xmltv files and, if
they differ, adjust the program start/stop times accordingly.

Assuming TimeOffset = +0200 if you run mythfilldatabase a few hours
before switching to wintertime, the program data for programs running
after the switch-over could be offset by one hour if your listings
provider sets the timezones to +0200 or +0100 respectively.

There's currently no way to avoid this to happen afaik. Except not to
import program data 'for winter time' while it's still summer time and
vice versa. Only if your provider completely ignores the timezone and
always sets it to CET (like the provider i use does it), you'd be
save with TimeOffset = +0100.

bye, Stefan

-- 
It does me no injury for my neighbor to say there are twenty gods or no God.
It neither picks my pocket nor breaks my leg.

                                   -- Thomas Jefferson