[OpenFontLibrary] Server Side SVG
So, what was the name of that server side svg renderer written in C which you were mentioning today? C and C++ are my favorite tools to develop websites with, btw... PHP certainly has it's place, but apparently mere mortals are able to code in PHP as well. --Eric Way
Re: [OpenFontLibrary] Server Side SVG
rsvg On Wed, Apr 21, 2010 at 11:37 PM, fontfree...@aol.com wrote: So, what was the name of that server side svg renderer written in C which you were mentioning today? C and C++ are my favorite tools to develop websites with, btw... PHP certainly has it's place, but apparently mere mortals are able to code in PHP as well. --Eric Way -- Jon Phillips http://rejon.org/ http://fabricatorz.com/ http://status.net/ http://rejon.status.net + skype: kidproto +1.415.830.3884 (sf/global) +86.134.3957.2035 (china)
Re: [OpenFontLibrary] Kernest’s Web Font Serving E ngine – Fontue – Now Open Source
On 04/22/2010 02:15 AM, Barry Schwartz 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.) Ha ha ha :-D I thought that the Alpha Centaurans would be using a more complicated writing system... but they just go for CAPITAL LETTERS then? Hey, that would explain the high quality of OpenBSD ;-D Seriously, the general mistake is mislabeling and miscategorizing creations that upstream authors have released under their chosen licenses (whatever it may be) and sweeping that under a superset EULA. All I'm saying is that these brokers shouldn't deliberately hide what authors have chosen to do with their creation as they distribute or provide subscriptions. It's rather disingenuous otherwise. 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. IMHO it's great that typekit provides a service to others allowing them easier access to your work. (BTW the link to your personal website and other creations you have published is 404 on your typekit profile). But people going through catalogs of such brokers will want to know the details of what they are allowed to do before using/subscribing to the given 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. Requiring (or not) attribution in the resulting artwork or document (such as in a small colophon) is orthogonal to requiring the copyright and licensing notice not be hidden, removed and overriden by a global license... In many licenses the former is optional (usually appreciated) but the latter is mandatory. My feeling is that in the knowledge society/economy you could argue that hiding or stripping away authorship information is one of the worst crimes whereas a mention in a colophon somewhere (or more generally some kind of linkback) is appreciated by most authors. Cheers, -- Nicolas Spalinger, NRSI volunteer Debian/Ubuntu font teams / OpenFontLibrary http://planet.open-fonts.org
Re: [OpenFontLibrary] Kernest’s Web Font Serving E ngine – Fontue – Now Open Source
On 04/22/2010 02:19 AM, Barry Schwartz wrote: 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 there's also Firefontfamily https://addons.mozilla.org/en-US/firefox/addon/111672 and TypeGauge: https://addons.mozilla.org/en-US/firefox/addon/9972 Very handy when designing or to learn more about a particular font but but at this stage they don't show origin and authorship metadata. Cheers, -- Nicolas Spalinger, NRSI volunteer Debian/Ubuntu font teams / OpenFontLibrary http://planet.open-fonts.org
[OpenFontLibrary] Meeting with Jon Phillips
I wanted the group to know that I had a very positive meeting with Meeting with Jon Phillips yesterday in San Francisco. We discussed openfontlibrary, my new open font website in development, and numerous websites Jon and I are working on which have nothing to do with fonts. (web based vector design software, social networking, tech law, and more) In person, Jon is MUCH more down to earth than I had expected. We dined on canned peaches and a Charlston Chew. Eric Way (FontFreedom)
Re: [OpenFontLibrary] Kernest’s Web Font Serving En gine – Fontue – Now Open Source
Nicolas Spalinger nicolas_spalin...@sil.org writes: 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. Many people outside the open-source community don't know those words. For discussions on a mailing list they're fine, but they don't really communicate well when your audience is the general public. Instead of Gratis I would suggest the phrase free of charge, which I believe nearly everyone in the English-speaking world understands. As for libre, it's better to name a specific license, or at least the general category (permissive versus share-alike). Not everyone will understand, but people who *care* about the license will, so. -- v4sw5Phw5ln5pr5FPO/ck2ma9u7FLw2/5l6/7i6e6t2b7/en4a3Xr5g5T http://hackerkey.com/decrypt.php?hackerkey=v4sw5PprFPOck2ma9uFw2l6i6e6t2b7en4g5T
