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

Font variants for different purposes #994

Closed
ghost opened this issue Apr 9, 2020 · 3 comments
Closed

Font variants for different purposes #994

ghost opened this issue Apr 9, 2020 · 3 comments

Comments

@ghost
Copy link

ghost commented Apr 9, 2020

Some ligatures are good for one language/use-case but are not wanted in another.
At the moment, those ligatures get remove to not annoy anyone.

Maybe it would be a good idea to make 2 or 3 variants of FiraCode where each contains some of the conflicting ligatures split to some use-cases/languages.
Maybe a base variant with less ligatures, and some variants which contains the conflicting ones?

Otherwise, maybe more stylistic sets would be great

(Also fine to leave it as it is - I am not missing something particular :)

@tonsky
Copy link
Owner

tonsky commented Apr 10, 2020

I’m taking stylistic sets approach for now. Maintaining multiple version would be too cumbersome. Eventually we might end up using locl and language tags but apply them to programming languages. I think some fonts are already doing it, don’t remember who. Also editor support is probably lacking #76

@adah1972
Copy link

I see that releasing multiple versions can be very cumbersome for you. Are there any tools that can help in this? Maybe switching on different style sets by default?

With more and more ligatures coming into this font, conflicts are more and more likely. Unwanted ligatures are annoying. Regretfully, program editors are not typesetting programs, and they are often lacking in supporting advanced features like style sets. It seems Vim does not support it so far.

@tonsky
Copy link
Owner

tonsky commented Mar 15, 2022

Resolved via #1387

@tonsky tonsky closed this as completed Mar 15, 2022
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