Open stevenbriscoeca opened 7 years ago
AFAIK Font Awesome 4 only comes in a webfont format.
No but why use don't awesome and not a SVG solution is my question
Font awesome 5 now comes with svg support. How can I integrate it into semantic?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 30 days if no further activity occurs. Thank you for your contributions.
Don't close
This would lead to shipping with a lot of assets and I don't think that would be a good idea for most people.
I too would like to switch to using svg icons to get around a Windows 10+IE11 bug when the Group Policy "Block Untrusted Fonts" is set that causes no external fonts to be rendered in IE11.
If Semantic uses Font Awesome 5, how do I switch to svg icons?
I personally want to use SVG icons as other libraries that I may want to inject icons into (e.g. MaterialUI expect an SVG icon). It seems however that semantic-ui uses font awesome anyway now, so perhaps I can just use that library instead of semantic.
Given this though, I suppose it makes sense that semantic-ui would allow SVG icons as props in their components, as this is the way other libraries (such as material-ui) have done it
Hello,
I was wondering why use icon fonts instead of svg? I could not find any issue on this subject.
Thanks!