Read the scheme beside the value
The XMLTV project defines xmltv_ns coordinates beginning at zero. An onscreen value serves a different, human-facing purpose. A bare numeric string copied without its scheme loses information needed to interpret it. Keep the complete episode-num context in an authorised investigation.
For an original simple example, structured season index zero and episode index two correspond to season one and episode three in an ordinary one-based display. Adding one again to an already formatted S 01 E 03 label would create an error rather than repair one. The scheme decides which conversion, if any, is appropriate.
Counts do not use the same offset as coordinates
Tvheadend's documentation distinguishes an index from its stated total in slash-separated values. The coordinate is zero-based while the count is a total, so they should not both be incremented. Treating every number in the field identically can create an impossible episode count.
Use the documented parser behaviour for the actual application. A display string and internal season or episode properties can also come from different fields. Comparing only a screenshot with a raw coordinate can miss which value the product deliberately selected for presentation.
Check text overrides before changing data
Tvheadend documents that an onscreen episode value can override its displayed episode text while other parsed properties remain populated. That is a product-specific rule, not a promise that every player handles multiple episode fields identically. Preserve the importer version and supplied fields.
For a mismatch, compare the structured coordinates, any onscreen text and the resulting interface. Ask whether the issue is an expected conversion, a source inconsistency or a product display rule. Do not globally renumber a guide until the relevant relationship is established; the same edit can break another importer that was interpreting the data correctly.
Retain an exact, small example
An authorised source maintainer can reduce the case to one harmless programme record containing the episode fields and enough title context to identify it. Remove private guide URLs and unrelated customer information. Keep the expected and actual displayed result beside the source values.
This article does not claim a real IPTV Australia programme was misnumbered or that a guide import was tested. It explains a documented conversion and one importer's display precedence so that a support enquiry can identify the actual mismatch without erasing valid structured information.
Questions about this guide
Does a zero season index always mean an invalid season?
No. It can be the first season under xmltv_ns.
Should a total after a slash be increased like a zero-based index?
No. The index and the count have different meanings.