On 04/16/08 14:45, Matthias Schwarzott wrote:
> On Mittwoch, 16. April 2008, Soeren Sonnenburg wrote:
>> Dear List,
>> I am desperately trying to get the german umlauts going for both vdr
>> receiving EPG information (out of the air directly from the channels...)
>> and via epg4vdr 0.5
>> http://www.wontorra.net/article.php?story=20050429181815661
>> I've noticed that standard EPG has the correct encoding, but only the
>> one from epg4vdr has not. However the pulled .xml files still have the
>> right (i.e. utf-8) encoding.
>> Only when this information is transferred to vdr (I guess via SVDRP)
>> umlauts and everything is distorted. Also then the dumped epgdata file
>> contains wrongly encoded parts...
>> Any ideas what I could do about this?
> I guess you need to know the encoding your vdr runs with, and then use this 
> for the SVDRP connection.
> For future VDR development I still think it could be useful to:
> 1. Either add a header for epg data (and other places where vdr exchanges 
> texts) telling the encoding.

The only reasonable thing IMO would be to make an SVDRP command (or extend an
existing one) that tells which encoding is used by this VDR. Maybe an extended
signon message would be ok, like

220 video SVDRP VideoDiskRecorder 1.7.1; Sat Apr 19 11:43:27 2008; ISO-8859-1

I wouldn't like to fiddle around with headers in many places.

> 2. or switch all external interfaces (epg.data, svdrp, channels.conf) to utf8.

Not going to happen - my systems all run with ISO-8859-1 ;-).

> 3. going even further, switch vdr so that it internally only uses utf8 (or 
> utf16 if one can tell that is easier - I doubt). So all code that does 
> switch/case on the charset can be simplified.

VDR currently uses the codeset that is used on the system. If it is UTF-8,
all is done in UTF-8.

You'll always have to be careful when exchanging data between systems
that use different codesets.


vdr mailing list

Reply via email to