The grabber accepts any parameter without returning an error-code.
The grabber returns an error when run with --version.
The grabber returns an error when run with --description.
The grabber returns an error when run with --capabilities.
The grabber does not list 'baseline' as one of its supported capabilities.
The grabber does not list 'manualconfig' as one of its supported capabilities.
The specified configuration-file does not exist.
The grabber returned with an error-code when asked to grab data.
The grabber printed something to STDERR even though the --quiet option was used.
The grabber produced different output when called with different combinations of --output and --quiet.
tv_cat returned an error-code when we asked it to process the output from the grabber.
tv_sort found errors in the data generated by the grabber. Probably overlapping programmes.
grabbing data for tomorrow first and then for the day after tomorrow and concatenating them does not yield the same result as grabbing the data for tomorrow and the day after tomorrow at once.
The file is not well-formed XML.
The file does not follow the XMLTV DTD.
No channel-entry found for a channelid that is used in a programme-entry.
More than one channel-entry found for a channelid.
No programme entries were found in the file.
There are no programme entries for one of the channels listed with a channel-entry.
An xmltvid does not look like a proper id, i.e. it does not match /^[-a-zA-Z0-9]+(.[-a-zA-Z0-9]+)+$/.
A programme-entry without an id was found.
A programme entry with an empty or missing title was found.
A programme entry with an invalid start-time was found.
A programme entry with an invalid stop-time was found.
An episode-num with system="xmltv_ns" was found where the episode number did not follow the format described in the Xmltv dtd.
The file contains characters that are unlikely to appear in correctly encoded files. It can be characters that don't have any meaning or control characters that don't appear in correct files often. (like non-breaking space) Another cause is some characters in windows-1252 encoding slipped through into a file encoded as iso-8859-1.
The file contains characters that are unlikely to appear in correctly encoded files. It can be characters that don't have any meaning or control characters that don't appear in correct files often. (like non-breaking space) Another cause is some characters where encoded to utf-8 as if they were iso-8859-1 while they were in fact windows-1252 encoded. Sometimes characters get encoded from iso-8859-1 into utf-8 twice.