id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc	mlocked
1035	EIT rewrite	Stuart Auchterlonie	danielk	"This ISN'T a wishlist. This is what we need to do
to rewrite the EIT handling for 0.20

#778 - Astra 19.2E EPG aka. remove Kristian Kalweit fix

#892 - Handling channels with high EIT data rates.

#913 - Handling of EIT data with additional data

#1025 - Handling of unicode characters within EIT data.


Split all eitFixup routines out of siparser. Use them
on EIT data only after we have decided that this is
new/updated information.

Keep track of which events we have sent to the database.
ie. do our own caching of EIT data, getting rid of that
currently done for events in siparser (also #943)
(!GreyFoxx has done most of this already)

EIT data prioritization. which is better EIT or xmltv?
Within EIT, lower table numbers always seem to be better
data. 0x4e & 0x4f now & next, 0x50 & 0x51 future, 0x60 & 0x61
far future, and other longer term EIT data from various
providers

Fixup routines sometimes try and put a subtitle in the DB that
exceeds the length of the subtitle field in the DB, so silent
truncation of information occurs."	task	closed	minor	0.21	eit	head	medium	fixed			0