[OpenFontLibrary] [Blueprint font-face-generator] The library must automatically generate @font-face files for uploaded fonts

Schrijver eric at authoritism.net
Mon Mar 21 07:02:39 PDT 2011

Op 21 mrt 2011, om 14:49 heeft Christopher Adams het volgende geschreven:

> What about providing all possible formats and letting the browser decide?
> Cf. The New Bulletproof @Font-Face Syntax
> http://www.fontspring.com/blog/the-new-bulletproof-font-face-syntax
> @font-face {
> 	font-family: 'MyFontFamily';
> 	src: url('myfont-webfont.eot?') format('eot'),
> 	     url('myfont-webfont.woff') format('woff'),
> 	     url('myfont-webfont.ttf')  format('truetype'),
> 	     url('myfont-webfont.svg#svgFontName') format('svg');
> }
> In any case if we can generate these files, then we can make them
> available as individual downloads on the font profile page.

Let’s say we want to offer all these formats,
Why would you want the individual downloads?

I would only offer people one download option: the font package as a zip.
It’s more easy, and also more correct since the package is going to include licenses and readme’s and FONTLOG’s etcetera.

This should include a subfolder webfonts/ which includes all these fonts with a css snippet and html example?

It’s bound to confuse people otherwise, if they can choose to download 5 versions of a font.

Providing all these formats is not so hard, like I said, with a simple python script that links to fontforge and calls ttf2eot.

the script I posted earlier can be called as a system command via php: 'python webfonts.py foo-font.[otf|ttf|ufo|etc]' and it will generate all these formats.



More information about the OpenFontLibrary mailing list