-
Notifications
You must be signed in to change notification settings - Fork 51
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
The font doesn't show up in Konsole font selection dialog #1
Comments
I think it's because it doesn't tell the system that it's a monospace font, the original font also had this issue: |
The good news is that the link above also has a solution :) |
Good stuff, thanks for the link. I'll look if I can make the corresponding change in my sources so it compiles right from the beginning in the proper form. I'm on the Mac and I tried to work with this font with FontForge with very poor results. |
Glad I could help a bit, looking forward to the next versions! |
BTW:
The position of the zero in your version is also still one pixel off |
Try Glyphs, it works great with bitmap fonts. |
I think this same issue may be the reason Windows Console (Command Prompt/Powershell) can't use this font. Any chance of a fix? |
The chance of the fix is seriously impaired by me not having neither Konsole nor Windows :-) I'd like to note that this font LOOKS bitmap, but it's not. See the readme, it consists of "pixels" drawn with vector lines. That's why it only works in one size, when these lines encompass real pixels and with antialiasing disabled. |
The solution at the link @JobLeonard provided essentially removes all glyphs that are not 80 wide. (Since we use 10x10 square for a "pixel" it means exactly 8 "pixels"). If this solution works for you you are in the wrong place: this solution removes all ligatures that I spent so much time adding :-) Zero offset was fixed a while ago. |
Probably some metadata is missing.
konsole --version gives Qt: 5.6.0, KDE Frameworks: 5.22.0, Konsole: 16.04.1
Arch Linux
reported by @Thimoteus
The text was updated successfully, but these errors were encountered: