A compressed XMLTV download contains a guide inside an outer compression format. The player needs to retrieve the bytes, handle that compression and then read the resulting XMLTV document. A failure at any layer can leave the guide empty, but the remedies differ.
The filename can offer a clue without proving the contents. A .gz suffix commonly indicates gzip, while a server response can also use transport-level compression. Inspect the actual arrangement through appropriate local tools or player diagnostics rather than repeatedly changing extensions.

Identify the outer and inner formats
A valid compressed file can contain the wrong inner document. Successful decompression is therefore only one step. The resulting text still needs to be the intended guide, with appropriate channel and programme records for the current dates.
Conversely, a player that accepts plain XML is not thereby proven to accept every archive format. ZIP, gzip and other containers are not interchangeable. Use the application’s documented input support and a source format it actually handles.
Check the import chain
Renaming guide.xml.gz to guide.xml does not decompress it. Likewise, adding .gz to an uncompressed error page does not create a valid compressed guide. The bytes, not the label, determine which operation is appropriate.
- Confirm the expected guide source and compressed format.
- Preserve the original file privately before inspecting it.
- Establish whether decompression succeeds using an appropriate supported method.
- Identify the resulting document and its XMLTV structure.
- Import through the player’s documented route and record the exact outcome.
Keep temporary extraction private
The inner guide can include private source references or other account-related information. An extracted copy deserves the same disclosure care as the original download. Avoid using a public online decompressor merely because it is convenient.
If decompression works but parsing fails, preserve the parser’s exact message and its line or column information when available. That points to the inner document rather than the compression layer. If parsing works but the displayed period is empty, move on to date coverage and channel relationships.
A useful report distinguishes “unsupported compression,” “decompression error,” “unexpected inner document” and “readable guide with missing dates.” Those descriptions give the maintainer a clear next question. Keep conclusions limited to the tested layer; successfully opening an archive does not establish current programme accuracy, account entitlement or playback availability.
Useful answers
Does renaming a gzip file decompress it?
No. The compressed bytes need an appropriate decompression operation.
Does plain XML support prove support for every archive type?
No. Check the importer’s documented formats.
Can decompression succeed while guide import still fails?
Yes. The inner document can be wrong or malformed.