Skip to content

Why Noto Sans Mono is not considered as Monospace? #481

Answered by SpartanJ
beteunam-saram asked this question in Q&A
Discussion options

You must be logged in to vote

Because many monospaced fonts are not actually "pure" monospaced fonts, most of their glyph will be monospaced but not all, so the font file won't be internally flagged as monospace when packaged, and ecode will not be able to take advantage of the fully monospaced font for coordinates calculation. It's not actually that problematic, the alert is slightly exaggerating the situation, I just simply don't recommend using non real monospaced fonts, but it will work just fine.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by beteunam-saram
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #480 on May 24, 2025 13:56.