[Pending] Proper handling of Extended event descriptor (1 Viewer)

quba54

Portal Member
November 24, 2007
17
0
Warsaw
Home Country
Poland Poland
Problems:
- if more than one “extended event descriptor” is sent to specific event and text begins with control codes with character table the EPGLanguage.text field contains badly concatenated string. There is no problem when there is only one descriptor for event. But when there is more descriptors each next descriptor text is added with control charactes to EPGLanguage.text field.
- You don’t process item description field (you just skip it). In polish EPG there is info about actors, year etc.
 

Attachments

  • ExtendedEvent_descriptor.patch
    30.7 KB

riksmith

Portal Pro
April 18, 2009
1,856
322
Home Country
Netherlands Netherlands
The item list should not be added to lang.event, if i read correctly this is the name of the event. It think it needs its own field if we are going to implement this.
 

jaobr

Portal Member
November 6, 2006
22
5
Found a bug in the extended event descriptor decoding (tswriter epgdecoder.cpp).

When an EPGLanguage is created the extendedEventComplete property is not initialize (should be set to false).
This leads to that extended event descriptor decoding somtimes works and somtimes the text is skipped.
 

Users who are viewing this thread

Top Bottom