Closed GoogleCodeExporter closed 8 years ago
Original comment by stua...@google.com
on 28 Feb 2015 at 12:45
jungshik, could we try this somewhere. I wanted to learn more about hints in fonts/systems
I confirmed this issue with FreeType. See the screenshots below (this has only Latin 'xX', but Cyrilic has the same problem).
With BCI hint ON :
With Hint OFF:
With FT's autohint
@waksmonskiMT : can you talk to your team to fix this issue? Thanks
@marekjez86 : The above screenshots were produced with Freetype's (Freetype demo's) ftview tools. You need to download both freetype2 and ft2demos tarballs and uncompress them side-by-side. Then, build freetype and ft2demos and go to ft2demos/bin. Run
./ftview -m 'xX' 24 <path to a font>
. You can control hinting with 'h' and 'H' key in ftview. Press '?' to see the help.
@BrianKraimerMT FYI.
I confirmed what @davelab6 wrote. Noto Serif Italic 1.03 is fine, but 1.04 has this bug.
ХхΧχXx
Greek (U+03A7; Χ) and Cyrillic (U+0425; Х) have the same problem. Apparently, they're all mapped to the same glyph as Latin 'X'.
Besides, Noto Serif Bold Italic is fine.
There's no difference between cvt, fpgm and gasp tables between 1.03 and 1.04. In the diff of glyf table between 1.03 and 1.04, I didn't find anything that would prevent us from hot-fixing BCI instruction for 'X', either.
1.04 with BCI for 'X' transplanted from 1.03 (everything else unchanged).
1.04 (original)
L: native hint (BCI) Center: auto-hinter R: no hint
Looking at the TTX decompilation, it looks like somehow the hints from "W" (starting in 183 38 1 ...
) got accidentally copied to "X" in 1.04.
@davelab6 Can you update Noto Serif in Google Font to the latest git version?
Original issue reported on code.google.com by
codeman38
on 26 Feb 2015 at 4:49Attachments: