Bug 1609239
| Summary: | [gnome-terminal] The default Google Noto CJK fonts are not listed in the preference menu. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bhushan Barve <bbarve> | ||||
| Component: | fontconfig | Assignee: | Akira TAGOH <tagoh> | ||||
| Status: | NEW --- | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rawhide | CC: | ajax, alexl, bbarve, caillon+fedoraproject, debarshir, egmont, fonts-bugs, gnome-sig, i18n-bugs, john.j5live, lijli, mclasen, pnemade, pwu, rhughes, rstrode, sandmann, tagoh | ||||
| Target Milestone: | --- | Keywords: | FutureFeature, i18n | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | Type: | Bug | |||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Bhushan Barve
2018-07-27 10:56:35 UTC
gnome-terminal 3.28 only offers you monospace fonts. I think it might require further investigation why Google Noto CJK is not believed to be a monospace font by the pango_font_family_is_monospace() function – if it actually is. Alternatively, the change in gnome-terminal could be reverted if there's a good reason, and if the aforementioned function is not safe to rely on. Until then, as a workaround you can set any font using dconf-editor (or command-line dconf) under /org/gnome/terminal/legacy/profiles:/:<profile_id>/font. Created attachment 1471422 [details]
noto CJK fonts not available for selection in gnome-terminal
just tried the following workaround for testing on gnome-terminal (and emacs which apparently is checking spacing property in the code). run fc-cache to apply and didn't see any side-effects so far:
<fontconfig>
<match target="scan">
<test name="family"><string>Noto Sans Mono CJK JP</string></test>
<edit name="spacing" mode="append"><const>dual</const></edit>
</match>
<match target="scan">
<test name="family"><string>Noto Sans Mono CJK KR</string></test>
<edit name="spacing" mode="append"><const>dual</const></edit>
</match>
<match target="scan">
<test name="family"><string>Noto Sans Mono CJK SC</string></test>
<edit name="spacing" mode="append"><const>dual</const></edit>
</match>
<match target="scan">
<test name="family"><string>Noto Sans Mono CJK TC</string></test>
<edit name="spacing" mode="append"><const>dual</const></edit>
</match>
</fontconfig>
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'. How about newer releases? This still persists in f31. I didn't make any changes in fonts side. and still in discussion to improve determining spacing property in fontconfig. Shouldn't this be reassigned to something in the text stack instead of gnome-terminal? gnome-terminal just uses pango_font_family_is_monospace to deal with it. Pango depends on spacing property in fontconfig. So reassigning to fontconfig. This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle. Changing version to 35. |