Hi,
I tested new libXft LCD Filtering patch and I got some screenshots to show
too :-)
http://cekirdek.pardus.org.tr/~ismail/tmp/knode-old-lcd-rendering.png
shows the rendering with old LCD rendering patch, its all good there.
04 Eki 2006 Çar 19:45 tarihinde şunları yazmıştınız:
Did you enable the bytecode interpreter in FreeType for the second
example ? It doesn't seem so.
Freetype library did not change between tests ( I am actually just installing
old libXft testing, installing new libXft testing ), so I don't
04 Eki 2006 Çar 20:51 tarihinde, David Turner şunları yazmıştı:
[...]
They're clearly different, look at the shapes of the 2 or 6, especially the
horizontal stems in these glyphs.
I think I understand now. I forgot to mention that you should enable
medium or full hinting in your fonts
Hi David,
04 Eki 2006 Çar 21:04 tarihinde, Ismail Donmez şunları yazmıştı:
04 Eki 2006 Çar 20:51 tarihinde, David Turner şunları yazmıştı:
[...]
They're clearly different, look at the shapes of the 2 or 6, especially
the horizontal stems in these glyphs.
I think I understand now. I
24 Eki 2006 Sal 14:49 tarihinde, David Turner şunları yazmıştı:
Hello everyone,
just to let you know there is a new LCD-filtering patch for Cairo 1.2.4 at:
http://www.mail-archive.com/freetype@nongnu.org/msg00981.html
Got very very good results, unlike libXft patch. Great work.
Regards,
02 Kas 2006 Per 19:00 tarihinde, Mike FABIAN şunları yazmıştı:
I wonder why the results for sub-pixel-hinting differ between
Freetype 2.1.10 and Freetype 2.2.1.20061027 (CVS from 2006-10-27).
The byte code interpreter is compiled in in both versions
of freetype.
Here are two screen shots:
11 Kas 2006 Cts 16:57 tarihinde şunları yazmıştınız:
Attached is a screenshot of kfontviewer showing Verdana Bold at some
sizes. Notice that 2nd and 3rd entries show that N character is badly
displayed.
Confirmed. David's latest changes to the bytecode interpreter (to
make it work the
12 Kas 2006 Paz 16:10 tarihinde şunları yazmıştınız:
For me it works (see attached image). Can you try to find out why
ftview fails?
Maybe a X.org problem I use X.org 7.1, are you using 7.0 or 7.1?
I use 6.9.0.
Problem seems to be DEVICE_X11 is not defined when make is used ( its
15 Kas 2006 Çar 14:39 tarihinde, Ismail Donmez şunları yazmıştı:
Hi,
After I syminked /usr/X11R6 to /usr it all works fine now because
ft2demos/graph/x11/rules.mk detects X11 based on this.
Apparently a symlink is not needed,
make X11_PATH=/usr
works fine.
/ismail
22 Kas 2006 Çar 12:36 tarihinde, Werner LEMBERG şunları yazmıştı:
Currently, I can't debug the fpgm/prep tables with FontForge because
it crashes. Rogier, maybe this information gives you further hints.
It seems that we have wrong assumptions on the storage area, and how
RS/WS interact
25 Kas 2006 Cts 02:10 tarihinde, Werner LEMBERG şunları yazmıştı:
Is the bug supposed to be fixed now?
Yes, it is fixed -- I just tried again.
Becase I can still reproduce with latest CVS.
What exactly can you reproduce? Note that grayscale rendering in the
range 9-16 ppem is
26 Kas 2006 Paz 00:19 tarihinde şunları yazmıştınız:
Uhm I just looked again in kfontview with latest CVS and bold N
character still have the same problem.
What about ftview?
Same in ftview, attached is the screenshot of
ftview -m MENNO ppem ~/buggy-font/verdanab.ttf
Regards,
ismail
27 Kas 2006 Pts 00:23 tarihinde şunları yazmıştınız:
Same in ftview, attached is the screenshot of
ftview -m MENNO ppem ~/buggy-font/verdanab.ttf
Hmrpf. The picture you've sent to the list shows the the
*anti-aliased* version. Just press the `a' key to get the correct
rendering result.
Hi,
I cvs upped freetype2 from savannah repository and I see crashes in
applications that use freetype2. Here is the backtrace:
(gdb) run -v -f
Starting program: /usr/bin/fc-cache -v -f
(no debugging symbols found)
(no debugging symbols found)
/usr/bin/fc-cache: /usr/share/fonts: caching, 0
On Tuesday 15 November 2005 12:36, Werner LEMBERG wrote:
David,
a comparison between a FreeType checkout with -D 2005-10-28 and -D
2005-10-29 shows that the latter has introduced a serious bug
w.r.t. TTF handling. Attached two images from the font Dustismo.ttf.
Perhaps your arithmetic
Hi all,
After I installed Freetype2 from CVS, fontconfig started giving undefined
reference to FT_Free so I tried to recompile fontconfig but it gave the same
error while compiling.
Is this expected i.e FT_Free is no longer public now?
Regards,
ismail
(www.freetype.org)
Ismail Donmez a écrit :
Hi all,
After I installed Freetype2 from CVS, fontconfig started giving undefined
reference to FT_Free so I tried to recompile fontconfig but it gave the
same error while compiling.
Is this expected i.e FT_Free is no longer public now?
Regards,
ismail
Hi all,
Looks like latest cmap commit introduced some new warnings:
freetype2/src/sfnt/ttcmap.c: In function `tt_cmap4_char_map_binary':
freetype2/src/sfnt/ttcmap.c:1036: warning: 'end' might be used uninitialized
in this function
freetype2/src/sfnt/ttcmap.c:1038: warning: 'mid' might be used
Salı 20 Aralık 2005 14:26 tarihinde, Werner LEMBERG şunları yazmıştı:
WARNING: INSTALLING THE CURRENT CVS WILL PROBABLY BREAK YOUR SYSTEM
What do you mean? The rendering results?
Well you will need unreleased Qt,fontconfig etc else you won't be able to
compile anything that links to
Perşembe 2 Şubat 2006 15:32 tarihinde, Graham Asher şunları yazmıştı:
Each sub-pixel value is partly spread out over its two neighbours to
the left and right. I have used this method with the output from
FreeType and it works very well.
Thank you both for explanations! Graham, is your
Perşembe 2 Şubat 2006 12:32 tarihinde, Werner LEMBERG şunları yazmıştı:
David,
your latest changes to the allocation functions and macros break
compilation of FreeType with g++ instead of gcc.
Why would one do that? g++ usually is slower than gcc.
Regards,
ismail
Perşembe 2 Şubat 2006 23:59 tarihinde, Werner LEMBERG şunları yazmıştı:
your latest changes to the allocation functions and macros break
compilation of FreeType with g++ instead of gcc.
Why would one do that? g++ usually is slower than gcc.
Some platforms only ship with a C++ compiler
Hi,
Looks like David forgot to cvs add src/base/ftlcdfil.c to latest CVS. [ I am
looking for testing the new stuff sorry for my impatience =) ]
Regards,
ismail
--
They that can give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety.
-- Benjamin
Hi David et. al.,
I played with FT_CONFIG_OPTION_SUBPIXEL_RENDERING today. I installed latest
freetype from CVS with FT_CONFIG_OPTION_SUBPIXEL_RENDERING enabled. And I
tested libXft + your lcd rendering patch and libXft + newest freetype with
FT_CONFIG_OPTION_SUBPIXEL_RENDERING on.
And with
Hi all,
Recent CVS errors out with :
/home/cartman/CVS/freetype2/objs/.libs/ftlcdfil.o: In function
`FT_Library_SetLcdFilter':
/home/cartman/CVS/freetype2/src/base/ftlcdfil.c:161: multiple definition of
`FT_Library_SetLcdFilter'
04 Eki 2006 Çar 08:13 tarihinde şunları yazmıştınız:
Attached patch shows a rendering problem with 'y' character with
Tahoma font (in python and system ). Notice that top-left part
of y looks cropped. Dpi is 96, and font size is 9 pts. I only see
the problem when italic text is used.
Hi,
In case someone hits this, I cooked up a patch for nvu 1.0. Might be worth to
put in rouge clients page.
Regards,
ismail
--- gfx/src/ps/nsType1.cpp 2002-12-11 08:24:47.0 +0200
+++ gfx/src/ps/nsType1.cpp 2006-10-11 17:17:11.0 +0300
@@ -81,8 +81,8 @@
intwmode;
27 matches
Mail list logo
