On Saturday 27 August 2011 01:18:31 Tony Houghton wrote:
On Fri, 26 Aug 2011 20:42:38 +0100
Laz laz@club-burniston.co.uk wrote:
I thought it had been doing this scrambling when I tried it earlier in the week but have now proved it to myself.
Time to start adding some more printfs...
The first byte of encoded strings should be 0x1f, followed by 1 or 2 indicating which table should be used (one is optimised for titles, the other for descriptions). "Normal" strings either start with a printable character for the default character set or a code < 0x20 indicating the character set. I use eepg too, but I haven't noticed it scrambling anything (this is probably the first time I've looked at QVC's schedule though ;)).
Over the evening, it scrambled more and more channels!
:-s
Thanks for the pointer to 0x1f! Now I know where to look.
(I assume that eepg only decodes EPG that comes in "over the air" and doesn't touch any EPG alread stored.)
Laz