It's intentional.
Thanks for clarifying that and for your explanation. Is this covered
in the Changelog somewhere?
No. The feature itself was announced for 2.4.5 as
- If autohinting is not explicitly disabled, FreeType now uses the
autohinter if a TrueType based font doesn't
f == follower follo...@rancidbacon.com writes:
f It seems like the instructions are intentionally disabled
f due to Condensed's experimental status:
The instructions are disabled because the condensed fonts are
algorithmically narrowed, and the code can't also adjust the
instructions to match.
Hi,
Thanks for your reply.
On 11 June 2015 at 23:45, Werner LEMBERG w...@gnu.org wrote:
It's not clear to me if this is a bug or an intended change in behaviour.
It's intentional.
Thanks for clarifying that and for your explanation. Is this covered
in the Changelog somewhere?
Unfortunately,
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
Hi,
I've encountered a change in behaviour which I've narrowed down to
being between libfreetype6 version 2.5.0.1 and 2.5.1 (I originally
encountered the issue moving code from 2.4.8 2.5.2 and can confirm
the new behaviour continues in 2.6).
Specifically, the change is that monochrome rendered
