XmltvTestCodes - Revision history

Dekarl: add badutf8

2012-05-02T12:56:30Z

add badutf8

Rmeden at 04:23, 12 June 2011

2011-06-12T04:23:01Z

Kingjohnjones at 05:16, 9 June 2011

2011-06-09T05:16:06Z

Dekarl: /* badlatin1 -> badiso8859 */ reword

2010-10-14T07:24:36Z

‎badlatin1 -> badiso8859: reword

Dekarl: add badlatin1 error

2010-10-01T20:39:35Z

add badlatin1 error

Dekarl: /* Test Codes */ linkify module references, notice that the manpages miss the XMLTV:: prefix in the file name but not in the title...

2010-09-02T20:25:43Z

‎Test Codes: linkify module references, notice that the manpages miss the XMLTV:: prefix in the file name but not in the title...

Jamesj at 14:48, 16 July 2008

2008-07-16T14:48:07Z

New page

==Test Codes==

This page documents all errorcodes emitted by test_grabbers and tv_validate_grabber. The descriptions are taken from the documentation of XMLTV::?ValidateGrabber and XMLTV::?ValidateFile.
===noparamcheck===

The grabber accepts any parameter without returning an error-code.
===noversion===

The grabber returns an error when run with --version.
===nodescription===

The grabber returns an error when run with --description.
===nocapabilities===

The grabber returns an error when run with --capabilities.
===nobaseline===

The grabber does not list 'baseline' as one of its supported capabilities.
===nomanualconfig===

The grabber does not list 'manualconfig' as one of its supported capabilities.
===noconfigurationfile===

The specified configuration-file does not exist.
===graberror===

The grabber returned with an error-code when asked to grab data.
===notquiet===

The grabber printed something to STDERR even though the --quiet option was used.
===outputdiffers===

The grabber produced different output when called with different combinations of --output and --quiet.
===caterror===

tv_cat returned an error-code when we asked it to process the output from the grabber.
===sorterror===

tv_sort found errors in the data generated by the grabber. Probably overlapping programmes.
===notadditive===

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.
===notwell===

The file is not well-formed XML.
===notdtd===

The file does not follow the XMLTV DTD.
===unknownid===

No channel-entry found for a channelid that is used in a programme-entry.
===duplicatechannel===

More than one channel-entry found for a channelid.
===noprogrammes===

No programme entries were found in the file.
===channelnoprogramme===

There are no programme entries for one of the channels listed with a channel-entry.
===invalidid===

An xmltvid does not look like a proper id, i.e. it does not match /^[-a-zA-Z0-9]+(.[-a-zA-Z0-9]+)+$/.
===noid===

A programme-entry without an id was found.
===emptytitle===

A programme entry with an empty or missing title was found.
===badstart===

A programme entry with an invalid start-time was found.
===badstop===

A programme entry with an invalid stop-time was found.
===badepisode===

An episode-num with system="xmltv_ns" was found where the episode number did not follow the format described in the Xmltv dtd.

← Older revision		Revision as of 12:56, 2 May 2012
Line 84:		Line 84:
	Another cause is some characters in windows-1252 encoding slipped through into a		Another cause is some characters in windows-1252 encoding slipped through into a
	file encoded as iso-8859-1.		file encoded as iso-8859-1.
		+
		+	===badutf8===
		+	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.

@@ Line 77: / Line 77: @@
 An episode-num with system="xmltv_ns" was found where the episode number did not follow the format described in the Xmltv dtd.
-===badlatin1===
+===badiso8859===
-The file is encoded in iso-8859-1 but contains characters that
+The file contains characters that are unlikely to appear in correctly encoded files.
-have no meaning in iso-8859-1 (or are control characters).
+It can be characters that don't have any meaning or control characters that don't
-A likely cause is some characters in windows-1252 encoding slipped through.
+appear in correct files often. (like non-breaking space)

← Older revision		Revision as of 20:39, 1 October 2010
Line 77:		Line 77:

	An episode-num with system="xmltv_ns" was found where the episode number did not follow the format described in the Xmltv dtd.		An episode-num with system="xmltv_ns" was found where the episode number did not follow the format described in the Xmltv dtd.
		+	===badlatin1===
		+
		+	The file is encoded in iso-8859-1 but contains characters that
		+	have no meaning in iso-8859-1 (or are control characters).
		+	A likely cause is some characters in windows-1252 encoding slipped through.

@@ Line 40: / Line 40: @@
 ===notadditive===
-grabbing data for tomorrow first and then for the day [http://www.pacquiaomarquezfight.com pacquiao vs marquez] after tomorrow and concatenating them does not yield the same result as grabbing the data for tomorrow and the day after tomorrow at once.
+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.
 ===notwell===

@@ Line 1: / Line 1: @@
 ==Test Codes==
-This page documents all errorcodes emitted by test_grabbers and tv_validate_grabber. The descriptions are taken from the documentation of XMLTV::?ValidateGrabber and XMLTV::?ValidateFile.
+This page documents all errorcodes emitted by test_grabbers and tv_validate_grabber. The descriptions are taken from the documentation of {{manpage|ValidateGrabber|3pm}} and {{manpage|ValidateFile|3pm}}.
 ===noparamcheck===