<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The Font-as-Service</title>
	<atom:link href="http://ilovetypography.com/2009/08/07/the-font-as-service/feed/" rel="self" type="application/rss+xml" />
	<link>http://ilovetypography.com/2009/08/07/the-font-as-service/</link>
	<description></description>
	<lastBuildDate>Wed, 08 Feb 2012 05:35:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Designers</title>
		<link>http://ilovetypography.com/2009/08/07/the-font-as-service/#comment-17070</link>
		<dc:creator>Designers</dc:creator>
		<pubDate>Fri, 04 Sep 2009 13:23:59 +0000</pubDate>
		<guid isPermaLink="false">http://ilovetypography.com/?p=5953#comment-17070</guid>
		<description>Pushing looks forward with DRM as the backend. People upload images to the web, and expect their designs not to be stolen, HTML/CSS/JS/images are all the same. Why is the solution something that should be obfusticated just for fonts? This isn&#039;t a solution, this is the hack. The solution exists and the way to use a font is through the proper CSS methods, and licensing fonts you don&#039;t have a license to. The same as it always has been for images.

I concur with the final synopsis, but I personally I can&#039;t wait to see the end to all of this SIFR/font replacement lark.</description>
		<content:encoded><![CDATA[<p>Pushing looks forward with DRM as the backend. People upload images to the web, and expect their designs not to be stolen, HTML/CSS/JS/images are all the same. Why is the solution something that should be obfusticated just for fonts? This isn&#8217;t a solution, this is the hack. The solution exists and the way to use a font is through the proper CSS methods, and licensing fonts you don&#8217;t have a license to. The same as it always has been for images.</p>
<p>I concur with the final synopsis, but I personally I can&#8217;t wait to see the end to all of this SIFR/font replacement lark.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse</title>
		<link>http://ilovetypography.com/2009/08/07/the-font-as-service/#comment-16967</link>
		<dc:creator>Jesse</dc:creator>
		<pubDate>Fri, 28 Aug 2009 15:32:41 +0000</pubDate>
		<guid isPermaLink="false">http://ilovetypography.com/?p=5953#comment-16967</guid>
		<description>Wow! Great post. I wasn&#039;t aware of any of these solutions. It is a great day for the web now that this is getting the attention it deserves. For too long we&#039;ve remained stagnant with the same typical font stacks while javascript and CSS improvements and adoption push us forward.</description>
		<content:encoded><![CDATA[<p>Wow! Great post. I wasn&#8217;t aware of any of these solutions. It is a great day for the web now that this is getting the attention it deserves. For too long we&#8217;ve remained stagnant with the same typical font stacks while javascript and CSS improvements and adoption push us forward.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Шрифтове в уеб &#8211; свободно споделяне или услуги &#8211; посредници &#124; Блогът на Гонзо</title>
		<link>http://ilovetypography.com/2009/08/07/the-font-as-service/#comment-16922</link>
		<dc:creator>Шрифтове в уеб &#8211; свободно споделяне или услуги &#8211; посредници &#124; Блогът на Гонзо</dc:creator>
		<pubDate>Mon, 24 Aug 2009 06:42:05 +0000</pubDate>
		<guid isPermaLink="false">http://ilovetypography.com/?p=5953#comment-16922</guid>
		<description>[...] The Font-as-Service &#8211; i love typography [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] The Font-as-Service &#8211; i love typography [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Links of the Week 11 - Inspect Element</title>
		<link>http://ilovetypography.com/2009/08/07/the-font-as-service/#comment-16893</link>
		<dc:creator>Links of the Week 11 - Inspect Element</dc:creator>
		<pubDate>Fri, 21 Aug 2009 16:27:54 +0000</pubDate>
		<guid isPermaLink="false">http://ilovetypography.com/?p=5953#comment-16893</guid>
		<description>[...] The Font-as-Service [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] The Font-as-Service [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elliot Jay Stocks</title>
		<link>http://ilovetypography.com/2009/08/07/the-font-as-service/#comment-16880</link>
		<dc:creator>Elliot Jay Stocks</dc:creator>
		<pubDate>Thu, 20 Aug 2009 14:04:58 +0000</pubDate>
		<guid isPermaLink="false">http://ilovetypography.com/?p=5953#comment-16880</guid>
		<description>Thanks for your thoughts, everyone. And what a huge honour to have comments from Jonathan and Erik — thank you, gentlemen!

&lt;strong&gt;Jason and Jeffrey:&lt;/strong&gt; I apologise heartily if this came across as sounding anti-Typekit. This certainly wasn&#039;t my intention. I really appreciate you clarifying the point about the font stacks and I&#039;m so excited with the way Typekit is going. You might be interested to read my latest post:&lt;a href=&quot;http://elliotjaystocks.com/blog/more-reasons-to-get-excited-about-typekit/&quot; rel=&quot;nofollow&quot;&gt;More reasons to get excited about Typekit&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Thanks for your thoughts, everyone. And what a huge honour to have comments from Jonathan and Erik — thank you, gentlemen!</p>
<p><strong>Jason and Jeffrey:</strong> I apologise heartily if this came across as sounding anti-Typekit. This certainly wasn&#8217;t my intention. I really appreciate you clarifying the point about the font stacks and I&#8217;m so excited with the way Typekit is going. You might be interested to read my latest post:<a href="http://elliotjaystocks.com/blog/more-reasons-to-get-excited-about-typekit/" rel="nofollow">More reasons to get excited about Typekit</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Liz Castro</title>
		<link>http://ilovetypography.com/2009/08/07/the-font-as-service/#comment-16866</link>
		<dc:creator>Liz Castro</dc:creator>
		<pubDate>Tue, 18 Aug 2009 18:51:29 +0000</pubDate>
		<guid isPermaLink="false">http://ilovetypography.com/?p=5953#comment-16866</guid>
		<description>I&#039;d like to second James Puckett&#039;s recommendation that you look at Kernest.com. It&#039;s up and running and works great. (I&#039;ve written a tutorial for using Kernest fonts on my blog (see http://bit.ly/bjT4u)

I&#039;d love to beta-test and document the rest of them myself!</description>
		<content:encoded><![CDATA[<p>I&#8217;d like to second James Puckett&#8217;s recommendation that you look at Kernest.com. It&#8217;s up and running and works great. (I&#8217;ve written a tutorial for using Kernest fonts on my blog (see <a href="http://bit.ly/bjT4u" rel="nofollow">http://bit.ly/bjT4u</a>)</p>
<p>I&#8217;d love to beta-test and document the rest of them myself!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Houghton</title>
		<link>http://ilovetypography.com/2009/08/07/the-font-as-service/#comment-16812</link>
		<dc:creator>Ian Houghton</dc:creator>
		<pubDate>Sun, 16 Aug 2009 02:51:35 +0000</pubDate>
		<guid isPermaLink="false">http://ilovetypography.com/?p=5953#comment-16812</guid>
		<description>Fontdeck has my vote for the logo alone, although I do like Typotheque&#039;s name.  Regular CSS support without messing around with JS is a bonus!</description>
		<content:encoded><![CDATA[<p>Fontdeck has my vote for the logo alone, although I do like Typotheque&#8217;s name.  Regular CSS support without messing around with JS is a bonus!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randomness, vol. IX - Programming Blog</title>
		<link>http://ilovetypography.com/2009/08/07/the-font-as-service/#comment-16778</link>
		<dc:creator>Randomness, vol. IX - Programming Blog</dc:creator>
		<pubDate>Fri, 14 Aug 2009 23:15:19 +0000</pubDate>
		<guid isPermaLink="false">http://ilovetypography.com/?p=5953#comment-16778</guid>
		<description>[...] The Font-as-Service [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] The Font-as-Service [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew M</title>
		<link>http://ilovetypography.com/2009/08/07/the-font-as-service/#comment-16740</link>
		<dc:creator>Andrew M</dc:creator>
		<pubDate>Fri, 14 Aug 2009 01:23:03 +0000</pubDate>
		<guid isPermaLink="false">http://ilovetypography.com/?p=5953#comment-16740</guid>
		<description>Only time will tell. Great summary of the situation. 

It seems odd Adobe or another big name has not jumped into this and created a service. Maybe they don&#039;t see a profit in it. Maybe they&#039;re working on it. I could see a Dreaweaver font selector tool similar to selecting a song from the iTunes store.</description>
		<content:encoded><![CDATA[<p>Only time will tell. Great summary of the situation. </p>
<p>It seems odd Adobe or another big name has not jumped into this and created a service. Maybe they don&#8217;t see a profit in it. Maybe they&#8217;re working on it. I could see a Dreaweaver font selector tool similar to selecting a song from the iTunes store.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Dunn</title>
		<link>http://ilovetypography.com/2009/08/07/the-font-as-service/#comment-16717</link>
		<dc:creator>Nick Dunn</dc:creator>
		<pubDate>Thu, 13 Aug 2009 13:54:02 +0000</pubDate>
		<guid isPermaLink="false">http://ilovetypography.com/?p=5953#comment-16717</guid>
		<description>One question I have yet to see answered is where existing licences will be valid. Not actually *owning* the font files themselves means that creating Photoshop comps for the client is going to be costly — won&#039;t we have to buy the font twice — once as an offline licence and another through Typekit/Font Deck?</description>
		<content:encoded><![CDATA[<p>One question I have yet to see answered is where existing licences will be valid. Not actually *owning* the font files themselves means that creating Photoshop comps for the client is going to be costly — won&#8217;t we have to buy the font twice — once as an offline licence and another through Typekit/Font Deck?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Content Delivery Network via cdn.ilovetypography.com

Served from: ilovetypography.com @ 2012-02-09 09:36:34 -->
