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[NumPhras
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
Hello to all UTF-8 user and naturally to others 8 and 7bit user also. ;-)
Please look at http://www.free-x.de/utf8/
The last version of utf8 patch is for vdr 1.4.3 the next version for 1.4.4 will
be soon there.
P.S.
Would be also interesting to know whether someone Antialiasing uses, otherwi
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 t
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://
+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
Hi!
New UTF-8 patch is now available at www.free-x.de/utf8
Changelog:
v.0.1.3 for vdr 1.4.4-3
* Add workaround for buggy freetype libs 2.1.7 - 2.2.1 (segmentation fault)
Enjoy !!!
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi
