Closed Akselmo closed 11 months ago
Interesting. I have an idea to why it is looking weird - I will try to fix.
Hi, any updates on this? :)
Will work on it, when I have time.
@Akselmo will you check if this is fixed with the latest version, that I just shipped?
Yeah, looks better now, it's not underlining the bottom dot in the :
like previously.
Just another datapoint, here is underline in macOS Terminal. Looks fine.
Seems font size affects a bit to the underline position. On font size 11 it looks fine, but on 10 it still gets a bit too close to the bottom dot in Er, nevermind.:
.
10px
12px
16px
Also something interesting I found.. In libreoffice if I tried to underline the font, it did not show up at all
Attached the odt file just if you want to give it a try as well commitmonotest.odt
I don't know where to go with this issue, can I close it?
I don't know where to go with this issue, can I close it?
Fine by me!
Hey, I don't know if this is a font thing or app thing, but felt like asking..
I like using this font everywhere, basically. It's great, helps me read things.
However, seems in non-monospace fields, the underlining behaves a bit oddly. Like it's a bit squashed on top of the text?
In the screenshot, above text is in Konsole, KDE terminal app. The text below is in Nheko, a Qt chat application for Matrix.
Seems the bug is also apparent in Kate, KDE code editor:
It seems the gap between underline and the text is gone in some applications.
I am using the otf fonts from the dev packages, only things I've customized are
alt-g
andsquare-dots
.I don't know if this is a font thing or linux thing or Qt thing... But all apps I screenshotted use Qt, so I am not sure.
My system info:
Is there anything I could help to do to track this down? Again, I really love this font, it made my reading experience much easier everywhere, and having the ability to use single-storey-g is great.
Alternatively, non-monospace version of this font for use in system wide applications that do not expect to use monospace fonts would be great! I think that may fix the issue, but not sure.