-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Suggestion: Further Default Normalization Styles #161
Comments
Nope, the folder is there. Are you really sure that you're not getting it? This is the output in my console: $ npm i --no-save simple-icons-font
$ tree node_modules/simple-icons-font
node_modules/simple-icons-font
├── DISCLAIMER.md
├── font
│ ├── simple-icons.css
│ ├── SimpleIcons.eot
│ ├── simple-icons.min.css
│ ├── SimpleIcons.otf
│ ├── SimpleIcons.ttf
│ ├── SimpleIcons.woff
│ └── SimpleIcons.woff2
├── LICENSE.md
├── package.json
└── README.md
1 directory, 11 files |
Oh, I see. The fonts are generated dynamically through installation, for obvious practical reasons? They're not just sitting in a folder plainly, within the repo. I'm setting them up manually and just needed to straight download them, so that's why I was a bit confused. |
Could you explain why we must add the following CSS properties? font-style: normal;
line-height: normal;
vertical-align: middle; |
I threw together a quick demonstration: |
Yes, they're needed. This is just a vanilla test, so doesn't take into account some common variables that might take place out in the wild.
I even ran into an issue where I needed to use For what it's worth, I actually came up with my own hybrid solution where I combined the font method with actual svgs so that I could benefit from a lighter front-end load (the font method adds over 1mb to page load, and my method brings that down to under 100kb) and the responsiveness of svgs. Anyway, that's a discussion for another day, if anyone's interested. |
Thank you for the report, but I think that:
For the problem of high load added by fonts, that's true. It would be great to expose the build process to create a customized build, filtering by icons slugs. I've opened #163 to track it. So I'm fine with adding |
Just a quick reminder that I'm not suggesting the addition of https://github.com/simple-icons/simple-icons-font/blob/develop/scripts/templates/base.css The logic (I would assume) would be that while it's technically a font, that that's only a formality as a trick/method for delivering icons that shouldn't otherwise be treated like text. The same logic applies to Anyway, that's all I have to offer on the subject; I'll let you take it from here. Thanks |
PS: Unless I'm just being a complete dumb-dumb, the actual
/font/
folder appears to be missing from the GitHub repo? I had to go to unpkg.com to find the font files and download them.The text was updated successfully, but these errors were encountered: