Date format

[Steve]

Great application. However I am not running Shepherd with MythTV. I need the date format to be in year/month/day/hour/minutes/seconds format. Can you steer me in the right direction to make the necessary changes?

Many thanks.

[max]

That is the date format output by Shepherd. If you run it and look at the resulting ~/.shepherd/output.xmltv file, you'll see this kind of thing:

  <programme start="200703070630" stop="200703070705" channel="abc2.fta.au">
    <title lang="en">Lateline</title>
    <desc lang="en">A unique nightly news analysis program bringing you up-to-the-minute coverage of Australian and international news and events. Presented by Tony Jones.</desc>
    <category lang="en">News</category>
    <subtitles type="teletext" />
  </programme>

[lincoln]

Steve,

Shepherd complies with the standard XMLTV DTD and outputs programme dates/times according to the DTD. (see http://xmltv.org).

Be interested in hearing what device you're looking to use Shepherd with. Feel free to ask additional questions on the mailing list.

[Steve]

Thanks Max. I'm using Webscheduler. I've altered reconciler_mk2 to suit my needs. However is this likely to be overwritten when sheppherd does an update of this module.

[max]

Hi Steve, still not clear on how Shepherd's output differs from what you want.

[Steve]

Webscheduler requires a date format 14 digits in length to include seconds. In reality this means that there is an extra "00" on the end of the string., i.e, from your example above:

This: start="200703070630" stop="200703070705"

Becomes: start="20070307063000" stop="20070307070500"

[lincoln]

Hi Steve, changing the reconciler in this way isn't really a good solution to the problem: firstly, it then create a date/time format which no longer obeys the XMLTV spec (so breaks mythtv), secondly, there are postprocessors which are typically run after the reconciler, which possibly go & rewrite the time fields (such as the augment_timezone postprocessor).

i think we can accomodate webscheduler correctly, but we really need to know more about how you call shepherd, whether its fully functional on windows, what grabbers work, etc. the ticket system isn't really ideal for having this form of communication, can you join the shepherd mailing list & we can discuss the various points there.

[Steve]

No problems Lincoln. I'll join the mailing list and will take it from there.

[lincoln]

implemented via [615]