Importing XMLTV file

[zehd]

I'm just playing with EPG data I've gotten from several aussie sites. When it imports into GB-PVR I see some strange things....

Here's a sample program from the xml

Code:

<programme start="20071121203000 +1000" stop="20071121213000 +1000" channel="free.QLDReg.10">
    <title lang="en">House, M.D.</title>
    <sub-title lang="en">You Don't Want to Know</sub-title>
    <desc lang="en">House treats a magician but comes to believe he's faking illness to cover up his own incompetence. Meanwhile, House pits the fellows against each other in his version of an immunity challenge.</desc>
    <category lang="en" />
    <rating system="ABA">
      <value />
    </rating>
  </programme>


  <programme start="20071117180000 +1000" stop="20071117183000 +1000" channel="free.QLDReg.10">
    <title lang="en">The Simpsons</title>
    <sub-title lang="en" />
    <desc lang="en">Join the world's favourite dysfunctional family.</desc>
    <category lang="en" />
    <rating system="ABA">
      <value />
    </rating>
  </programme>

In both examples: When GB-PVR imports this into its database, it takes the Description and copies it to the Ratings filed as well. When there is no specific sub-title (as in the simpsons) then the description is copied over that too

In other words, after import, viewing the TV-Guicde in GB-PVR, I see the same description three times in many cases, as the description is copied into the subtitle and ratings, when there is no data in those fields...

Sometimes this can be quite crowded on the screen with three paragraphs, wrapping onto each other...

Is there some way to fix this in GB-PVR, or could we run the xmltv through a processor ?

[sub]

In both examples: When GB-PVR imports this into its database, it takes the Description and copies it to the Ratings filed as well

I've never seen any reports of this in the past, and the xmltv epg source hasnt been updated in a very long time, which makes me think there must be something subtly wrong with the xmltv file you have been producing. If you zip and attach a complete xmltv file then I'll try it here.

[zehd]

I've never seen any reports of this in the past, and the xmltv epg source hasnt been updated in a very long time, which makes me think there must be something subtly wrong with the xmltv file you have been producing. If you zip and attach a complete xmltv file then I'll try it here.

What do you mean not updated in a long time? I just did it today... Oh well. Thanks. Here's the file that the d1 grabber is getting.

[sub]

What do you mean not updated in a long time? I just did it today...

I mean that the GB-PVR code that imports xmltv listings has been unchanged and stable for a very long time, so unlikely to be a new bug introduced in the latest release.

[zehd]

I mean that the GB-PVR code that imports xmltv listings has been unchanged and stable for a very long time, so unlikely to be a new bug introduced in the latest release.

OK

I noticed that entries with no sub-title information don't have an </sub-title> just a "/>" tag yet when there is info, there's a full tag.

I'm just digging into XML format again as -Oz- and I are starting to work on a new xmltv processor.

I'm going to see if forcing a </sub-title> helps...

[bgowland]

I noticed that entries with no sub-title information don't have an </sub-title> just a "/>" tag yet when there is info, there's a full tag.

From what I can see at the xmltv.org/xmltv page, all examples show that all elements should have the form <element></element>.

If you download the xmltv distribution from Sourceforge, there are apparently some tools including one called tv_validate_file which will check an xmltv file for valid format. (NB I haven't tried it though).

Cheers,
Brian

[sub]

zehd, can you try the attached patch.

It doesnt like these tags being present but empty in this shortened form. Normally the tags just arent included in the file if the data isnt present. It doesnt mind them being there, but empty, as long as it was in the long form shown in bgowlands post above.

[-Oz-]

looks like we have our work cut out for us

[sub]

looks like we have our work cut out for us

Its never been a problem until now, and we've been using dozens of xmltv sources from all around the world, so it cant be that common

[bgowland]

zehd - I've just looked again at the examples from your xmltv file in the first post. Which grabber are you using? It's badly broken as far as I can tell.

The xml may well be valid but some of it doesn't make sense from an xmltv point of view. It's one of those situations - all xmltv is xml but not all xml is xmltv.

Cheers,
Brian