-
Notifications
You must be signed in to change notification settings - Fork 1
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
ligatures in vscode #3
Comments
Can you please be more specific? Which ligatures are you missing? Or can't you get the font to work? Also if you realy are missing ligatures I would suggest opening a ticket at https://github.com/cormullion/juliamono, I'm just the guy adding the Nerd part ;) |
Any feedback @tobsn? |
sorry, busy week - I meant double/triple equals for example. They seem to not work with the latin version at least (which, why does this look so much better? :)) |
Sorry I still don't get what you mean, could you give me the Unicode code point, e.g. U+2261 and perhaps post a screenshot of the working ligature in another font vs. the non working in julia? |
I build with the |
I build the font without the font.zip includes:
Could you test if this fixes the issue? If so I'll update the release and from now on build with and without Ok the Arrows work, but not the equal signs. That's confusing... Edit: But the behaviour is the same for the unpatched font |
Ok as far as my understanding goes that is not a part that the NerdFontPatcher adds, the ligatures must be defined in the font itself. @tobsn and @cormullion please correct me if I'm wrong, otherwise I'll close this Issue. Nevertheless it is always interesting to learn how unicode works 😉 I also will add the non |
Ok I also found this repo: https://github.com/ToxicFrog/Ligaturizer I'll try it later |
Don't use the "-Latin" fonts - they're stripped down "Latin-only" versions designed for quick loading.
|
I was able to build a font with working ligatures for the equal signs, but it's a pain in the ***. The Ligaturizer scripts is buggy and only works with:
all other files look like this:
There is a Issue in the repo, but without a fix: ToxicFrog/Ligaturizer#53 Also the script uses a old version (3.1) of fira code, updating to a newer version is not possible because fira code switched to I will not integrate this into the workflows. But if you want to reproduce it, this is the script I used:
From my point of view there
Edit: Missed @cormullion reply... down to one solution |
Forgot to upload the But if you need updates or more / newer ligatures of fira you have to build them yourself or use |
Thanks for all your hard work @mietzen! I follow the issues on Fira Code' github repo. Ligatures are a continuing source of issues, problems, and additional work, and I don't regret my decision to not start down that path (even if I was funded 🤣). |
@mietzen that works great yes! You think you could rerun it again with Latin? If not that's okay :) |
@tobsn I already delete the files sorry, also I think the Ligaturizer script had some troubles with the latin font as well |
Out of interest, why do you want the Latin? You could always remove unwanted features with https://mutsuntsai.github.io/fontfreeze/ ... |
can't get them to work... any idea?
The text was updated successfully, but these errors were encountered: