<?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: My recommendation to the W3C &#8211; Centralized Web Fonts</title>
	<atom:link href="http://fordinteractive.com/2007/09/my-recommendation-to-the-w3c-centralized-web-fonts/feed/" rel="self" type="application/rss+xml" />
	<link>http://fordinteractive.com/2007/09/my-recommendation-to-the-w3c-centralized-web-fonts/</link>
	<description>thoughts on web design and front-end development</description>
	<lastBuildDate>Fri, 27 Apr 2012 23:32:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Jeremy</title>
		<link>http://fordinteractive.com/2007/09/my-recommendation-to-the-w3c-centralized-web-fonts/#comment-1847</link>
		<dc:creator>Jeremy</dc:creator>
		<pubDate>Fri, 29 Jul 2011 14:29:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.aloestudios.com/blog/2007/my-recommendation-to-the-w3c-centralized-web-fonts/#comment-1847</guid>
		<description>I was wondering about this myself recently. Fonts are a small file size and I wondered why they could not be served from a server the same as an image file. If security is an issue perhaps the browser could interpret the font. Then the OS would not be in the loop similar to Flash embedded fonts. I have read actually that its less of a security issue and more an issue with intellectual property. Which you have addressed in a way ( although a centralized font server still limits the fonts developers can choose from). But a font is no more an intellectual property than an image, and the majority of fonts the average developer would use are free. In conclusion I agree with your suggestion.</description>
		<content:encoded><![CDATA[<p>I was wondering about this myself recently. Fonts are a small file size and I wondered why they could not be served from a server the same as an image file. If security is an issue perhaps the browser could interpret the font. Then the OS would not be in the loop similar to Flash embedded fonts. I have read actually that its less of a security issue and more an issue with intellectual property. Which you have addressed in a way ( although a centralized font server still limits the fonts developers can choose from). But a font is no more an intellectual property than an image, and the majority of fonts the average developer would use are free. In conclusion I agree with your suggestion.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

