Opened 17 years ago

Closed 16 years ago

Last modified 13 years ago

#11 closed defect (fixed)

OzTivo grabber provides bad XMLTV

Reported by: Max Owned by:
Priority: major Milestone: 1.0
Component: Grabber Version: 0.3
Keywords: Cc:

Description

The XML file provided by OzTivo? has elements in the wrong order -- at least, the wrong order according to XMLTV.pm, which refuses to parse it.

Change History (4)

comment:1 Changed 17 years ago by lincoln

(actually, XMLTV.pm doesn't refuse to parse it - it just throws away programmes it considers to be bad).

three approaches to fixing this:

  • host our own local copy of XMLTV.pm exclusively for shepherd & components, with lines 1959-1965 commented out (the "foreach" block that does 'warn "element $name not expected here"; next SUBELEMENT;')
  • talk to OzTivo? folk about getting them to generate compliant XMLTV
  • have our OzTivo? grabber pre-process the input to present the fields in a correct order.

Of these three, 2 is best. But in the short term, perhaps implementing 3 will be the easiest path.

comment:2 Changed 17 years ago by Max

The data from Free*EPG is also out of order (according to current XMLTV.pm). So it'd be nice if we could implement a general fix in Shepherd for naughty grabbers. I vote for the third option, if it's not too hard.

comment:3 Changed 16 years ago by lincoln

Resolution: fixed
Status: newclosed

implemented the 3rd option - just clean up the xmltv we see from oztivo.

see [346].

comment:4 Changed 16 years ago by Max

Excellent!

Note: See TracTickets for help on using tickets.