View Single Post
Old 10-26-2024, 12:19 AM   #4
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,063
Karma: 169810634
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
For what it may be worth, the Noto Sans Mono fonts have glyphs that do not fit the fixed width. A check using fc-scan does not show the expected spacing = 100 for a monospaced font. Using FontForge under Windows under Font Information => OS/2 => Panose => Proportion does not show Monospaced.

There have been quite a few discussions about how QT decided a font is monospaced and issues with the Noto San Mono fonts.

If anyone is suffering from insomnia, you can check Noto Sans Mono doesn't declare spacing property on GitHub especially the last comment.

And continuing on, this item from QT's bugs: Qt fails to consider dual-width fonts mono with fontconfig.

Last edited by DNSB; 10-26-2024 at 12:30 AM. Reason: Added link to GitHub discussion
DNSB is offline   Reply With Quote