Projekt infosat2vdr - Revision history

Joachim: /* Source */

2009-04-30T11:15:11Z

Source

← Older revision		Revision as of 11:15, 30 April 2009
Line 9:		Line 9:
	== Source ==		== Source ==

	[http://banzhaf.~~ath~~.cx/hg/infosat2vdr Mercury repository]		[http://banzhaf.homeip.net/hg/infosat2vdr Mercury repository]

	== Why another epg source? ==		== Why another epg source? ==

Joachim: /* infosat2epg */

2007-07-23T16:40:32Z

infosat2epg

← Older revision		Revision as of 16:40, 23 July 2007
Line 1:		Line 1:
	= ~~infosat2epg~~ =		= infosat2vdr =
	This project aims to make fully automatic epg updates for vdr via the infosat datastream.		This project aims to make fully automatic epg updates for vdr via the infosat datastream.

Joachim: Projekt infosat2epg moved to Projekt infosat2vdr: typo

2007-07-23T16:40:17Z

Projekt infosat2epg moved to Projekt infosat2vdr: typo

← Older revision	Revision as of 16:40, 23 July 2007
(No difference)

Joachim: /* Source */

2007-07-23T16:39:46Z

Source

← Older revision		Revision as of 16:39, 23 July 2007
Line 9:		Line 9:
	== Source ==		== Source ==

	[http://banzhaf.ath.cx Mercury repository]		[http://banzhaf.ath.cx/hg/infosat2vdr Mercury repository]

	== Why another epg source? ==		== Why another epg source? ==

Joachim at 16:38, 23 July 2007

2007-07-23T16:38:02Z

← Older revision		Revision as of 16:38, 23 July 2007
Line 6:		Line 6:

	if you want to help, see the open topics below		if you want to help, see the open topics below

			== Source ==

			[http://banzhaf.ath.cx Mercury repository]

	== Why another epg source? ==		== Why another epg source? ==

Joachim: /* Problems */

2007-07-23T16:25:24Z

Problems

← Older revision		Revision as of 16:25, 23 July 2007
Line 13:		Line 13:

	== Problems ==		== Problems ==
	* Get the infosat data ~~<br>~~		* Get the infosat data
	* Merge the infosat data with channels own data ~~<br>~~		* Merge the infosat data with channels own data

	== Architecture ==		== Architecture ==

Joachim: /* Problems */

2007-07-23T16:25:09Z

Problems

← Older revision		Revision as of 16:25, 23 July 2007
Line 13:		Line 13:

	== Problems ==		== Problems ==
	- Get the infosat data <br>		* Get the infosat data <br>
	- Merge the infosat data with channels own data <br>		* Merge the infosat data with channels own data <br>

	== Architecture ==		== Architecture ==

Joachim: /* Architecture */

2007-07-23T16:24:55Z

Architecture

← Older revision		Revision as of 16:24, 23 July 2007
Line 22:		Line 22:
	Last but not least: import and export of epg data should be modular, too. It should be possible to read epg data via vdr socket, read the vdr's epg.data file, read enigma's epg data (how?) read it from infosat, xml or an sql database. Export should be possible in various formats as well.		Last but not least: import and export of epg data should be modular, too. It should be possible to read epg data via vdr socket, read the vdr's epg.data file, read enigma's epg data (how?) read it from infosat, xml or an sql database. Export should be possible in various formats as well.
	As soon as the epg data is read from more than one source, it should be possible, to define priorities. Each import module should implement some parsing, to provide subtitles, episode numbers, actors, ... The merging should be based on those fields. I want to be able to use episode title from one source and subtitle from another. For each column, I want to be able to specify different priorities for the data sources (in case both sources provide the same level: concatenate them)		As soon as the epg data is read from more than one source, it should be possible, to define priorities. Each import module should implement some parsing, to provide subtitles, episode numbers, actors, ... The merging should be based on those fields. I want to be able to use episode title from one source and subtitle from another. For each column, I want to be able to specify different priorities for the data sources (in case both sources provide the same level: concatenate them)

			== Open topics ==
			* Manage streams and files with glibmm
			* Manage sockets for glibmm streams
			* Implement commandline parsing with glibmm options
			* provide wrapper for buggy infosatepg executable (or better yet: reimplement it as a lib - lower prio)

Joachim: /* infosat2epg */

2007-07-23T16:20:35Z

infosat2epg

← Older revision		Revision as of 16:20, 23 July 2007
Line 1:		Line 1:
	= infosat2epg =		= infosat2epg =
	This project aims to make fully automatic epg updates for vdr via the infosat datastream.		This project aims to make fully automatic epg updates for vdr via the infosat datastream.


	== Status ==		== Status ==
Line 7:		Line 6:

	if you want to help, see the open topics below		if you want to help, see the open topics below



	== Why another epg source? ==		== Why another epg source? ==
Line 14:		Line 11:
	Unfortunately, the quality is lacking. Some channels do not send epg at all, some only now/next, others do not categorize, send incomplete descriptions or no subtitles or no episode numbers.		Unfortunately, the quality is lacking. Some channels do not send epg at all, some only now/next, others do not categorize, send incomplete descriptions or no subtitles or no episode numbers.
	Infosat in most cases provides better data for german channels. I want to use that data as much as possible, while retaining the channels own epg where necessary.		Infosat in most cases provides better data for german channels. I want to use that data as much as possible, while retaining the channels own epg where necessary.


	== Problems ==		== Problems ==

Joachim: /* Problems */

2007-07-23T16:19:57Z

Problems

← Older revision		Revision as of 16:19, 23 July 2007
Line 17:		Line 17:

	== Problems ==		== Problems ==
	- Get the infosat data		- Get the infosat data <br>
	- Merge the infosat data with channels own data		- Merge the infosat data with channels own data <br>


	== Architecture ==		== Architecture ==