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
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. Werner ___ 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
Uhm I just looked again in kfontview with latest CVS and bold N character still have the same problem. What about ftview? Werner ___ 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: IMPORTANT! Re: [ft] Problem with Verdana Bold
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. Werner ___ Freetype mailing list Freetype@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype
Re: IMPORTANT! Re: [ft] Problem with Verdana Bold
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'. Werner ___ Freetype mailing list Freetype@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype
Re: IMPORTANT! Re: [ft] Problem with Verdana Bold
On 11/14/06, Werner LEMBERG [EMAIL PROTECTED] wrote: 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. Bad news: The bug in verdanab is *not* related to the recent updates in the bytecode interpreter (which are now disabled temporarily). It is already present in 2.1.10. I did as much investigation as my time allowed. This error happens with my TrueTypeViewer as well. As far as I can see, my interpreter skips over some vital Delta instructions in N because store[2] != 6. store[2] happens to be 1. (I've got no idea what the value in store[2] stands for.) Hope this helps, Rogier ___ Freetype mailing list Freetype@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype
IMPORTANT! Re: [ft] Problem with Verdana Bold
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. Bad news: The bug in verdanab is *not* related to the recent updates in the bytecode interpreter (which are now disabled temporarily). It is already present in 2.1.10. David, do you have time to investigate? Werner ___ Freetype mailing list Freetype@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype
Re: IMPORTANT! Re: [ft] Problem with Verdana Bold
I don't have much time at the moment, though I just finished a large commit spree recently. Even though I'd like to investigate this problem in parallel with the enhancement bugs we have in the interpreter, I really feel we should prepare for a new release before that. OK. PS: By the way, I sent three emails to the devel list a few days ago that never went through. I have been unsusbcribed again ? Yep. Werner ___ Freetype mailing list Freetype@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype
Re: IMPORTANT! Re: [ft] Problem with Verdana Bold
I don't have much time at the moment, though I just finished a large commit spree recently. Even though I'd like to investigate this problem in parallel with the enhancement bugs we have in the interpreter, I really feel we should prepare for a new release before that. More on this later, - David PS: By the way, I sent three emails to the devel list a few days ago that never went through. I have been unsusbcribed again ? On Tue, 14 Nov 2006 09:48:27 +0100 (CET), Werner LEMBERG [EMAIL PROTECTED] said: 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. Bad news: The bug in verdanab is *not* related to the recent updates in the bytecode interpreter (which are now disabled temporarily). It is already present in 2.1.10. David, do you have time to investigate? Werner ___ Freetype mailing list Freetype@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype ___ Freetype mailing list Freetype@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype
