[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ft] Change in monochrome rendered font behaviour from 2.5.0.1 to 2.
|
From: |
Werner LEMBERG |
|
Subject: |
Re: [ft] Change in monochrome rendered font behaviour from 2.5.0.1 to 2.5.1 |
|
Date: |
Fri, 12 Jun 2015 08:45:53 +0200 (CEST) |
> Specifically, the change is that monochrome rendered fonts (in small
> sizes for a low resolution display) appear noticeably "worse" unless
> the `FT_LOAD_FORCE_AUTOHINT` option is supplied. It's not clear to
> me if this is a bug or an intended change in behaviour.
It's intentional.
> The following demonstrates the difference in behaviour (when viewed
> with a monospace font) with a 14 pt letter 'e' from
> `DejaVuSansCondensed-Bold.ttf`: [...]
Previously, FreeType used the auto-hinter as soon a glyph doesn't have
instructions. However, this can cause severe problems if a hinted
font intentionally contains some unhinted glyphs that render fine at
all resolutions: If the auto-hinter jumps in, the ascender or
descender values might be completely different, causing uneven lines.
Now it checks whether there are hints at all in the font, and only if
there are none it uses the auto-hinter.
Unfortunately, the DejaVu Sans Condensed Bold font (version 2.34) is
lying: It contains both an `fpgm' and `prep' table, but not a single
glyph is hinted!
The proper solution of course is to fix the font. The second best
solution is to set up a FontConfig rule that enforces auto-hinting for
this font.
Werner