If you simply reference custom system fonts, then the licensing requirement is on the user.
If you provide a font, then you (or your client) will need to license the font — even if it is a free font, there will probably be some form of license.
@ font-face uses two forms of links: LOCAL , which refers to the font of the user system and URL , which effectively uses a copy of the font that you provide, and it makes little sense to use the @fontface rule, if you are not going to provide the font, then it is almost sure that you will need to actively get a license.
eg:
@font-face { font-family: myHelveticaLight; src: local("Helvetica Neue Light"), local("HelveticaNeue-Light"); }
Here you refer only to a custom system font and, therefore, are not responsible for obtaining a license.
In the following example, you also provide a backup copy of the font, so you should actively obtain a web license for this font (more precisely, your client or website owner)
@font-face { font-family: myHelveticaLight; src: local("Helvetica Neue Light"), local("HelveticaNeue-Light"), url(HelveticaNeueLight.ttf); }
Chris Bentley Mar 30 '11 at 1:16 2011-03-30 01:16
source share