search

kika / fixedsys

Fixedsys Excelsior font with programming ligatures
982 stars 50 forks source link

The font doesn't show up in Konsole font selection dialog #1

Open kika opened 8 years ago

kika commented 8 years ago

Probably some metadata is missing. b8p54on

konsole --version gives Qt: 5.6.0, KDE Frameworks: 5.22.0, Konsole: 16.04.1 Arch Linux reported by @thimoteus

JobLeonard commented 7 years ago

I think it's because it doesn't tell the system that it's a monospace font, the original font also had this issue:

http://askubuntu.com/questions/210283/how-to-use-fixedsys-in-the-gnome-terminal-or-wherever-monospaced-fonts-are-requ

JobLeonard commented 7 years ago

The good news is that the link above also has a solution :)

kika commented 7 years ago

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.

JobLeonard commented 7 years ago

Glad I could help a bit, looking forward to the next versions!

JobLeonard commented 7 years ago

BTW:

If you want, you can tweak one or more questionable features of Fixedsys. E.g., the zero character is shifted one pixel to the right. To shift it back to center, double click on it, then click Metrics → Set LBearing..., set the LBearing to 10 and click OK. You can also change the shape of characters, but always keep control points at multiples of 10, and the width at 80.

The position of the zero in your version is also still one pixel off

iiiGerardoiii commented 7 years ago

I tried to work with this font with FontForge with very poor results.

Try Glyphs, it works great with bitmap fonts.

orffen commented 5 years ago

I think this same issue may be the reason Windows Console (Command Prompt/Powershell) can't use this font. Any chance of a fix?

kika commented 5 years ago

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. I personally tried FontForge and Glyphs with abysmal results. The only tool that worked was TTX and text editor. It's actually not that bad. The decompiled font (see the source in this repo) has a lot of some flags and values and whatnot, and I'm sure some of it affects the problem in this issue. I don't know enough about font technology to figure out what. I just like 8x16 fonts :-)

kika commented 5 years ago

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.