* Source Han Sans and Noto Sans CJK are basically the same font. Info:
http://blog.typekit.com/2014/07/15/introducing-source-han-sans/
Which program triggers the problem? Specify the filename if possible.
Using Windows' font viewer (fontview.exe), BabelMap (BabelMap.exe)
What steps will reproduce the problem?
0. Enable gdipp service.
1. Install Region-specific Subsets fonts for Source Han Sans / Noto Sans CJK
2. Preview those fonts in font viewer
What is the expected output? What do you see instead?
Expected result:
The preview window pops up instantly and characters are shown.
Actual result:
The preview window pops up very slowly. Sometimes Windows says it is not
responding. In the end no characters are shown.
Video of the slow loading: http://gfycat.com/ConsiderateCommonCurassow
(It is showing Source Han Sans but it applies to Noto Sans too)
Pic of the final result: https://i.imgur.com/fJzIBqB.png
Disabling gdipp services eliminates the issue.
What version of gdipp (including renderer)? On which operating system?
gdipp_x64_0.9.1.msi. Win8.1 pro 64bit with all updates installed.
Please provide any additional information below. Screenshots always help.
Affected Fonts:
SourceHanSansCN-1.000.zip
SourceHanSansJP-1.000.zip
SourceHanSansKR-1.000.zip
SourceHanSansTWHK-1.000.zip
(from http://sourceforge.net/projects/source-han-sans.adobe/files/)
and Noto Sans variants:
NotoSansSChinese.zip
NotoSansJapanese.zip
NotoSansKorean.zip
NotoSansTChinese.zip
(from http://www.google.com/get/noto or
https://code.google.com/p/noto/source/browse/third_party/noto_cjk)
Fonts NOT affected: SourceHanSansOTF-1.000.zip, NotoSansCJK-Regular.otf (and
possibly other weights)
The affected fonts actually works in common usage, e.g. LibreOffice, Adobe
Photoshop. However, I cannot use it in BabelMap
(http://www.babelstone.co.uk/Software/BabelMap.html) as it works similarly as a
font preview program.
Cross Reference:
https://github.com/adobe-fonts/source-han-sans/issues/8
https://code.google.com/p/noto/issues/detail?id=65
Original issue reported on code.google.com by Fanol...@gmail.com on 17 Jul 2014 at 12:10
Original issue reported on code.google.com by
Fanol...@gmail.comon 17 Jul 2014 at 12:10