Australia Network

Hi Kristian,
 
I made a new australianetwork.com siteini . http://www.webgrabplus.com/sites/default/files/download/ini/info/zip/Networks_australianetwork.com.zip Indeed the site was completely changed. Because the different regions are set by changing the timezone value in the ini file you probably need to adapt it. There are a few files with info how to do that. It relies on the timezone functionality of the latest beta 1.1.1/53.16 http://www.webgrabplus.com/sites/default/files/patchexe_prebuild_2.zip , so you need that as well.
 
Next I will have a look at Deutsche Welle
 
Jan

Kristian

as promissed , DeutscheWelle : http://www.webgrabplus.com/sites/default/files/download/ini/info/zip/Networks_dw.de.zip

As with AustraliaNetwork it needs the last beta 53.16, in this case because the times are in UTC

Re your idea http://webgrabplus.com/content/repository-collected-inis-specific-global-channels-epg-channels-tab :

I am sorry but I don't understand what you mean by:

So if the specific sites are devleoped, then I think it would very useful for those that like more detail in their EPG and their provider provdes those channels, to use the specific web sites and just modify the TIME reference to match.

Can you be a bit more specific about what you want? Also, how are we to know what kind of details are provided by Cable providers? 

Jan

Kristian,

thanks, now I understand your point!

I think I need to explain how the times (start and stop) in xmltv are defined and how these times are used to get the correct ones for a user anywhere in the world.
In fact this is not a special WG++ issue but rather how these thing are specified in the xmltv standard.

- the times in xmltv are - always - in UTC! Xmltv allows several formats , the one WG++ uses :  guidedatetime+/-offset or  yyyyMMddhhmmss +/-hhmm . The guidedatetime is the one that wg++ grabs from the tvguide website. The offset is the actual timezoneoffset wrt UTC for the guidedatetime.
Example: suppose the guidedatetime is 5 may 2014 10:15 for a tvguide in Hong Kong , then the xmltv time would list as 20140505101500 +0800 The offset is +0800 because the 5 may 2014 10:15 is 8 hours later than the UTC time of it. So in fact the same time in xmltv could also be expressed as 20140505021500 +0000 or any other combination of time and offset as long as the result is the same time in UTC.

- Daylightsaving times: xmltv has no special listing of dst changeover dates. It simply relies on the offset. So if the guidedatetime must be expressed after a dst changeover, the offset must again reflect the actual offset wrt UTC. Most tvguidesites list their programs in 'local wall clock' times. And that is a difficulty that WG++ has to adress, because this local wall clock time must be converted in UTC, or which comes down to the same, the actual UTC offset needs to be figured out. Prior to the latest beta version, it did that by using the standard timezone utc offset, as specified in the siteini, (like timezone=UTC+08:00 in the case of Hongkong) and simply asuming that the dst changeover date is the same for the guidedatetime as for the computer on which WG++ runs. In most cases that works well (if the user of WG++ lives in the same timezone as the one for the guidedatetime). But that fails of course if the user lives in an area where the dst changeover is on a different date. It also fails if the tvguide site lists the programs in UTC (no dst!!) and not in 'local wall clock'.
With the latest beta that problem is solved. The timezone in the ini can now be entered as a timezone_id, like timezone=Asia/Hong_Kong , and the buildin timezones database calculates the actual UTC offset from the internatioanal timezone rules which are a part of that database. So in case of HongKong it will not apply any DST changeover because HongKong doesn't use DST in 2014..

- How about the timedifference for a user living in another timezone than that of the guidedatetime? This has to be taken care of by the xmltv importer of the PVR software. This was always the case and is not changed with the latest beta .

So, concluding, all WG++ siteini's can be used anywhere in the world , Without the latest beta there were a few limitations: For sites that are listed in UTC times and for user living in a timezone wit a different dst changeover date than the tvguidesite.

So these 'global' , mostly network tvguide sites can also be used by anyone anywhere. There are quite a few of them in the 'network' section and a few more in the 'international' section.

Does this answer your question?

Jan

Hi Kristian,

Part of the exessive logging is due to a debug switch I seem to have left in DW. Open the ini and locate the following line:

title.scrub {single(debug)|<div id="bodyContent">|<h1>|</h1>|</h1>}

change that into;

title.scrub {single()|<div id="bodyContent">|<h1>|</h1>|</h1>}

I will have a look at the rest of the logging some time, but I don't think that there is anything serious. Its mostly due to differences between index_title and title.

Jan

Hi k. 

two issues:

1. The gabs in Austaralia network: The ini relies on the duration given on the site, assuming these are correct! But they aren't!! Have a look at:

http://www.australianetwork.com/tvguide and compare the starts + duration with the starts of the next program. Very messy!!

I think it is better to simply disable the duration lines in the ini, the stop time of a show then becomes the start of the next. So add a * to the two lines that start with index_duration, like this:

*index_duration.scrub {single|<p class="duration">||mins|</p>}
*index_duration.modify {calculate(format=timespan,hours)|60 /}

2. I noticed there is a debug swith in merge_xmltv.ini :

index_showsplit.modify {substring(debug type=regex)|"(.+channel=\"'index_variable_element'\">.+)"}

It doesn't harm but it fills your logfile with a lot of unnecessary lines.

You better remove the word debug from that line.

Jan

Which region are you using or do you want to use? Did you follow the instructions in australianetwork.com_howto_set_the_regions.txt ?
(You didn't include the ini, so I can't see you timezone setting)
 
Jan