Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No bitmap font support since pango 1.44 #4390

Closed
dnkl opened this issue Jul 28, 2019 · 10 comments
Closed

No bitmap font support since pango 1.44 #4390

dnkl opened this issue Jul 28, 2019 · 10 comments

Comments

@dnkl
Copy link
Contributor

dnkl commented Jul 28, 2019

Since version 1.44, pango no longer supports bitmap fonts: https://blogs.gnome.org/mclasen/2019/05/25/pango-future-directions/

Since sway uses pango, this also means no more bitmap fonts in sway. I just wanted to a) make you aware of this, and b) ask what your thoughts on this are?

I for one cannot live without bitmap fonts. At least not on non-high-DPI monitors.

If sway wants to continue supporting bitmap fonts, what kind of solutions would you find acceptable? I'm asking since it would seem this requires either moving away from pango, or at least add support for more font rendering backends?

@emersion
Copy link
Member

I don't care a lot about these personally.

In case you missed it:

Note that Harfbuzz does support loading bitmap-only OpenType fonts.

@progandy
Copy link
Contributor

progandy commented Jul 28, 2019

Some useful links for font conversions. It should be possible to convert Type1 fonts to OTF (CFF) fonts and bitmap fonts to bitmap-only TTF/OTF fonts (optionally with a vectorized variant).

https://fontforge.github.io/scripting-tutorial.html
https://github.com/kreativekorp/bitsnpicas
https://github.com/koron/bdf2ttf
https://github.com/dse/bdf2ttf
https://github.com/Tblue/mkttf

@DmitryHetman
Copy link

Why use ttf fonts in console? Bitmaps looks much better.

@DmitryHetman
Copy link

you dont have to smooth them etc.

@Architector4
Copy link

Why use ttf fonts in console? Bitmaps looks much better.

Subjective, though. I, for one, don't like bitmap fonts, and prefer smooth monospace vector based fonts.

@hissssst
Copy link

hissssst commented Jul 30, 2019

Got my bitmap font fucked up broken today, any fix/branch ?

@emersion
Copy link
Member

Use OpenType bitmap fonts.

@dnkl
Copy link
Contributor Author

dnkl commented Jul 30, 2019

@hissssst: since re-packaging all my fonts in TTF/OTF isn't really something I wanted to do, I opted to: a) limit my usage of GTK/pango based programs as much as possible, b) use titlebar-less windows in Sway, and instead display the active window's title in the bar (not swaybar though, my own bar), and c) use qt or terminal based applications whenever possible.

Might write a dunst/mako-replacement just for fun as well...

Yeah, I'm not happy, but life goes on.

@parkerlreed
Copy link

RIP Terminus. Glad I'm still on KDE. Sad to bear.

@dnkl
Copy link
Contributor Author

dnkl commented Aug 7, 2019

@parkerlreed @hissssst @DmitryHetman
I've created a fork/PR-that-will-never-be-merged at https://gitlab.com/dnkl/sway. It replaces pango with fontconfig+cairo, which still support bitmap fonts. It's a huge hack, with lots of limitations. See README.md in the fontconfig branch for details and instructions.

I guess it's also a good idea to not comment here anymore - don't beat the dead horse.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

7 participants