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
> render
> 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 rendere
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,
isma
> 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
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
> 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 `ga
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 int
> 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 (
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,
- Dav
> 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 t
11 matches
Mail list logo
