Re: [vdr] dxr3 and 1.5.11 antialiasing
Hi, which freetype version/Distribution use you? Some medium fresh FreeType versions have a bug with SPACE symbol 32 DEC. In UTF8 patch for vdr 1.4 there is a workaround for this. Ville Aakko schrieb: Hi Jan, Just in case vdr: [3936] ERROR: FreeType: error during FT_Render_Glyph 32, 3 is not caused by this / VDR does not crash because of that (I'm not getting that error), I've noticed that VDR does not start at all if I enable text2skin. It used to work in vdr-1.5.10 but not in 1.5.11 anymore, VDR just dies if I enable it. In the logs I get this: Nov 18 20:01:35 VillenVDRdevil kernel: em8300_video.o: Video sync rdptr is stuck at 0xdc01, wrptr 0xdcfb, left 250 Nov 18 20:01:35 VillenVDRdevil kernel: em8300_video.o: Video sync timeout And then VDR dies. If I disable it and use skinsoppalusikka instead, everything is OK. It even seems more stable (i.e. as stable as text2skin) than it used to, though I haven't done extensive testing yet. I'm on Gentoo, though. I'm having strange problems there with my dxr3 and VDR-1.5.10 that other people on other distros don't. This could be one of those. - Ville ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.5.3 - issue with translations out of plugins
Hi All, hi Klaus, here is a patch for this problem: --- /home/riedel/GENS/orig-vdr/vdr-1.5.3.orig/i18n.c2007-06-09 10:44:54.0 +0200 +++ /home/riedel/GENS/orig-vdr/vdr-1.5.3/i18n.c 2007-06-11 23:40:43.0 +0200 @@ -6820,7 +6820,7 @@ *Converted = new tI18nPhrase[NumPhrases + 1]; memset(*Converted, 0, sizeof(tI18nPhrase) * (NumPhrases + 1)); } - if (!(*Converted)[NrPhrase][NrLanguage]) { + if (!(*Converted)[NrPhrase][NrLanguage] Original[NrPhrase][NrLanguage] ) { cCharSetConv csc(Phrases[1][NrLanguage], cCharSetConv::SystemCharacterTable()); (*Converted)[NrPhrase][NrLanguage] = strdup(csc.Convert(Original[NrPhrase][NrLanguage])); } Now work it for other Languages, for example with OSDLanguage = 16 Klaus Schmidinger wrote: On 06/10/07 21:43, Joachim Wilke wrote: Hi Klaus, I just installed vdr-1.5.3, but lcdproc plugin caused vdr to crash on startup. I figured out that the problem is the translation of the string Volume . Unlike the other strings that are used by the plugin this string is provided by the vdr-core i18n.c This worked fine in vdr-1.5.1. Adding a dummy translation of Volume directly in the plugins i18n.c fixed the crash. Is this the intended behaviour? Or was this a feature by accident? ;-) This was certainly unintended. I'll look into it. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Utf8-patch experiences, anyone?
Harald Milz schrieb: Freetype. And IMHO the Arial font looks better on the OSD than the original VDR font, but that's a matter of taste I guess. You can always replace it by another TTF if you like. exact ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Utf8-patch experiences, anyone?
Hi Marko, last debian or freetype has problems with utf8 patch. I know. :-/ Version for 1.4.4 will fix it. You can try older freetype versions or wait. Und also link to German wiki: http://www.vdr-wiki.de/wiki/index.php/Utf8-patch Marko Mäkelä schrieb: On Mon, Dec 04, 2006 at 09:36:58PM +0100, Alexander Riedel wrote: Hi Marko, built-in bitmap Fonts in vdr are not uniform. Those must be first exchanged. UTF8 user found Freetype fonts better than built-in. Size is scallable. I see. I gave the patch a try. After all, the only added dependence on my system seems to be libfreetype6{,-dev}. Marko Mäkelä schrieb: For one, I fear that Freetype could use too much processing power. Secondly, I would expect the rendered glyphs to look bad in the interlaced output of vdr -P'softdevice -vo dfb:mgatv' (TV output of Matrox G450). try out simply, i use DXR3 and meine frends FF cards. Unfortunately, it caused a segmentation fault or something strange in iconv_close() in CharSetConv(), called from ConvertPhrases(). When I started it in gdb or quickly attached gdb during the initialization, there was no crash, but a hang or a signal (SIGTERM if I remember correctly), varying from time to time. When I started vdr standalone as vdr -l1, it crashed in SIGSEGV. Valgrind didn't reveal anything either; it just appeared hung. The only error in the logs related to your patch was this one: ERROR: FreeType: an error occurred during FT_Render_Glyph I see that the iconv functions are part of GNU libc. I'm using version 2.3.6. The compiler version is gcc (GCC) 4.1.2 20061028 (prerelease) (Debian 4.1.1-19). The crash occurred on both vdr 1.4.2 and 1.4.3. On 1.4.2, there was one trivial reject: the disabling of the UTF-8 check. On 1.4.3, the patch applied cleanly. The only other patches are the patch of vdr-subtitles-0.3.11 (http://www.virtanen.org/vdr/subtitles/) and this patch of mine: http://www.ktverkko.fi/~msmakela/software/vdr/vdr-1.4.0-suspend-0.4.3.patch.gz I run vdr in LANG=fi_FI, charset iso-8859-1 (locale does not say it, but it definitely is 8859-1 or 8859-15). Marko ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Utf8-patch experiences, anyone?
Hi Marko, built-in bitmap Fonts in vdr are not uniform. Those must be first exchanged. UTF8 user found Freetype fonts better than built-in. Size is scallable. Marko Mäkelä schrieb: For one, I fear that Freetype could use too much processing power. Secondly, I would expect the rendered glyphs to look bad in the interlaced output of vdr -P'softdevice -vo dfb:mgatv' (TV output of Matrox G450). try out simply, i use DXR3 and meine frends FF cards. Do you have any thoughts on this? How hard would it be to combine all VDR font bitmaps to one that would use Unicode Basic Multilingual Plane? Presumably, it would have to be a sparse data structure, since most code points of the BMP are not present in the bitmap fonts nor used by DVB-T senders. Marko PS: I saw one Russian (or Bulgarian or some Cyrillic) and one German comment being added by vdr-1.4.3-utf8-0.1.3-rc1.diff.gz. Maybe it would be better to translate them into English. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr