Closed Grawl closed 10 years ago
I agree that custom webfonts are used on many projects, but it seems that font generation might be a bit more unique. I think it's awesome that all the other needed web font formats can be generated from a .ttf
file, but I think this use case is very specific for certain projects.
That being the case, I don't think it makes sense to add something like this to yeogurt at this time.
I will keep this issue open for a bit in order for discussion.
Okay I will create yeogurt
fork with fonts, JSON for Jade and for Ruby Sass and other improvements when you will release 0.10
if you won't add them to your scaffold.
Okay.
So you want me to add all my additions to #43?
Let's keep #43 limited to only the local JSON file changes and have new PR for every other feature (Like Ruby Sass)
I think so. Let this webfont issue be opened before someone will create a PR.
Many projects need to use custom web fonts and static site generator needs to support this feature.
Now I use
webfonts
to generate them (and just copy to/fonts
) and think that we can usegrunt-shell
to embed it into Grunt andgrunt-fontface
to generate stylesheets.Why
webfonts
and notgrunt-fontgen
? Becausegrunt-fontgen
requires installation ofhomebrew
modules that maybe hard to novices and windows users.webfonts
uses compiled binaries to generate fonts. I have not tested it in windows but think that it would work.We need these formats:
eot
for IEwoff
for WebKitttf
as a standardsvg
for some old browsers such as old MobileSafariThere is also few generators per format as Grunt tasks:
grunt-ttf2woff
grunt-ttf2eot
ttf2svg
. newermind, we do not need them I think