search

majodev / google-webfonts-helper

A Hassle-Free Way to Self-Host Google Fonts. Get eot, ttf, svg, woff and woff2 files + CSS snippets
https://gwfh.mranftl.com
MIT License
12.02k stars 420 forks source link

ttf in Legacy, but no woff #182

Open Vallek opened 7 months ago

Vallek commented 7 months ago

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?

majodev commented 7 months ago

For background see https://github.com/majodev/google-webfonts-helper/issues/162#issuecomment-1547693525

Vallek commented 7 months ago

That's a strange reasoning imo)

  1. Yes ttf has more support percentage obviously cause it's older) That's a reason to put in in Historic not Legacy
  2. Not sure I understand compression argument as woff also uses the same source structure. woff2 just has different and better compression.
  3. Also as far as I know up until recently the standard legacy option was woff+woff2 and before that all three. I never saw anyone uses woff2+ttf without woff.

Anyway thanks for this tool!

xpe commented 1 month ago

@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.)

Vallek commented 1 month ago

@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)