[vdr] Premiere UTF-8 fix for VDR 1.5.1+
Hi all,
Here is a small patch for all Premiere watchers who want to use UTF-8
encoding.
The patch simply changes the default character set that is used when
no encoding is broadcasted.
Kind regards,
Stefan
--- libsi/si.c.orig 2007-06-28 14:37:28.0 +0200
+++ libsi/si.c 2007-06-28 14:35:45.0 +0200
@@ -340,5 +340,6 @@
// and length are adjusted accordingly.
static const char *getCharacterTable(const unsigned char *buffer, int length, bool *isSingleByte = NULL) {
- const char *cs = ISO6937;
+ // const char *cs = ISO6937;
+ const char *cs = ISO8859-15;
if (isSingleByte)
*isSingleByte = false;
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] softdevice with menuaudio but no video
Stefan Lucke wrote: Quoting Darren Wilkinson: Torgeir Veimo wrote: On 27 Jun 2007, at 18:32, Darren Wilkinson wrote: The problem is that although I can hear the channel playing and I can see and use the vdr menus using softdevice I can't view the actual program wether or not it's live or recorded. Ae you using Xv output? It's prob the wrong colour key used for the overlay. Search the softdevice devel for a fix. --Torgeir Veimo [EMAIL PROTECTED] I forgot to mention that I'm using DirectFB only. And you forgot to mention which hardware you are using. With DirectFB we need hardware YUV - RGB conversion support. Plain fb output mode should run on any hw, but requires some more CPU power. Stefan Lucke I'm using nvidiafb with a GF 6600. However normal framebuffer is also showing menus but no video. Also shouldn't colourspace errors mean I get no menus either? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-ttxtsubs in vdr developer versions?
Rolf Ahrenberg wrote: On Wed, 27 Jun 2007, Luca Olivetti wrote: I just commented out these lines and it seems to work (though lately I'm not using it very much). Thank you Luca it works if i comment out four lines in ttxtsubsdisplay.c. Well, I guess it only works if your VDR is using the same charset as the teletext subtitling stream. How do I see if the charset is the same? I am not able see any Swedish characters (åäöÅÄÖ) in subtitles but it works in VDR. Any clue? I don't have any channels with teletext subtitles and haven't used the plugin for years. However, if someone is keen enough to make a real fix and send it to me, I can update my patches... BR, -- rofa I appreciate your work with the patches, here in Sweden both DVB-S and DVB-T uses teletext subtitles and it's very important to have it working. Thank you for making the patches even if you don't use them. /Svankan ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [vdr-1.5.5][Patch] inc/dec chara cter not working for ÄÖÜ in non-UTF8
Hi Klaus,
Found a bug in VDR-1.5.5 in non-UTF8 mode. In any text field, when the
cursor is on an uppercase non-ASCII character like ÄÖÜ, the up/down key
jumps directly to A.
The core problem is that the non-UTF8 version of Utf8ToArray
sign-extends chars to uints, turning the ä of the allowed chars into
0xFFE4, while the towlower() of the edit control changes the Ä into
0x00E4, which is then not in the list of allowed characters.
Lowercase works, since here everything stays sign-extended.
The attached patch changes Utf8ToArray to properly extend chars as unsigned.
Cheers,
Udo
--- vdr-1.5.5-orig/tools.c 2007-06-23 15:38:30.0 +0200
+++ vdr-1.5.5/tools.c 2007-06-28 21:10:58.0 +0200
@@ -685,7 +685,7 @@
int n = 0;
while (*s --Size 0) {
if (cCharSetConv::SystemCharacterTable())
- *a++ = *s++;
+ *a++ = (unsigned char)(*s++);
else {
int sl = Utf8CharLen(s);
*a++ = Utf8CharGet(s, sl);
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Premiere UTF-8 fix for VDR 1.5.1+
On 06/28/07 15:41, Stefan Taferner wrote:
Hi all,
Here is a small patch for all Premiere watchers who want to use UTF-8
encoding.
The patch simply changes the default character set that is used when
no encoding is broadcasted.
Kind regards,
Stefan
--- libsi/si.c.orig 2007-06-28 14:37:28.0 +0200
+++ libsi/si.c2007-06-28 14:35:45.0 +0200
@@ -340,5 +340,6 @@
// and length are adjusted accordingly.
static const char *getCharacterTable(const unsigned char *buffer, int
length, bool *isSingleByte = NULL) {
- const char *cs = ISO6937;
+ // const char *cs = ISO6937;
+ const char *cs = ISO8859-15;
if (isSingleByte)
*isSingleByte = false;
Well, this might cause problems on channels that do adhere to the
standard and actually broadcast their EPG data in ISO6937.
Maybe somebody should call Premiere and complain to them. After all,
it's them who are not following the standard ;-)
Klaus
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Premiere UTF-8 fix for VDR 1.5.1+
On 06/28/07 21:53, Luca Olivetti wrote: En/na Klaus Schmidinger ha escrit: Well, this might cause problems on channels that do adhere to the standard and actually broadcast their EPG data in ISO6937. Maybe somebody should call Premiere and complain to them. After all, it's them who are not following the standard ;-) Unfortunately they're not the only one :-( Maybe some broadcasters aren't even aware that they are not adhering to the DVB standard. So let's all call them and tell them about it. The more people call and complain, the better the chances things get fixed (at least that's what I'd hope for ;-). Building workarounds into receivers is certainly not the right way to go (even though it is, of course, a quick fix and may be sufficient for some users). Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] softdevice with menuaudio but no video
Stefan Lucke wrote: Quoting Darren Wilkinson: Torgeir Veimo wrote: On 27 Jun 2007, at 18:32, Darren Wilkinson wrote: The problem is that although I can hear the channel playing and I can see and use the vdr menus using softdevice I can't view the actual program wether or not it's live or recorded. Ae you using Xv output? It's prob the wrong colour key used for the overlay. Search the softdevice devel for a fix. --Torgeir Veimo [EMAIL PROTECTED] I forgot to mention that I'm using DirectFB only. And you forgot to mention which hardware you are using. With DirectFB we need hardware YUV - RGB conversion support. Plain fb output mode should run on any hw, but requires some more CPU power. Stefan Lucke This looks so very similar to the problem which occured to me some 2 months ago (similar hardware and video output method): http://lists.berlios.de/pipermail/softdevice-devel/2007q2/002841.html As I didn't have too much time to look for the cause, I'm still at vdr-1.4.6 and using xineliboutput (working well), but now that I've catched up with reading few things on the ML which seems interesting to me, I'll soon try the latest vdr-1.5 as it now supports UTF8. Lucian Muresan ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] gettext in 1.5.x (was: vdr-1.5.3 - issue with translations out of plugins)
Hi Klaus, Klaus Schmidinger wrote: On 06/13/07 00:21, [EMAIL PROTECTED] wrote: unfortunately this patches do not fix Transtation problems complete. i still have segmentation faults for example with softdevice plugin. maybe this help: vdr has translation none. softdevice as also none. at this translation none have i core dumps... Well, it was just a quick shot. I'll look into it over the weekened. Klaus what about gettext? This ist better alternative to Home-made converting. In the long run this is the plan, but as a first step I wanted to do the freetype and UTF-8 stuff separately. Or minimaly without on the fly converting of i18n strings, these string use from the begin as utf8 strings. If you remeber the thread almost 2 years ago, OSD language settings stored as language code (was: i18n.c sorted) http://linvdr.org/mailinglists/vdr/2005/11/msg00646.html at that time you first found it a good idea, then postponed it for 1.5.x. Right after that I also developed a working gettext patch based on this one, and of course, Alexander Riedel's UTF8-patch as it looked like at that time. Now you integrated utf8/freetype in vanilla VDR yourself, and from what I've read (haven't tried or looked at the code yet) it seems you used at least parts of that UTF8 ideas. What plans do you have about gettext, how long would that run be? Would it make sense if I'd rework my gettext patch based on the current VDR developer version in the near future (I developed it exactly having in mind your sketched ideas fom that time There would be one file for each language in VDR itself, and each plugin would also have its own set of language files. There will also be a way of converting the exiting i18n files into the new format. ). Interested (in the next weeks, not right now...)? Lucian ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
