<?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: Font linking, type foundries, and&#160;DRM</title>
	<atom:link href="http://bradt.ca/archives/font-linking-type-foundries-and-drm/feed/" rel="self" type="application/rss+xml" />
	<link>http://bradt.ca/archives/font-linking-type-foundries-and-drm/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=font-linking-type-foundries-and-drm</link>
	<description>Independent web developer, web designer, and entrepreneur living in Halifax, Canada.</description>
	<lastBuildDate>Wed, 16 May 2012 01:30:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: A Call For Open Sourcing Our Fonts &#8212; Some Random Dude</title>
		<link>http://bradt.ca/archives/font-linking-type-foundries-and-drm/comment-page-1/#comment-34215</link>
		<dc:creator>A Call For Open Sourcing Our Fonts &#8212; Some Random Dude</dc:creator>
		<pubDate>Thu, 26 Feb 2009 10:11:29 +0000</pubDate>
		<guid isPermaLink="false">http://bradt.ca/?p=615#comment-34215</guid>
		<description>[...] embedding becomes commonplace on sites catering to current generation browsers. There is a large collection of blog articles discussing the obvious ramifications of embedding commercially-licensed fonts, the [...]</description>
		<content:encoded><![CDATA[<p>[...] embedding becomes commonplace on sites catering to current generation browsers. There is a large collection of blog articles discussing the obvious ramifications of embedding commercially-licensed fonts, the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bradt</title>
		<link>http://bradt.ca/archives/font-linking-type-foundries-and-drm/comment-page-1/#comment-34180</link>
		<dc:creator>bradt</dc:creator>
		<pubDate>Sun, 14 Dec 2008 22:45:25 +0000</pubDate>
		<guid isPermaLink="false">http://bradt.ca/?p=615#comment-34180</guid>
		<description>If the font is slow to load (or fails), it will add a lot of lag to your web site which is a very big deal.  And again, what happens if they close up shop?  All customers get screwed out of their money.

I certainly appreciate the problem of fonts being taken for granted but I believe that a font store that delivers a pleasant experience and sensible licenses is what is needed. I completely disagree that any type of DRM will be an effective solution.</description>
		<content:encoded><![CDATA[<p>If the font is slow to load (or fails), it will add a lot of lag to your web site which is a very big deal.  And again, what happens if they close up shop?  All customers get screwed out of their money.</p>
<p>I certainly appreciate the problem of fonts being taken for granted but I believe that a font store that delivers a pleasant experience and sensible licenses is what is needed. I completely disagree that any type of DRM will be an effective solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rene</title>
		<link>http://bradt.ca/archives/font-linking-type-foundries-and-drm/comment-page-1/#comment-34179</link>
		<dc:creator>Rene</dc:creator>
		<pubDate>Fri, 12 Dec 2008 15:40:09 +0000</pubDate>
		<guid isPermaLink="false">http://bradt.ca/?p=615#comment-34179</guid>
		<description>It&#039;s really no big deal if it failed. I would just revert back to a web font. Just like with sIFR -- if you don&#039;t have it, no biggie. Not visually perfect, but at least nothing breaks and functionality is maintained. 

I&#039;m not saying it&#039;s perfect, but at least it&#039;s somewhat of a middle ground. 

Being a bit of a type freak, I&#039;m concerned at how type, more than any other art, is taken for granted. It&#039;s almost like everyone expect fonts to be free. And that can last forever if we want access to quality fonts.</description>
		<content:encoded><![CDATA[<p>It&#8217;s really no big deal if it failed. I would just revert back to a web font. Just like with sIFR &#8212; if you don&#8217;t have it, no biggie. Not visually perfect, but at least nothing breaks and functionality is maintained. </p>
<p>I&#8217;m not saying it&#8217;s perfect, but at least it&#8217;s somewhat of a middle ground. </p>
<p>Being a bit of a type freak, I&#8217;m concerned at how type, more than any other art, is taken for granted. It&#8217;s almost like everyone expect fonts to be free. And that can last forever if we want access to quality fonts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad</title>
		<link>http://bradt.ca/archives/font-linking-type-foundries-and-drm/comment-page-1/#comment-34178</link>
		<dc:creator>Brad</dc:creator>
		<pubDate>Fri, 12 Dec 2008 07:00:12 +0000</pubDate>
		<guid isPermaLink="false">http://bradt.ca/?p=615#comment-34178</guid>
		<description>Yea, I&#039;ve heard that proposition before but I don&#039;t like it.  I have little faith that the type foundries would do a good job hosting the fonts.  And what happens when one shuts down?  It&#039;s MSN Music all over again.</description>
		<content:encoded><![CDATA[<p>Yea, I&#8217;ve heard that proposition before but I don&#8217;t like it.  I have little faith that the type foundries would do a good job hosting the fonts.  And what happens when one shuts down?  It&#8217;s MSN Music all over again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rene</title>
		<link>http://bradt.ca/archives/font-linking-type-foundries-and-drm/comment-page-1/#comment-34161</link>
		<dc:creator>Rene</dc:creator>
		<pubDate>Wed, 03 Dec 2008 01:07:37 +0000</pubDate>
		<guid isPermaLink="false">http://bradt.ca/?p=615#comment-34161</guid>
		<description>What type foundries should do is host the fonts and sell the access. CSS @font-face permits external hosted fonts, and with type foundries hosting them and selling licenses/access  sounds like a better solution for everyone. That way they control font usage per domain (or something like that). I&#039;m sure that can&#039;t be too technically difficult.</description>
		<content:encoded><![CDATA[<p>What type foundries should do is host the fonts and sell the access. CSS @font-face permits external hosted fonts, and with type foundries hosting them and selling licenses/access  sounds like a better solution for everyone. That way they control font usage per domain (or something like that). I&#8217;m sure that can&#8217;t be too technically difficult.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

