Difference between revisions of "User:Dekarl"
From XMLTV
(start collecting notes for a Best Practice sheet) |
m (→Potential Data Sources: link to notes on grabbers for xmltv files) |
||
Line 32: | Line 32: | ||
= Potential Data Sources = | = Potential Data Sources = | ||
+ | Candidates for wrapping into [[User:Dekarl/Static_File_Grabber_Template|Static File Grabbers]] | ||
* _cz_arcao: XMLTV export from [http://xmltv.arcao.com/ arcao.com]. Provides explicit time offsets. | * _cz_arcao: XMLTV export from [http://xmltv.arcao.com/ arcao.com]. Provides explicit time offsets. | ||
* _dk_ontv: XMLTV export from [http://ontv.dk/xmltv/ ontv.dk]. | * _dk_ontv: XMLTV export from [http://ontv.dk/xmltv/ ontv.dk]. | ||
* _eu_phazer: XMLTV service from tvprofil.net aka [http://tvprofil.net/xmltv/ Phazer XMLTV Service]. Notice that they provide timestamps in their local time as floating time which is intepreted as UTC... | * _eu_phazer: XMLTV service from tvprofil.net aka [http://tvprofil.net/xmltv/ Phazer XMLTV Service]. Notice that they provide timestamps in their local time as floating time which is intepreted as UTC... | ||
+ | * _fr_kazer: XMLTV service from [http://kazer.org/ kazer.org]. | ||
* _it_ambrosa: XMLTV export from [http://www.ambrosa.net/index.php/contents/XMLTV.html ambrosa.net]. Explicit about non-commercial use only. | * _it_ambrosa: XMLTV export from [http://www.ambrosa.net/index.php/contents/XMLTV.html ambrosa.net]. Explicit about non-commercial use only. | ||
* _ru_teleguide: XMLTV export from [http://www.teleguide.info/article1.html teleguide.info]. Provides explicit time offsets. | * _ru_teleguide: XMLTV export from [http://www.teleguide.info/article1.html teleguide.info]. Provides explicit time offsets. |
Revision as of 20:05, 12 April 2011
Contents
Known Issues with Character Encoding
- Need to verify that we can dump perl strings at XMLTV::Writer and it will do the right thing with regard to escaping anything outside $encoding into XML entities.
- tv_grab_hr tv_grab_no_gfeed tv_grab_se_swedb fix commited upstream
- #1910245 should add a test for HTML entities in the generated XML. (hint ´ is invalid XML!)
Issues with Time Zones
- tv_grab_dk_dr DST issues
- tv_grab_il DST issues
- tv_grab_it DST issues
- tv_grab_pt_meo DST issues
- tv_grab_uk_bleb DST issues, floating start>stop leads to wrong date calculation and time offsets
Memory Leaks??
- #2612996 tv_grab_na_dtv dumps core on windows as .exe, grows quite as perl
Cleanup List
Feel free to take anything from the list
- #1880681 the bug was solved (not a bug), the suggestion for Supplementary Files is turning one can of worms into another...
- tv_grab_huro has no maintainer?
- #2748362 site changes: holes in the collected programs
- #2837668 site changes: unexpected hash references
- #2858285 close it, was "no channels found", the grabber does not fail completely anymore (see status)
- #2910015 close it, was "no programs on channel 1", test_grabbers tests with that channel succesful
Cleanup SourceForge Project
- remove group/status/category examples from the tracker (might check for other unused stuff while there)
Check for Breakage caused by LWP::Simple
- silent uncompression
- silent code page conversion
- silent proxy handling
Maybe it's best to move most uses over to our own Get_nice.
Potential Data Sources
Candidates for wrapping into Static File Grabbers
- _cz_arcao: XMLTV export from arcao.com. Provides explicit time offsets.
- _dk_ontv: XMLTV export from ontv.dk.
- _eu_phazer: XMLTV service from tvprofil.net aka Phazer XMLTV Service. Notice that they provide timestamps in their local time as floating time which is intepreted as UTC...
- _fr_kazer: XMLTV service from kazer.org.
- _it_ambrosa: XMLTV export from ambrosa.net. Explicit about non-commercial use only.
- _ru_teleguide: XMLTV export from teleguide.info. Provides explicit time offsets.
Configuration API
- [1] possible extensions/clarifications from a consumers POV
- list in the supplementary files mapping DVB/ATSC id to grabber/channel. Then let --list-channels & co. enrich channel list with related ids
Data Sinks
- Check [2] and see if all are mentioned here
Best Practices
Consumers of XMLTV Data
- be prepared that xmltv ids really might be similar to FQDN (255 characters max.) the longest I've seen in the wild is 69 characters (_es_laguiatv)