Font parcher - fonts get blurred/grayed out

[im-n1]

Hi folks

I've spend many hours choosing my new font to substidue my bitmap current one (need scalability). The major thing bitmap fonts are so great (according to me) is they are sharp and thus well visible. I could achieve the same visibility and sharpness with AnonymousPro font. But if I try to use your patched font or i do patch it by myself with your font patcher I get blurry font and grayed out characters.

Before patching

After

The letter spacing is ok - i can adjust that in Xresources. But not the blurriness :(

[gim913]

There's actually same issue with Terminess TTF Nerd font

This is Terminus TTF font (click to zoom in):

This is Terminess TTF Nerd from patched-fonts dir:

[im-n1]

Offtopic: whats the crate you are working on?

[gim913]

Offtopic: whats the crate you are working on?

actually not my crate, clone of https://github.com/Peltoche/lsd
(apparently github needs some kind of chat/messaging ^^)

[im-n1]

Nice to see another Rust dev. Let's use irc. Serv: irc.mozilla.org, chann: rust

Back to topic:
The lsd is nice tool. Another usage for nerd fonts. I hope the font patcher will be fixed soon.

[Slabity]

Anything on this?

Bitmap fonts are still blurry when patched. What seems to be the issue?

[im-n1]

I just tried already patched font in term Alacritty and it's completely different font...

[hbjydev]

Can I get a bump on this?

[Slabity]

Bumping... Still broken...

[pinusc]

I believe there is a chance this is related to fontconfig issues. I have been playing with my configuration all day, and can not seem to achieve the same sharpness as when using .pcf or .otb fonts (testing on GohuFont)
I can achieve sharpness by disabling antialiasing, but then the font "breaks", I suspect as a result of hinting.

[topaxi]

This is not only happening with bitmap fonts but any font 😕

[Akselmo]

Ive seen this problem too. I really like the terminus font in its bitmap form

[gim913]

Ive seen this problem too. I really like the terminus font in its bitmap form

And so I've switched to Iosevka ¯_(ツ)_/¯
https://github.com/be5invis/Iosevka

[yamabiiko]

Is there any update on this? Terminess Nerd Font still looks blurry in my system

[Finii]

I looked a bit into this.

Terminus is a bitmap only font http://terminus-font.sourceforge.net/

Q. Scalable version?
A. Long story short, when the average display resolution becomes at least 150 DPI. Prefferably 200.

The bitmap fonts are bundled into a ttf then with https://github.com/Tblue/mkttf
to form the Terminus (TTF) we use as base.

(Well in fact in the middle this is also involved: https://github.com/drew-kun/terminus_powerline_font_osx, I guess. Or something alike there are multiple projects; but that has no influence on the technical aspect in this comment)

That mkttf takes all bitmap fonts, stuffs them into a ttf file and uses autotrace or potrace to create also a scalable font.
I see no special handling in the potrace call, and I also see no manual adjustments to the resultant glyphs we use (like Almost Vertical etc). So the results are ... sorry, I would call that mediocre.

If you use the 'original' TTF (calling it 'original' feels a bit strange) you in fact use the embedded bitmap fonts (I believe). Thus the result looks good. After Nerd Font patching the bitmaps are dropped (we do not patch bitmaps), and the (mediocre) outlines are used.

Making good outlines for Terminus would involve a lot of work, also manually. This is nothing I would conduct.

So sorry, I see no easy solution for this. But maybe I'm wrong. @ryanoasis might know more about Terminus.
More info maybe at Issue #23

[Finii]

Duplicate of #86

[DoctorKnowsBetter]

I fixed this crap :)
https://github.com/DoctorKnowsBetter/TerminessNerdFont-FixBlur

[Finii]

Closed via #939.

Many thanks to @DoctorKnowsBetter for finding a solution and help testing!

[github-actions]

This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. If you have found a problem that seems similar, please open a new issue, complete the issue template with all the details necessary to reproduce, and mention this issue as reference.