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
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
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.
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
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
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
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
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
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
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.
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 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,
-
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
Werner LEMBERG wrote:
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?
It probably was built on a system that didn't
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.
Werner
___
Freetype mailing list
Freetype@nongnu.org
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
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
17 matches
Mail list logo
