Closed sdbbs closed 2 years ago
Is it possible you are using an older version of the fonts? In that case this might be a case of font substitution by the system and are the spaces from a different font perhaps.
Box drawing glyphs were added to IBM Plex Mono version 2.3 which was released in September last year.
I’m unfamiliar with the applications in question and don’t have access to a Linux installation to check if this issue can be reproduced.
Thanks, @BoldMonday :
Is it possible you are using an older version of the fonts?
Could be, I'm not sure; that is why I included the output of fc-scan
- it only says: fontversion: 131137(i)(s)
, but I'm not sure how to translate/understand that; it doesn't look like the semver strings used here (e.g. latest release currently is tagged v6.0.0)
In that case this might be a case of font substitution by the system and are the spaces from a different font perhaps.
Box drawing glyphs were added to IBM Plex Mono version 2.3 which was released in September last year.
Indeed, there seems to be font substitution - I've found:
... Gucharmap will display the origin font when you right-click on a glyph.
... and this is what I get for BOX DRAWINGS LIGHT DOWN AND LEFT
in IBM Plex Mono:
So yeah, in my case, that character's glyph is actually delivered by DejaVu Sans ...
Then again, I still don't see why that fact would have influence on the width of the spaces preceding that character ...
I thought there might exist "hidden font commands" that do this when a glyph is rendered, and so I suspected the IBM Plex Mono font - but it looks like, the problem originates somewhere else (maybe in the glyph substitution engine?)
In any case, if there are any other suggestions to debug this, I'd appreciate it!
Could be, I'm not sure; that is why I included the output of fc-scan - it only says: fontversion: 131137(i)(s), but I'm not sure how to translate/understand that; it doesn't look like the semver strings used here (e.g. latest release currently is tagged v6.0.0)
I have no idea how to interpret that long version number either. It’s not how we define that field when developing fonts.
A note about versions: this repository uses release numbers (such as 6.0) everytime new fonts are added or when existing fonts are changed. The fonts themselves contain individual font version numbers (such as 2.3 for the latest Plex Mono). Because not all fonts change with every new release.
In any case, if there are any other suggestions to debug this, I'd appreciate it!
I recommend to get the latest version of Plex Mono from this repository. That should fix the problem. And perhaps file a bug report to the maintainers of the applications in question. It’s definitely font substitution that is creating unexpected results.
Just discovered this, I'm on Ubuntu 20.04 Mate, and can see this with IBM Plex in both
scite
andgeany
.Basically, if I use normal characters, then when I type SPACE, it is a normal space - here
scite
, View/Whitespace is on, spaces are indicated by very small central dots, font size (via mouse scrollwheel) to the max:Now, let's paste in
┐
, that is,BOX DRAWINGS LIGHT DOWN AND LEFT
:Well - now the spaces before the
┐
got reduced in width?! For a monospaced font?Same happens also in
geany
- but I do not get the same behavior from other monospaced fonts ...I assume this is a bug of some kind ... The font I use: