<?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: Towards Using Custom Fonts</title>
	<atom:link href="http://ajaxian.com/archives/towards-using-custom-fonts/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/towards-using-custom-fonts</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 09 Feb 2012 06:55:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
	<item>
		<title>By: westonruter</title>
		<link>http://ajaxian.com/archives/towards-using-custom-fonts/comment-page-1#comment-266974</link>
		<dc:creator>westonruter</dc:creator>
		<pubDate>Wed, 27 Aug 2008 22:22:58 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=4212#comment-266974</guid>
		<description>While this solution does work, it is also problematic: the client potentially downloads both font files and then throws away the one it doesn’t understand; this problem of wasted HTTP request is intensified by the fact that font files are often quite big (note that Safari appears to skip downloading font files that end in “.eot”, but MSIE doesn’t skip files that end in “.ttf”). There is a more efficient way to serve these font.

Here, I believe, is an improvement: http://weston.ruter.net/2008/08/27/efficiently-serving-custom-web-fonts/</description>
		<content:encoded><![CDATA[<p>While this solution does work, it is also problematic: the client potentially downloads both font files and then throws away the one it doesn’t understand; this problem of wasted HTTP request is intensified by the fact that font files are often quite big (note that Safari appears to skip downloading font files that end in “.eot”, but MSIE doesn’t skip files that end in “.ttf”). There is a more efficient way to serve these font.</p>
<p>Here, I believe, is an improvement: <a href="http://weston.ruter.net/2008/08/27/efficiently-serving-custom-web-fonts/" rel="nofollow">http://weston.ruter.net/2008/08/27/efficiently-serving-custom-web-fonts/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nosredna</title>
		<link>http://ajaxian.com/archives/towards-using-custom-fonts/comment-page-1#comment-266967</link>
		<dc:creator>Nosredna</dc:creator>
		<pubDate>Wed, 27 Aug 2008 14:30:21 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=4212#comment-266967</guid>
		<description>&gt;&gt;Soon-to-be ubiquitous  (somehow, we&#039;ll get there)...

The final IE8 better have it native, or peasants will riot.</description>
		<content:encoded><![CDATA[<p>&gt;&gt;Soon-to-be ubiquitous  (somehow, we&#8217;ll get there)&#8230;</p>
<p>The final IE8 better have it native, or peasants will riot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ChrisHuff</title>
		<link>http://ajaxian.com/archives/towards-using-custom-fonts/comment-page-1#comment-266964</link>
		<dc:creator>ChrisHuff</dc:creator>
		<pubDate>Wed, 27 Aug 2008 14:09:22 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=4212#comment-266964</guid>
		<description>I used to use image replacement techniques, but I recently stumbled upon &lt;a href=&quot;http://www.joaomak.net/util/dtr/&quot; rel=&quot;nofollow&quot;&gt;a dynamic text replacement technique&lt;/a&gt; that looks very promising.  Granted, it&#039;s not as cool as a browser simply supporting custom fonts with no additional scripting, but it does seem to do the trick.  I haven&#039;t used it on any live sites yet, but I definitely intend to!</description>
		<content:encoded><![CDATA[<p>I used to use image replacement techniques, but I recently stumbled upon <a href="http://www.joaomak.net/util/dtr/" rel="nofollow">a dynamic text replacement technique</a> that looks very promising.  Granted, it&#8217;s not as cool as a browser simply supporting custom fonts with no additional scripting, but it does seem to do the trick.  I haven&#8217;t used it on any live sites yet, but I definitely intend to!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

