> On 06 Dec 2015, at 20:55, Peter Münster wrote:
>
> On Wed, Dec 02 2015, Klaus Schmidinger wrote:
>
>>> C S19.2E-133-3-263 SVM - GR\326D
>>>
>>> Would it be possible/easy to patch vdr to filter out such errors?
>>> What is the right function to look at?
>>
>> Take a look at StripControlChara
On Wed, Dec 02 2015, Klaus Schmidinger wrote:
>> C S19.2E-133-3-263 SVM - GR\326D
>>
>> Would it be possible/easy to patch vdr to filter out such errors?
>> What is the right function to look at?
>
> Take a look at StripControlCharacters() or cEvent::FixEpgBugs() in epg.c.
It seems, that these f
> On 02 Dec 2015, at 20:45, Peter Münster wrote:
>
> On Sun, Nov 29 2015, Klaus Schmidinger wrote:
>
>> Have you tried this (from the VDR “INSTALL” file)?
>>
>> Workaround for providers not encoding their DVB SI table strings correctly
>
> Thanks, I've tried it. But unfortunately I've got tod
On Sun, Nov 29 2015, Klaus Schmidinger wrote:
> Have you tried this (from the VDR “INSTALL” file)?
>
> Workaround for providers not encoding their DVB SI table strings correctly
Thanks, I've tried it. But unfortunately I've got today this line:
C S19.2E-133-3-263 SVM - GR\326D
with the same 0xD
> On 29 Nov 2015, at 14:04, Peter Münster wrote:
>
> Hi,
>
> It seems, that the encoding of the epg.data file is utf-8, but
> sometimes, there are lines like this:
>
> C S19.2E-133-3-263 18:00 GRÖD - RBS
>
> The "Ö" is one byte (0xD6) that seems not conform to utf-8 encoding.
>
> How could I
Hi,
It seems, that the encoding of the epg.data file is utf-8, but
sometimes, there are lines like this:
C S19.2E-133-3-263 18:00 GRÖD - RBS
The "Ö" is one byte (0xD6) that seems not conform to utf-8 encoding.
How could I avoid such characters in the epg.data file please?
TIA for any hints,
--