Xmltv needs to be a bit more robust..

[sash]

Hi Sub

I hoping possibly you could make your xmltv a bit more robust..
seems it works quite well with the tsreaders xmltv file ( for those not familar tsreader is dvb sat program found at coolstf.com - there is a free crippled version that will download the guide ). you can download a nine day guide for most sats in a couple minutes ( but I find the 4 day guide much more reliable) . normally it will only download the 2 hour guide but if you go transponder by transponder you will find the one that has the four or nine day guide. once you find it just remember that transponder and use it to download the guide quickly

BUT..... there is a bit of a problem since data streams from the sats can come down a bit gagbled at times you might have to receive the guide a couple time before getting a good one..
when checking the problem out in the epg.xml it seems most of the time is just because there might be an unreconizable character in the description of the program and your xml import program does not know how to deal with this character and fails to load the xml..

anyways just a suggestion.. it alot easier to download the guide this way then to do it over the net, especially so if you live in a country that does not have xmltv support or surfing by modem. and for some sats you could be talking a thousand channels to have to download via these routes..

[sub]

Quote[/b] ]when checking the problem out in  the epg.xml  it seems most of the time is just because there might be an unreconizable character  in the description of the program and your xml import program does not know how to deal with this character and fails to load the  xml..

The Microsoft API I use for loading XML documents will only load VALID xml documents, which I also believe is the right thing to do.
What type of unreconizable character are we talking about? If its just like an extended character (umlauts etc), then chances are tsreader is just not correctly setting the encoding type on the first line of the XML as per the spec, and you're probably best to talk to the author of tsreader. If it is this extended character problem, you could probably use a batch file to add the encoding type to the start of the xmltv file.
If it's an ampersand or other illegal character, then the author of tsreader will need to fix this by encoding the data before writing it to the XML file.

[sash]

no problem, Like I said it does make proper xmltv most of the time.. but since the streams can be a bit flakey atimes and there is data curruption. I guess a filter would be good way to repair any inconsistancy in the xmltv file. would be the easiest route.. scan for illegal characters and remove them.. when they do come up....

anyways I included any example of 2 epg generated one was a proper one gereated by tsreader.. and one was one with an improper characters as generated in a flakey stream.. if you are curious on the illegal character