-
-
Notifications
You must be signed in to change notification settings - Fork 725
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
Do we support ligatures? #3312
Comments
Duplicate of #1013. |
Even with ligatures we'd need to maintain the CSS files who those who wouldn't want to use ligataures. And the ligatures would only increase the size of the font files too. If the physical size of the files is a concern for you then you should look into using SVG instead of the webfont, which is something we're actively encouraging everyone to do. |
UPDATE: To just answer my own question: https://css-tricks.com/icon-fonts-vs-svg/ Thank you. I was just looking into this option after my failed attempt to see if 'liga' was going to work . Could you please help me understand why SVG is encouraged instead of webfonts here? |
@blendsdk Every month and a half we add roughly 100+ icons. The font will never be an ideal way to use the icons as we reach over 3k icons. We'll be adding TypeScript and a ES6 module shortly for more 3rd party integrations. TBH, we're never going to add ligature support, it's just not a priority unfortunately. |
@Templarian thank you. It is clear now. |
Hi,
The icon font files originally provided by Google supported a pretty nice feature called "ligatures"
Do we support this?
At the moment the CSS file is very large and will get larger as new icons are added. With ligatures we won't be needing a separate css selector for each icon.
Any thoughts?
The text was updated successfully, but these errors were encountered: