[mythtvnz] EPG Data for 'niche' channels ?

[dmoo1790 at ihug.co.nz]

On Thu, 10 May 2012 18:46:27 +1200, Nick Rout <nick.rout at gmail.com> wrote:
> On Thu, May 10, 2012 at 6:26 PM, David Moore <dmoo1790 at ihug.co.nz> wrote:
>> On 10/05/12 17:18, Steven Ellis wrote:
>>>
>>>
>>> On Thu, May 10, 2012 3:14 pm, David Moore wrote:
>>>>
>>>> On 10/05/12 09:07, Steven Ellis wrote:
>>>>>
>>>>>
>>>>> Hi David. In your MythTV setup for the freeview source what time zone
>>>>> do
>>>>> you set for the EPG. In my case I default to using AUTO as I import
>>>>> multiple EPG feeds for different timezones, for example SBS (now
sadly
>>>>> off
>>>>> air).
>>>>>
>>>>> When I generate listings with epgsnoop the data contains the +1200
>>>>> offset
>>>>> based on my local system vs the DVB data.
>>>>>
>>>>> In the case of DTT I merge DVB and MHEG data so that my DTT and DTH
>>>>> channels are being provided with identical EPG information. For the
>>>>> DTT
>>>>> exclusive channels I just pull them from the MHEG file using tv_split
>>>>> and
>>>>> tv_cat.
>>>>>
>>>>> Steve
>>>>>
>>>> Hi Steve. My setting is "none" for the EPG timezone. I only have DVB-T
>>>> so it works fine with the MHEG EPG local times. I'll probably do a
>>>> quick
>>>> fix just for you :) that gives you the option to generate UTC +1200
(or
>>>> +1300 for DST). Then I'll think about a more general solution. /David
>>>>
>>>
>>> Dave. That would be brilliant. Cheers
>>
>>
>> Version 0.3.4 just uploaded. Turned out to be not so simple because (a)
I
>> decided to try and do it right rather than quick and dirty and (b)
>> surprisingly Python doesn't do time zones very well. Anyway I think it
>> works. Just add "-z" command line arg. Enjoy.
>>
> 
> Just pointing out that accroding to the mythtv DTD the prescription
> for date/time formats is:
> 
> 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.)
> 
> 
> http://xmltv.cvs.sourceforge.net/viewvc/xmltv/xmltv/xmltv.dtd
> 
> I haven't followed this thread properly, but the impression I got was
> that one of the scripts was not adding a timezone string to the
> date/time string, but I was unclear to me whether that script was
> creating UTC or localtime.
> 

Doh! I should have RTFM. Would have been easy to add the NZDT or NZST
string to the UTC times or just produce UTC with no timezone string/offset.
FYI the default is/was to produce local times.