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

Support for TrueType collections? #577

Closed
imyxh opened this issue May 26, 2018 · 4 comments
Closed

Support for TrueType collections? #577

imyxh opened this issue May 26, 2018 · 4 comments

Comments

@imyxh
Copy link

imyxh commented May 26, 2018

I hate to bother you with another issue mentioning Iosevka, but this looks distinct from the previous issues filed because I actually can't get kitty to use the Iosevka Term as the font at all, which hasn't been mentioned yet as far as I've checked. Iosevka Term has no ligatures or anything else that I know would break kitty; kitty just refuses to display it.
Here's a screenshot that should explain:
image
The lower part with QTerminal is the expected result, of course. Fully monospaced with no ligatures.

It's probably worth noting that when I set the font as "monospace" or just comment out the line, kitty will use some other weird font even if I have "Iosevka Term Regular" specified as my monospace font in GNOME tweaks.
All other applications handle this fine, so I suspect that something's up with fontconfig.find_best_match in the source code. Or perhaps there's just another incompatibility with the way Iosevka is made.

Thanks!

@kovidgoyal
Copy link
Owner

I cannot replicate this. Installing both Iosevka and Iosevka Term (I installed the ttf files and ran fc-cache) and using

kitty -c NONE -o 'font_family=Iosevka Term' -o font_size=15

screenshot_20180527_081234

You can debug fontconfig matching in fontconfig.c in fc_match() print out what parameters are being passed to fontconfig to chekc they are as expected. If they are then the issue is whitht he fontconfig configuration on your syste,. Look for fontconfig .conf files either in /etc or the user fontconfig directory.

@imyxh
Copy link
Author

imyxh commented May 27, 2018

(I installed the ttf files and ran fc-cache)

Actually, I installed Iosevka via .ttc. Which means that my configuration looks like this:

$ ls /usr/share/fonts/TTF/ | grep iosevka
iosevka-bold.ttc
iosevka-extralight.ttc
iosevka-heavy.ttc
iosevka-light.ttc
iosevka-medium.ttc
iosevka-regular.ttc
iosevka-slab-bold.ttc
iosevka-slab-extralight.ttc
iosevka-slab-heavy.ttc
iosevka-slab-light.ttc
iosevka-slab-medium.ttc
iosevka-slab-regular.ttc
iosevka-slab-thin.ttc
iosevka-thin.ttc

Does kitty not work with TrueType collections?

@kovidgoyal
Copy link
Owner

I've never actually tested it with ttc as they are pretty rare. If you zip them up and attach the file, I'll take a look. Or just remove them and install the ttf files. As far as I know upstream does not release ttc, so where are you getting them from? https://github.com/be5invis/Iosevka/releases/tag/v1.13.3

@kovidgoyal kovidgoyal reopened this May 27, 2018
@imyxh
Copy link
Author

imyxh commented May 27, 2018

Alright, I just replaced them with .ttf files and it works fine now.
The Iosevka pack is a collection of .ttc files.
I think I'll rename this bug to be a feature request for TrueType collections, then.

@imyxh imyxh changed the title Kitty displays Iosevka instead of Iosevka Term Support for TrueType collections? May 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants