Tune/adjust FreeType rendering parameters |
||||
Issue descriptionIn bug 646635, FreeType was updated to 2.7 which introduced a new 'hinting' mode and made it the default. To avoid an unexpected change in a 54 branch, I turned off that explicitly. We need to evaluate and consider turning it on. Moreover, now that CFF and Truetype renderer can support 'horizontal stem only hinting' even with built-in hinting, we also have to experiment with it for Roboto and Noto CJK. Going to autohint is also an option, but we need to be careful. See https://github.com/googlei18n/noto-fonts/issues/750#issuecomment-251034599 BTW, not everybody likes a new default hinting mode in FreeType 2.7. See bug 649362
,
Oct 10 2016
One more tuning parameter (there's a bug already on this) for CFF fonts is stem-darkening. It's ON at the moment.
,
Nov 8 2017
FreeType 2.8.1 now has a new 'rendering' mode called 'Harmony' when FT_CONFIG_OPTION_SUBPIXEL_RENDERING is undefined. Currently, it is defined, but we may consider undefining to get a new behavior when subpixel rendering is on (low res).
Below is an excerpt from ChangeLog:
This is a new technology for LCD-optimized rendering. It capitalizes
on the fact that each color channel grid is shifted by a third of a
pixel. Therefore it is logical to render 3 separate monochrome
bitmaps shifting the outline by 1/3 pixel, and then combine them.
Importantly, the resulting output does not require additional LCD
filtering.
* src/smooth/ftsmooth.c (ft_smooth_render_generic)
[!FT_CONFIG_OPTION_SUBPIXEL_RENDERING]: Implement new LCD-optimized
rendering.
,
Nov 8 2017
,
Nov 8 2017
It would be interesting to see if this helps with issue #740385 .
,
Mar 21 2018
,
Sep 28
Triage nag: This Chrome OS bug has an owner but no component. Please add a component so that this can be tracked by the relevant team.
,
Nov 8
<UI triage> Bug owners, please add the appropriate component to your bug. Thanks!
,
Nov 9
|
||||
►
Sign in to add a comment |
||||
Comment 1 by js...@chromium.org
, Oct 10 2016