Re: [OpenFontLibrary] Kernest’s Web Font Serving En gine – Fontue – Now Open Source
Garrick Van Buren wrote: I've open-sourced Kernest's underlying font serving engine. Info here: http://blog.kernest.com/archive/kernests-web-font-serving-engine-fontue-now-open-source Hi Garrick, Quick note to say thanks a lot for all your efforts in this area and releasing your font serving component under MIT/X11 (and with some documentation too). Interesting approach ! Do you have any stats on the preferred formats you currently support? I like the way you're not hiding the origin, license and other metadata of the libre/open fonts you include in your catalog (Ahem unlike others apparently: http://readableweb.com/typekit-and-copyright-fraud/ but they promised they will work on clarifying it..) but I really recommend you move away from the confusing free description: please consider saying Gratis when you don't make your subscribers directly pay for the given font and libre/open when you describe fonts released under community-approved licenses allowing distribution / modification / study / redistribution. This clarification will benefit everyone. Please do it. You're benefiting (and rightly so, it's great!) from the work of font designers who have released their creation under a community-recognized license so please don't misrepresent their work by wrapping it under confusing blanket terms... You could also consider some more linkbacks to the open font community websites or even some small amount of support/sponsoring of community efforts around collaborative font design (a tiny percentage of profit on libre/open fonts given back to encourage community efforts which will then benefit you?)... (A very minor thing: s/browswer/browser/g) Thanks again! -- Nicolas Spalinger, NRSI volunteer Debian/Ubuntu font teams / OpenFontLibrary http://planet.open-fonts.org signature.asc Description: OpenPGP digital signature
Re: [OpenFontLibrary] Kernest’s Web Font Serving En gine – Fontue – Now Open Source
Oh, I forgot to say: An easy way to see what fonts are used at a site is the Font Finder extension for Firefox: https://addons.mozilla.org/en-US/firefox/addon/4415
Re: [OpenFontLibrary] Kernest’s Web Font Serving En gine – Fontue – Now Open Source
Nicolas Spalinger nicolas_spalin...@sil.org skribis: I like the way you're not hiding the origin, license and other metadata of the libre/open fonts you include in your catalog (Ahem unlike others apparently: http://readableweb.com/typekit-and-copyright-fraud/ but they promised they will work on clarifying it..) More like blog fraud, if you ask me. :) But TypeKit did make the mistake of writing language that sounds legal, rather than English. (The ISC license is the only I can think of that is written in English, and for that you have to disregard the disclaimer, which is written in Alpha Centauran.) TypeKit embeds my fonts, as a service to others; they should embed the copyright string with the font, but it doesn't really matter, because I do not require attribution when someone embeds my fonts. Some _do_ require attribution for embedding (Jos Buivenga, for one), but I'm not sure it's TypeKit who needs to do the attributing; rather the website using the font. Personally, I think requiring attribution for the use of a text font is somewhat like requiring a painter to follow the signature with a note about what brand of paint, brushes, palettes, and easles were used.
Re: [OpenFontLibrary] Kernest’s Web Font Serving En gine – Fontue – Now Open Source
On Wed, Apr 21, 2010 at 8:15 PM, Barry Schwartz chemoelect...@chemoelectric.org wrote: Nicolas Spalinger nicolas_spalin...@sil.org skribis: I like the way you're not hiding the origin, license and other metadata of the libre/open fonts you include in your catalog (Ahem unlike others apparently: http://readableweb.com/typekit-and-copyright-fraud/ but they promised they will work on clarifying it..) More like blog fraud, if you ask me. :) But TypeKit did make the mistake of writing language that sounds legal, rather than English. (The ISC license is the only I can think of that is written in English, and for that you have to disregard the disclaimer, which is written in Alpha Centauran.) TypeKit embeds my fonts, as a service to others; they should embed the copyright string with the font, but it doesn't really matter, because I do not require attribution when someone embeds my fonts. Some _do_ require attribution for embedding (Jos Buivenga, for one), but I'm not sure it's TypeKit who needs to do the attributing; rather the website using the font. Personally, I think requiring attribution for the use of a text font is somewhat like requiring a painter to follow the signature with a note about what brand of paint, brushes, palettes, and easles were used. People who are really interested in fonts often will know already who the font author is, and will make the effort to find out if they like the font. Other people don't care as much and so will most likely not pay much attention to the attribution even if it is present. So in the end analysis, it may not make that much difference whether attribution is given or not ...
