-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Variable font version could not display some symbols #296
Comments
Comment deleted because I was completely off. Sorry for the confusion. |
I use Google's font tool to dump its cmap. (googlefonts/fonttools: A library to manipulate font files from Python.) <cmap>
<tableVersion version="0"/>
<cmap_format_4 platformID="0" platEncID="3" language="0">
<!-- some maps -->
<map code="0x25c6" name="uni25C6"/><!-- BLACK DIAMOND --> Now I am confused. |
Those characters are in the font and look fine in some apps, but I see them disappear in other apps. What system and software are you using where they don't show up? |
Actually, something very weird happened and a bunch of those glyph outlines disappeared. My local build is totally fine so we will be doing a new release soon that will fix this. |
Windows 10 version 19042.867 In Microsoft Edge (Chromium version), change font to Noto Sans CJK SC VF in settings -> appearence -> custom fonts Change font-family by developer tools to Source Han Sans SC VF: Change font-family by developer tools to Source Han Sans SC: Andorid 11 <!-- some family -->
<family lang="zh-Hans">
<font weight="100" style="normal" index="3">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="100.0" />
</font>
<font weight="300" style="normal" index="3">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="300.0" />
</font>
<font weight="350" style="normal" index="3">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="350.0" />
</font>
<font weight="400" style="normal" index="3">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="400.0" />
</font>
<font weight="500" style="normal" index="3">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="500.0" />
</font>
<font weight="700" style="normal" index="3">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="700.0" />
</font>
<font weight="900" style="normal" index="3">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="900.0" />
</font>
<!-- serif font -->
</family>
<family lang="zh-Hant,zh-Bopo">
<font weight="100" style="normal" index="4">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="100.0" />
</font>
<font weight="300" style="normal" index="4">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="300.0" />
</font>
<font weight="350" style="normal" index="4">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="350.0" />
</font>
<font weight="400" style="normal" index="4">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="400.0" />
</font>
<font weight="500" style="normal" index="4">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="500.0" />
</font>
<font weight="700" style="normal" index="4">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="700.0" />
</font>
<font weight="900" style="normal" index="4">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="900.0" />
</font>
<!-- serif font -->
</family>
<family lang="ja">
<font weight="100" style="normal" index="1">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="100.0" />
</font>
<font weight="300" style="normal" index="1">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="300.0" />
</font>
<font weight="350" style="normal" index="1">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="350.0" />
</font>
<font weight="400" style="normal" index="1">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="400.0" />
</font>
<font weight="500" style="normal" index="1">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="500.0" />
</font>
<font weight="700" style="normal" index="1">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="700.0" />
</font>
<font weight="900" style="normal" index="1">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="900.0" />
</font>
<!-- serif font -->
</family>
<family lang="ko">
<font weight="100" style="normal" index="2">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="100.0" />
</font>
<font weight="300" style="normal" index="2">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="300.0" />
</font>
<font weight="350" style="normal" index="2">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="350.0" />
</font>
<font weight="400" style="normal" index="2">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="400.0" />
</font>
<font weight="500" style="normal" index="2">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="500.0" />
</font>
<font weight="700" style="normal" index="2">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="700.0" />
</font>
<font weight="900" style="normal" index="2">NotoSansCJK-VF.ttc
<axis tag="wght" stylevalue="900.0" />
</font>
<!-- serif font -->
</family>
<!-- some family --> In Google Pinyin Method |
@punchcutter In my case it is the autohinter that caused the disappearance of the glyphs. From my observation, the glyph would disappear when the outlines of the two masters are the same (but I do see a few exceptions). |
@tamcy Thanks for confirming that. I recently found the bug in |
- Variable font STAT table ranges were updated to display correctly on Windows. Issue [#291](#289) - Variable font postscript names were updated to display correctly on macOS 11. Issue [#291](#289) - Added missing CID+37953 to Korean Subset. Issue [#289](#289) - Glyphs with missing outlines were corrected. Issue [#296](#296)
- Variable font STAT table ranges were updated to display correctly on Windows. Issue [#291](#289) - Variable font postscript names were updated to display correctly on macOS 11. Issue [#291](#289) - Added missing CID+37953 to Korean Subset. Issue [#289](#289) - Glyphs with missing outlines were corrected. Issue [#296](#296)
- Variable font STAT table ranges were updated to display correctly on Windows. Issues [#190](#190) and [#291](adobe-fonts/source-han-sans#289) - Variable font postscript names were updated to display correctly on macOS 11. Issue [#291](adobe-fonts/source-han-sans#289) - Added missing CID+37953 to Korean Subset. Issue [#289](adobe-fonts/source-han-sans#289) - Glyphs with missing outlines were corrected. Issue [#296](adobe-fonts/source-han-sans#296)
- Variable font STAT table ranges were updated to display correctly on Windows. Issues [#190](#190) and [#291](adobe-fonts/source-han-sans#289) - Variable font postscript names were updated to display correctly on macOS 11. Issue [#291](adobe-fonts/source-han-sans#289) - Added missing CID+37953 to Korean Subset. Issue [#289](adobe-fonts/source-han-sans#289) - Glyphs with missing outlines were corrected. Issue [#296](adobe-fonts/source-han-sans#296)
- Variable font STAT table ranges were updated to display correctly on Windows. Issues [#190](#190) and [#291](adobe-fonts/source-han-sans#289) - Variable font postscript names were updated to display correctly on macOS 11. Issue [#291](adobe-fonts/source-han-sans#289) - Added missing CID+37953 to Korean Subset. Issue [#289](adobe-fonts/source-han-sans#289) - Glyphs with missing outlines were corrected. Issue [#296](adobe-fonts/source-han-sans#296)
Fixed in 2.004 |
Prerequisites
Description
[Please provide here a thorough description of the issue, being sure to specify at least a Unicode code point if it affects a character or a particular glyph for a character. Including the character itself after the Unicode code point also helps, for visual reasons. Images with annotations that pinpoint the issue also help. If you are referencing standards, please keep in mind that they may have known or unknown errors. It is not necessary to provide CIDs.]
Thanks to @AokiFuru simonsmh/notocjk#25.
⚽ (U+26BD), ● (U+25CF), ■ (U+25A0), ◆ (U+25C6), ▲ (U+25B2), ▶ (U+25B6), ▼ (U+25BC), ◀ (U+25C0), ♠ (U+2660), ♥ (U+2665), ♣ (U+2663), ♦(U+2666), ❖ (U+2756), ✚ (U+271A), ✿ (U+273F), ◢ (U+25E2), ◣ (U+25E3), ◤ (U+25E4), ◥ (U+25E5)
Those were displayed correctly in super OTC version.
The text was updated successfully, but these errors were encountered: