Change the hint setting for Noto (hinted) and Roboto to hint_slight |
||||
Issue descriptionNoto (hinted) and Roboto are hinted in such a way that horizontal stems are grid-fitted while vertical stems are left alone to be faithful the original outline. (similar to light-auto-hint mode). Recent versions of FreeType now work with 'hinting=true, hintstyle=hintslight'. How Blink/Skia treats that setting needs to be checked, though.
,
Sep 13 2016
Let's give it a try.
,
Sep 13 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 13 2017
Obsolete given recent FreeType changes. |
||||
►
Sign in to add a comment |
||||
Comment 1 by derat@chromium.org
, Aug 31 2016This is what we're using right now (from third_party/chromiumos-overlay/media-libs/fontconfig/files/local.conf), right? <match target="font"> <test name="noto_hinted"><bool>true</bool></test> <edit name="hinting" mode="assign"><bool>true</bool></edit> <edit name="autohint" mode="assign"><bool>false</bool></edit> <edit name="hintstyle" mode="assign"><const>hintfull</const></edit> <edit name="antialias" mode="assign"><bool>true</bool></edit> </match> <!-- Roboto is BCI-hinted for widely used LGC characters --> <match target="font"> <test name="family"><string>Roboto</string></test> <edit name="hinting" mode="assign"><bool>true</bool></edit> <edit name="autohint" mode="assign"><bool>false</bool></edit> <edit name="hintstyle" mode="assign"><const>hintfull</const></edit> <edit name="antialias" mode="assign"><bool>true</bool></edit> </match> Is the proposed change just switching hintstyle from hintfull to hintslight? Are there before-and-after screenshots? And is there any relation to issue 633377 ("Repeated Arial/Arimo 'f' characters are ugly due to subpixel positioning")? Does this have a risk of causing a similar issue for Noto (hinted) and Roboto?