Re: IMPORTANT! Re: [ft] Problem with Verdana Bold
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 verdana-ftview.png Description: PNG image ___ Freetype mailing list Freetype@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype
Re: IMPORTANT! Re: [ft] Problem with Verdana Bold
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. I can only repeat that this font cannot be rendered correctly in anti-aliased mode within the range 9-16 ppem. Yes its rendered correctly when not anti-aliased. Regards, ismail ___ Freetype mailing list Freetype@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype
Re: IMPORTANT! Re: [ft] Problem with Verdana Bold
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 *unusable* with this font! You have to follow the recommendations from the `gasp' table. Uhm I just looked again in kfontview with latest CVS and bold N character still have the same problem. Regards, ismail ___ Freetype mailing list Freetype@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype
Re: IMPORTANT! Re: [ft] Problem with Verdana Bold
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 with the CVT. George provided a quick patch, so I was able to debug it. I have found the problem, which is something completely different: Function #84 (defined in the fpgm table) in font verdanab.ttf (version 2.40) is called as the last subroutine in the prep table. Within the function, the GETINFO instruction is called to find out whether we do grayscaling. If yes, storage[2] is set to 1 and to 0 otherwise. The gasp table indicates that you must not use gray scaling in the range 9-16, so everything is fine. However, verdanab.ttf exhibited two bugs in FreeType, which I've now fixed: . `tt_loader_init' never reset `exec-grayscale' properly because a wrong constant has been used in a comparison. . A change from mono to grayscale rendering (and vice versa) requires a re-execution of `tt_face_load_prep'. Is the bug supposed to be fixed now? Becase I can still reproduce with latest CVS. Regards, ismail ___ Freetype mailing list Freetype@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype
Re: [ft] ftview and X.org
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 ___ Freetype mailing list Freetype@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype
Re: [ft] Problem with Verdana Bold
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 defined in Jamfile ) so that grNewSurface() fails. Regards, ismail ___ Freetype mailing list Freetype@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype
Re: [ft] Problem with Verdana Bold
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 same as the Windows rasterizer) are still buggy. AFAIK, he hasn't fixed this yet. Thanks for confirming. I can't get ftview to work: [~/CVS/ft2demos/bin] ./ftview pppem ~/buggy-font/verdanab.ttf could not allocate display surface error = 0x 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? Regards, ismail ___ Freetype mailing list Freetype@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype
Re: [ft] sub-pixel-hinting of ft 2.2.1 and ft 2.1.10 differs
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: http://lisa.goe.net/~mfabian/freetype2-luxi-mono-sub-pixel-hinting-problem/ luxi-mono-sub-pixel-hinting-ft-2.1.10.png http://lisa.goe.net/~mfabian/freetype2-luxi-mono-sub-pixel-hinting-problem/ luxi-mono-sub-pixel-hinting-ft-2.2.1.20061027.png Hmm I know Suse switched to new LCD rendering for for libXft so I guess this is the same issue I reported[1] , solution is to use old libXft LCD rendering patch. [1] http://www.nabble.com/Testing-new-LCD-rendering-mode-tf2382905.html Regards, ismail ___ Freetype mailing list Freetype@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype
Re: [ft] updated LCD filtering patch
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, ismail ___ Freetype mailing list Freetype@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype
Re: [ft] Testing new LCD rendering mode
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 forgot to mention that you should enable medium or full hinting in your fonts preference dialog. That's because light hinting will now always invoke the auto-hinter (with the exception of fonts which require the unpatented hinter to load properly, e.g. MingLiU). I believe it should remove the difference you see. If not, send more screenshots :-) Sadly I still see problems: http://cekirdek.pardus.org.tr/~ismail/tmp/knode-new-lcd-filtering-fullhinti ng.png I added following to ~/.fonts.conf ( actually changed hintmedium to hintfull so it was already using medium hinting ) and run fc-cache after : match target=font edit mode=assign name=hintstyle consthintfull/const /edit /match Its been sometime without comment on this, do you think my setup is buggy or is there some another problem? Regards, ismail ___ Freetype mailing list Freetype@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype
[ft-devel] [PATCH] nvu 1.0 does not compile with Freetype 2.2
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;
} FT2PT1_info;
-static int cubicto(FT_Vector *aControlPt1, FT_Vector *aControlPt2,
- FT_Vector *aEndPt, void *aClosure);
+static int cubicto(const FT_Vector *aControlPt1, const FT_Vector *aControlPt2,
+ const FT_Vector *aEndPt, void *aClosure);
static int Type1CharStringCommand(unsigned char **aBufPtrPtr, int aCmd);
static int Type1EncodeCharStringInt(unsigned char **aBufPtrPtr, int aValue);
@@ -173,7 +173,7 @@
}
static PRBool
-sideWidthAndBearing(FT_Vector *aEndPt, FT2PT1_info *aFti)
+sideWidthAndBearing(const FT_Vector *aEndPt, FT2PT1_info *aFti)
{
int aw = 0;
int ah = 0;
@@ -216,7 +216,7 @@
}
static int
-moveto(FT_Vector *aEndPt, void *aClosure)
+moveto(const FT_Vector *aEndPt, void *aClosure)
{
FT2PT1_info *fti = (FT2PT1_info *)aClosure;
FT_UShort upm = fti-face-units_per_EM;
@@ -253,7 +253,7 @@
}
static int
-lineto(FT_Vector *aEndPt, void *aClosure)
+lineto(const FT_Vector *aEndPt, void *aClosure)
{
FT2PT1_info *fti = (FT2PT1_info *)aClosure;
FT_UShort upm = fti-face-units_per_EM;
@@ -279,7 +279,7 @@
}
static int
-conicto(FT_Vector *aControlPt, FT_Vector *aEndPt, void *aClosure)
+conicto(const FT_Vector *aControlPt, const FT_Vector *aEndPt, void *aClosure)
{
FT2PT1_info *ftinfo = (FT2PT1_info *)aClosure;
FT_UShort upm = ftinfo-face-units_per_EM;
@@ -311,7 +311,7 @@
}
static int
-cubicto(FT_Vector *aControlPt1, FT_Vector *aControlPt2, FT_Vector *aEndPt,
+cubicto(const FT_Vector *aControlPt1, const FT_Vector *aControlPt2, const FT_Vector *aEndPt,
void *aClosure)
{
FT2PT1_info *ftinfo = (FT2PT1_info *)aClosure;
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel
[ft] Testing new LCD rendering mode
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. http://cekirdek.pardus.org.tr/~ismail/tmp/knode-new-lcd-filtering.png shows the rendering with new LCD filtering patch, notice that the blurriness of the font makes it look bad especially when its bold, also notice there are color fringes which looks like the case for vanilla libXft + enabling subpixel hinting. Test Environment: 8pt Tahoma, 96 dpi I downloaded libXft-2.1.7 and applied patch libXft-2.1.7-lcd-filter-2.patch . Thoughts? P.S: Example application used is KNode. Regards, ismail ___ Freetype mailing list Freetype@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype
Re: [ft] Testing new LCD rendering mode
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 think thats the problem but I agree it just looks like that indeed. Regards, ismail ___ Freetype mailing list Freetype@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype
Re: [ft] Testing new LCD rendering mode
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 preference dialog. That's because light hinting will now always invoke the auto-hinter (with the exception of fonts which require the unpatented hinter to load properly, e.g. MingLiU). I believe it should remove the difference you see. If not, send more screenshots :-) Sadly I still see problems: http://cekirdek.pardus.org.tr/~ismail/tmp/knode-new-lcd-filtering-fullhinting.png I added following to ~/.fonts.conf ( actually changed hintmedium to hintfull so it was already using medium hinting ) and run fc-cache after : match target=font edit mode=assign name=hintstyle consthintfull/const /edit /match P.S: Thanks for working on these amazing set of patches. My eyes owe a lot to you. Regards, ismail ___ Freetype mailing list Freetype@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype
Re: [ft-devel] Rendering problem with 'y' character
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. Which tahoma font have you used? I only have normal and bold, but no slanted version. I have the following : 212bc6614bb04a673ce8b93656c1dccb3415b54f tahomabd.ttf 28bde5b328ae7e9dade8e5e9d405210578e4d52a tahoma.ttf Does anyone know if this is a problem in KDE/Qt or a known problem? And how to debug this better? Can you reproduce the bad behaviour with ftview? I am not _yet_ able to reproduce with ftview, I am wondering khtml/Qt does font substition somehow although I set Konqueror to use Tahoma only. Regards, ismail ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
[ft-devel] Recent CVS does not compile
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' /home/cartman/CVS/freetype2/objs/.libs/ftbase.o:/home/cartman/CVS/freetype2/src/base/ftlcdfil.c:161: first defined here If ftlcdfil.c include is removed from src/base/ftbase.c it compiles successfully. But I am not sure if its the right fix. Regards, ismail ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
[ft-devel] Missing ftlcdfil.c
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 Franklin ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
[ft-devel] Playing with FT_CONFIG_OPTION_SUBPIXEL_RENDERING
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 the latter I get very poor results compared to the libXft + your lcd rendering patch combination. So I wonder if libXft should be modified to take advantage of FT_CONFIG_OPTION_SUBPIXEL_RENDERING or freetype does not yet enable it? Sorry if it this code not meant to be tested yet, in that case please ignore this mail. Regards, ismail -- They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] ClearType like rendering
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 code open in some way? No, I'm sorry. I was paid to write it for a commercial company. By the way, when I said Each sub-pixel value is partly spread out over its two neighbours to the left and right I meant two neighbours on the left and two on the right - that is, the filter spreads the value over five pixels in total. Thank you Graham, I will look into this. Regards, ismail ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] compiling of FT CVS with g++ is broken
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 ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] compiling of FT CVS with g++ is broken
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 by default (you might ask Nelson Beebe for details). Ah I see. Regards, ismail ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] ft-smooth for 2.1.10?
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 freetype. Regards, ismail ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
[ft-devel] New warnings
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 uninitialized in this function freetype2/src/sfnt/ttcmap.c: In function `tt_cmap12_char_map_binary': freetype2/src/sfnt/ttcmap.c:2049: warning: 'end' might be used uninitialized in this function freetype2/src/sfnt/ttcmap.c:2050: warning: 'mid' might be used uninitialized in this function Regards, ismail ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] serious bug introduced 2005-10-29
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 performance improvents are buggy... This might also be the cause for the strange Vera rendering issues. I am seeing many bad artifacts with Tahoma.ttf from Windows installation. I was thinking optimization would break Qt but I guess it breaks more. Regards, ismail ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
[ft-devel] Freetype CVS fontconfig
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 ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Freetype CVS fontconfig
On Tuesday 15 November 2005 23:18, you wrote: Hello, FT_Free was *never* public. You should upgrade your fontconfig to a more recent version, since it must include the necessary patch to get rid of all FT2 internals dependencies. Regards, - David Turner - The FreeType Project (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 ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
[ft-devel] Freetype2 cvs crashes
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 fonts, 2 dirs /usr/bin/fc-cache: /usr/share/fonts/truetype: caching, 0 fonts, 3 dirs /usr/bin/fc-cache: /usr/share/fonts/truetype/mac: Program received signal SIGSEGV, Segmentation fault. tt_cmap4_next (cmap=0x597d30) at ttcmap.c:742 742 FT_UInt gindex = FT_NEXT_USHORT( p ); (gdb) print gindex (gdb) print p $1 = (FT_Byte *) 0x2aabab3f91da Address 0x2aabab3f91da out of bounds (gdb) print *p Cannot access memory at address 0x2aabab3f91da (gdb) Regards, ismail -- They say people don't believe in heroes anymore ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
