Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1186960" data-attributes="member: 82144">No, we don't agree. Probably one or even both/all of the entries represent valid programs. The problem is that the encoder has failed to encode the start and stop times correctly. Such input is non-compliant. I insist that the XMLTV plugin shouldn't even attempt to deal with the situation. If there are multiple programmes with the same start time, obviously at least one should be kept. However the XMLTV plugin has no idea what to do. That's why I say this problem should be fixed at the source and the XMLTV plugin code should be completely left alone. If there are multiple sources for this problem, all of them should be fixed.No, I disagree again. FixEndTimes (and various other processing) is responsible for determining the stop time when it's not provided (remember that providing the stop time is optional). Therefore such methods will always be needed.</blockquote>

[QUOTE="mm1352000, post: 1186960, member: 82144"] No, we don't agree. Probably one or even both/all of the entries represent valid programs. The problem is that the encoder has failed to encode the start and stop times correctly. Such input is non-compliant. I insist that the XMLTV plugin shouldn't even attempt to deal with the situation. If there are multiple programmes with the same start time, obviously at least one should be kept. However the XMLTV plugin has no idea what to do. That's why I say this problem should be fixed at the source and the XMLTV plugin code should be completely left alone. If there are multiple sources for this problem, all of them should be fixed. No, I disagree again. FixEndTimes (and various other processing) is responsible for determining the stop time when it's not provided (remember that providing the stop time is optional). Therefore such methods will always be needed. [/QUOTE]

Verification