-
-
Notifications
You must be signed in to change notification settings - Fork 435
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
ttf in Legacy, but no woff #182
Comments
For background see #162 (comment) |
That's a strange reasoning imo)
Anyway thanks for this tool! |
@Vallek Roughly six months later, has anything changed with your rationale above? (I'm just a person on the internet trying to help out this project; I don't have any particular experience with font formats.) |
@xpe Hi! Nothing changed as far as I know. But I guess the difference between woff and ttf is not that important. The support is pretty similar. woff2+ttf seems wider so i guess it makes sense. It just looked weird to me cause woff2+woff seems more standard. In the end of the day everyone can manually choose what they want) Also I'm not font expert either and absolutely could be unaware of something else) |
Hi! I noticed that there is ttf fonts in Legacy Support but no woff. And woff is present in Historic Support. Shouldn't it be the other way around? Since ttf is older then woff?
The text was updated successfully, but these errors were encountered: