Kitty terminal emulator support

[fluix-dev]

I'm not sure if this font is considered monospace*, but if it is, then it doesn't get recognized by kitty. The kitty terminal emulator is quite picky about what it takes as a monospaced font and it doesn't detect Cozette. A list of fonts that it deems acceptable can be listed with kitty list-fonts.

Here's three issues for reference and possible solutions (it seems a common one is the font's Spacing parameter): kovidgoyal/kitty#827, kovidgoyal/kitty#557, and ryanoasis/nerd-fonts#268

Regardless of the resolution, thanks for the beautiful font!

*If this font isn't meant to be monospaced, feel free to close this issue.

[the-moonwitch]

If this font isn't meant to be monospaced, feel free to close this issue.

There... isn't really a useful definition of "monospaced" for people to agree on. The BDF font is specified as monospaced with the XLFD spacing property, but Kitty doesn't accept it because it wants a font considered "scalable" by fontconfig. The other fonts don't really have a way, afaict, of specifying they're monospace - it's generally based on whether the characters in the font are all the same width (and in Cozette, they explicitly aren't, because of eg. double-wide emoji), and some more black magic behind the scenes.

I've found microsoft/cascadia-code#118 (comment), which might be relevant. They seem to have solved the problem of a font with mixed-width glyphs not being recognized as monospace, I'll have to try and figure out how.

[fluix-dev]

Ah, alright, I've never delved into fonts or font making so I didn't know about all the fine details. Thanks for trying though, I'm happy to test anything!

[the-moonwitch]

I just realized Kitty doesn't support bitmap fonts, so this is a CozetteVector issue, which makes it much easier to fix. I suspect this might've gotten fixed in #14 and could work as of release 1.8.1. Could you try it out and let me know if it works now?

[fluix-dev]

Oh, I didn't know Kitty doesn't support bitmap fonts, but I've just tried CozetteVector and kitty still doesn't detect it. With this new info (about no bitmap support), I don't personally have a need for kitty terminal support but I'm happy to test out any future releases / fixes :)

[colingabr]

Here's a related issue I opened yesterday without seeing this one kovidgoyal/kitty#2739

Without the patch, I am able to get kitty to render CozetteVector via the below configuration options

However, as you can see the font is too small for my DPI. @slavfox I'm curious about what your DPI is? I'd really like to use Cozette but might go blind in the process :)

[the-moonwitch]

@novcn the font in your screenshot is not Cozette, as can be seen by eg. the a glyph and its derivatives. Cozette:

I'm on a HP Omen X35, 3440x1440 over 35", which comes down to 106.55 PPI. My laptop is 15" 1080p, for 146.86 PPI. I like small fonts :D

If you're looking for a larger bitmap font that still has solid powerline support, I can't recommend Tamzen enough. It's too big for my taste, but might be perfect for you.

I'll add a note with some larger bitmap fonts to the README, since this seems to be a common question. Making a bitmap font with this many glyphs is a lot of work - unlike vector fonts, which can be auto-patched for Nerd Fonts support, I draw each character by hand. I doubt I'm ever going to make larger variants of Cozette for that reason, so the least I can do is refer to some excellent larger bitmap fonts :)

[fluix-dev]

@novcn the font in your screenshot is not Cozette, as can be seen by eg. the a glyph and its derivatives.

I think this has to do with your command line. You should probably specify CozetteVector not Cozette (because Kitty doesn't have bitmap support), although I haven't had success with either, hence this issue.

[colingabr]

@slavfox thanks for the info! I'll give Tamzen a shot sometime.

Kitty was indeed falling back to Nimbus Mono

I was able to get kitty to load Cozette-otb using the patched branch mentioned in the kitty issue I linked.

CozetteVector is working for me as well! (Without patched kitty) and the size is perfect and scalable.

[fluix-dev]

I was able to get kitty to load Cozette-otb using the patched branch mentioned in the kitty issue I linked.

Damn, I really wanted this to work, but I tried it as well and it just... doesn't 😞

Not really sure why, I built both cozette-otb and kitty from source. I guess this should probably be closed though, since it seems to work for you and others in the kitty thread you linked.

[the-moonwitch]

I'd like to leave this open until (if) bitmap font support gets merged into kitty master. Cozette bitmap should work correctly on the new branch, Cozette Vector still doesn't look right in @novcn's screenshot - the bottoms of the glyphs are cut off, although I suspect that's just a Kitty configuration issue, I'd try playing with adjust_line_height.

Compare eg. g, p, and q in @novcn's second screencap:

To the bitmap version, which renders correctly:

As far as I can tell, bitmap Cozette gets correctly detected as monospace because the bitmap font formats allow me to explicitly define the spacing as monospace, but CozetteVector... doesn't, despite having the panose tables set. I think fontconfig might be basing that on individual glyph widths.

@TheAvidDev I didn't realize I never asked for this - are you on Linux or MacOS? novcn is on Mac, so this might be a system-specific problem (kitty uses coretext rather than fontconfig on Mac).

[colingabr]

I'm actually on Linux @slavfox

[fluix-dev]

I'm on Arch Linux x86_64 - 5.6.15-arch1-1. I also have a quick question:

new branch

Do you mean the kitty fork?