Re: Transition from tv_grab_uk_rt to tv_grab_sd_json

On 6/5/2016 3:21 PM, Kevin Groeneveld wrote:
> On Sun, Jun 5, 2016 at 2:19 PM, Kevin Groeneveld 
> <[email protected] <mailto:[email protected]>> wrote:
>
>         (Since I'm on MythTV 0.24 I also put
>         back the $previously_shown{'start'} =
>         $dt->strftime('%Y%m%d%H%M%S %z');
>         line that was changed to '%Y%m%d' in XMLTV 0.5.68.)
>
>
>     I have been planning on adding a config option to specify the
>     previously shown date format to address this but have not gotten
>     to it yet.
>
>
> I just committed a change that allows the previously-shown format to 
> be configured for date only or date and time.

Does SD-JSON ever report a time for previously-shown?  You shouldn't 
report more precision than the data source.

BTW, as far as MythTV and timezones,  the XMLTV dates should always be 
in a TIME-OFFSET, not timezone format.  It can have an offset (+0100,  
-0500, etc) or just use +000 and provide UTC.   The purpose of the 
office is to improve readability.   With the numeric offset you can 
always convert to UTC for storage.

It's important to realize that the XMLTV times are not TIMEZONES... for 
example, they don't change with DST.  That's up to the data source. 
(Gracenote deals with it properly.)

Robert

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e

_______________________________________________
xmltv-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xmltv-users