I’m not sure Quinn is after what you think he is :) Quinn… do you mean you want to serve fonts like the example i am serving from http://newtypography.net/testing/ ?
A.k.a you want your fonts to be served to remote web pages by simply adding a 'link href’ line to the head of the source html document and then using the ‘font-family’ to set text ? You (or anyone else using your webfont) would not have to write those lines and lines of @font-face rules in css documents? A.k.a users can’t simply browse the css source and see that ‘myfont.ttf’ is residing at ‘http://myweb.com/fonts/myfont.ttf' Of course, even if you use a ‘server’, people can still download the fonts, e.g. by using Chrome's ‘Developer Tools -> Elements’ and grabbing the woff files of any fonts embedded in the page. -v On 29 Oct 2013, at 10:39, Dave Crossland <d...@lab6.com> wrote: > On 29 October 2013 13:05, Quinn Keaveney <qke...@gmail.com> wrote: >> By saying I don't want to use @ff I just mean that I want to use an @ff that >> obfuscates the link/src file so you can not just click and download the >> woff. > > This is impossible.
