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
Poppins truetype font file can't work with font-feature-settings #771
Comments
We actually convert the Although if the |
Hey Ayu, thank you for your reply. I understand Google fonts CDN doesn't support truetype font files from their API for size optimizations, I am not sure if fontsource is considering the same in the future? |
This isn't in this project's scope since we only aim to replicate Google Fonts with optimised fonts for the web. It would be too labour-intensive for us to manually support fonts compared to simply mirroring Google Fonts. If you need explicit support for this, we can only recommend you download from the source itself. Thanks! |
After a little bit more thought on this, it might make sense to expand the scope of the project to include this. #39 would be the relevant issue to discuss this. |
Describe the bug
Fontsource poppins truetype font file can't work with font-feature-settings as Google font.
Steps to Reproduce
poppins-latin-400-normal.ttf
frompoppins/ttf
a
and use Poppins from locally-installed font.font-feature-settings: "ss02";
for Poppins font-weight 400.a
not being updated to double storey.Expected behavior
After enabling
(font-feature-settings: "ss02";)
for double-storey lower case a with manually installed Google Poppins truetype font file, lower casea
shows correctly.Version
No response
OS
No response
Browser
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: