Re: IMPORTANT! Re: [ft] Problem with Verdana Bold

2006-11-24 Thread Ismail Donmez
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

2006-11-24 Thread Werner LEMBERG

 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: [ft] rendering changes 2.1.10 - 2.2.1

2006-11-24 Thread David Turner
Hello Gordon,

thanks for the clarification; it seems that you're saying that:

A) light hinting now produces fuzzy glyphs
B) medium hinting used to provide better output that previously

well, first of all, A) is purely intentional since we modified the
algorithm to get results that are consistently closer to the original
shapes than previously. The result is indeed fuzzier, though this is
minimized when using proper LCD filtering. This is also more or less
equivalent to what you get on Mac OS X

for B), I'm quite surprised because the algorithm for medium hinting
in FreeType didn't really change between these two versions. Besides,
I'm more interested in knowing what you think about the current CVS
hinting changes

Hope this helps,

- David Turner
- The FreeType Project  (www.freetype.org)


On Thu, 16 Nov 2006 08:33:27 -0800, Gordon Messmer [EMAIL PROTECTED] said:
 David Turner wrote:
  There are indeed differences in the auto-hinter between various
  FreeType releases, since we try to enhance it incrementally (and
  this will be true for the next release, by the way, which should
  treat serif fonts much better, try the CVS if you want).
 
 I'll give that a shot soon.
 
  I fail to see exactly what the problem is; you're not even providing
  screenshots nor telling what is wrong, only that things are different.
 
 OK, I didn't describe the problem, as I perceive it, until the end. 
 where Medium hinting used to provide very pleasing results, it
 now seems to squish characters vertically, and they're fuzzy
 
 I've included a set of screenshot selections showing the Gnome terminal 
 using Courier and Luxi Mono.  In each shot, the upper terminal is using 
 freetype 2.2.1, and the lower one is using 2.1.10.  In the best 
 contrast shots, both appear identical.
 
 In Courier-12-BestShapes, the fonts in the upper terminal look fuzzy. 
 Magnify the word Monospace in the image.  You can see clearly in the 
 'M', 'n' and 'p' characters in the lower terminal have good, solid 
 vertical stems.  They're one pixel wide and relatively solid in color. 
 In the upper terminal, those characters have two-pixel wide stems that 
 fade into the black background.  This difference makes them appear very 
 fuzzy.  All of the characters in the upper terminal appear fuzzy, 
 regardless of whether or not they have vertical lines.  The old 
 rendering model did a better job, here, with medium hinting.
 
 In LuxiMono-10-BestShapes, the fonts in the upper terminal appear fuzzy, 
 again.  Vertical stems tend to be more faded in color, where they used 
 to be bright.  The 'g' character also looks vertically squished where it 
 used to have a well rounded shape.
 
 I can provide more shots, with different fonts, if you'd like.  In 
 general, though, all of the fonts that I look at appear to look better 
 with medium hinting in 2.1.10.
 
 Is there an easier way to test various hinting levels?  I don't see 
 options within ftview to do anything other than turn hinting on or off...
 
 Thanks for looking at this.
 


___
Freetype mailing list
Freetype@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype