Reply to thread

Message

<blockquote data-quote="mbb" data-source="post: 260050" data-attributes="member: 10503">since my tvguide provider add some new feature&nbsp; the TVguide.xml import fail.status:tvguide.xml:Invalid XML file:Input string was not in a correct format.;After some investigation, it seems that MP doesnt handle well the episode-num field.I asked my provider about this and he claims that he respects the xmltv.dtd standard about this: <a href="http://xml.coverpages.org/XMLTV-DTD-20021210.html" target="_blank">XML: XMLTV - DTD for TV listings</a>I did some some test by replacing some string:xmltv_ns&quot;&gt;.. by xmltv_ns&quot;&gt;..&lt;/episode-num&gt; by &lt;/episode-num&gt;xmltv_ns&quot;&gt;0.. by xmltv_ns&quot;&gt;0and the same for 1.., 2.., 3.., etcIt works, and seems to confirm that the episode-num field parsing have something wrong.I upload the file to test and some logsThanksmbb</blockquote>

[QUOTE="mbb, post: 260050, member: 10503"] since my tvguide provider add some new feature the TVguide.xml import fail. status:tvguide.xml:Invalid XML file:Input string was not in a correct format.; After some investigation, it seems that MP doesnt handle well the episode-num field. I asked my provider about this and he claims that he respects the xmltv.dtd standard about this: [url=http://xml.coverpages.org/XMLTV-DTD-20021210.html]XML: XMLTV - DTD for TV listings[/url] I did some some test by replacing some string: xmltv_ns">.. by xmltv_ns"> ..</episode-num> by </episode-num> xmltv_ns">0.. by xmltv_ns">0 and the same for 1.., 2.., 3.., etc It works, and seems to confirm that the episode-num field parsing have something wrong. I upload the file to test and some logs Thanks mbb [/QUOTE]

Verification