<?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"
	>
<channel>
	<title>Comments on: Advances in Web typography</title>
	<atom:link href="http://www.atoker.com/blog/2008/01/18/advances-in-web-typography/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.atoker.com/blog/2008/01/18/advances-in-web-typography/</link>
	<description>There is a third way</description>
	<pubDate>Thu, 28 Aug 2008 07:36:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: alp</title>
		<link>http://www.atoker.com/blog/2008/01/18/advances-in-web-typography/#comment-4375</link>
		<dc:creator>alp</dc:creator>
		<pubDate>Mon, 21 Jan 2008 09:12:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.atoker.com/blog/2008/01/18/advances-in-web-typography/#comment-4375</guid>
		<description>sentio: The List Apart @font-face advocacy article is written by Opera Software CTO Håkon Wium Lie so it seems fair to assume that their browser supports it :-)</description>
		<content:encoded><![CDATA[<p>sentio: The List Apart @font-face advocacy article is written by Opera Software CTO Håkon Wium Lie so it seems fair to assume that their browser supports it <img src='http://www.atoker.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sentio</title>
		<link>http://www.atoker.com/blog/2008/01/18/advances-in-web-typography/#comment-4373</link>
		<dc:creator>sentio</dc:creator>
		<pubDate>Mon, 21 Jan 2008 06:17:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.atoker.com/blog/2008/01/18/advances-in-web-typography/#comment-4373</guid>
		<description>As far as I know Opera has no @font-face support. I don't know where you read about it.</description>
		<content:encoded><![CDATA[<p>As far as I know Opera has no @font-face support. I don&#8217;t know where you read about it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alp</title>
		<link>http://www.atoker.com/blog/2008/01/18/advances-in-web-typography/#comment-4249</link>
		<dc:creator>alp</dc:creator>
		<pubDate>Sat, 19 Jan 2008 06:48:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.atoker.com/blog/2008/01/18/advances-in-web-typography/#comment-4249</guid>
		<description>Anonymous: Good idea. I guess we should make sure that it's:

a) Possible to disable auto-download of custom fonts, just like you can already disable image download.

b) Possible to revert custom fonts after a page has loaded, in case the fonts are difficult to read.

I'll look into getting these features added and supported in the SDK. Thanks!</description>
		<content:encoded><![CDATA[<p>Anonymous: Good idea. I guess we should make sure that it&#8217;s:</p>
<p>a) Possible to disable auto-download of custom fonts, just like you can already disable image download.</p>
<p>b) Possible to revert custom fonts after a page has loaded, in case the fonts are difficult to read.</p>
<p>I&#8217;ll look into getting these features added and supported in the SDK. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.atoker.com/blog/2008/01/18/advances-in-web-typography/#comment-4235</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sat, 19 Jan 2008 05:24:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.atoker.com/blog/2008/01/18/advances-in-web-typography/#comment-4235</guid>
		<description>Does WebKit support disabling this feature, forcing pages to use standard fonts instead?</description>
		<content:encoded><![CDATA[<p>Does WebKit support disabling this feature, forcing pages to use standard fonts instead?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oliver</title>
		<link>http://www.atoker.com/blog/2008/01/18/advances-in-web-typography/#comment-4206</link>
		<dc:creator>Oliver</dc:creator>
		<pubDate>Sat, 19 Jan 2008 01:01:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.atoker.com/blog/2008/01/18/advances-in-web-typography/#comment-4206</guid>
		<description>@Alex: Opera supports a large amount of SVG, almost all of it in fact.  ASVG however does not support SVG, it supports a subset of modern SVG but with a large number of non-standard properties.  In fairness that is because ASVG was developed a long time ago prior to more complete definitions of the SVG spec.  It no longer matters anyway as Adobe has discontinued it.  And i believe Batik and Renesis are purely SVG viewers, eg no (or minimal) web proper.</description>
		<content:encoded><![CDATA[<p>@Alex: Opera supports a large amount of SVG, almost all of it in fact.  ASVG however does not support SVG, it supports a subset of modern SVG but with a large number of non-standard properties.  In fairness that is because ASVG was developed a long time ago prior to more complete definitions of the SVG spec.  It no longer matters anyway as Adobe has discontinued it.  And i believe Batik and Renesis are purely SVG viewers, eg no (or minimal) web proper.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://www.atoker.com/blog/2008/01/18/advances-in-web-typography/#comment-4198</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Fri, 18 Jan 2008 23:58:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.atoker.com/blog/2008/01/18/advances-in-web-typography/#comment-4198</guid>
		<description>@Jeff Schiller

Thanks, I never knew Opera supported it (nor the Adobe SVG viewer), great work on their behalf.</description>
		<content:encoded><![CDATA[<p>@Jeff Schiller</p>
<p>Thanks, I never knew Opera supported it (nor the Adobe SVG viewer), great work on their behalf.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WebFonts: il paradiso dei WebDesigner si avvicina &#124;</title>
		<link>http://www.atoker.com/blog/2008/01/18/advances-in-web-typography/#comment-4178</link>
		<dc:creator>WebFonts: il paradiso dei WebDesigner si avvicina &#124;</dc:creator>
		<pubDate>Fri, 18 Jan 2008 21:09:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.atoker.com/blog/2008/01/18/advances-in-web-typography/#comment-4178</guid>
		<description>[...] a Alp Toker che ha oggi ci ha rallegrato con questa notizia e Pollycoke che ha diffuso la [...]</description>
		<content:encoded><![CDATA[<p>[...] a Alp Toker che ha oggi ci ha rallegrato con questa notizia e Pollycoke che ha diffuso la [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://www.atoker.com/blog/2008/01/18/advances-in-web-typography/#comment-4167</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Fri, 18 Jan 2008 19:35:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.atoker.com/blog/2008/01/18/advances-in-web-typography/#comment-4167</guid>
		<description>Holy cow! I just tried this out and it flies! I don't know how Firefox 3 fell so far behind on both features and performance, I thought they had lots of good developers</description>
		<content:encoded><![CDATA[<p>Holy cow! I just tried this out and it flies! I don&#8217;t know how Firefox 3 fell so far behind on both features and performance, I thought they had lots of good developers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alp</title>
		<link>http://www.atoker.com/blog/2008/01/18/advances-in-web-typography/#comment-4164</link>
		<dc:creator>alp</dc:creator>
		<pubDate>Fri, 18 Jan 2008 19:16:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.atoker.com/blog/2008/01/18/advances-in-web-typography/#comment-4164</guid>
		<description>robert: People routinely download fonts off the Web and install them system-wide without raising security concerns. The approach taken in WebKit is in fact more conservative (fonts get loaded in-process and aren't installed to the system) -- just like PDF viewers xpdf and Evince. But even then, you're right of course, we always need to stay vigilant.

Adam Williamson: Since the fonts are loaded in-process, the threat of thousands of font files is no different than the threat of, say, thousands of img tags in a page. There are sanity checks in place to avoid this becoming a problem.</description>
		<content:encoded><![CDATA[<p>robert: People routinely download fonts off the Web and install them system-wide without raising security concerns. The approach taken in WebKit is in fact more conservative (fonts get loaded in-process and aren&#8217;t installed to the system) &#8212; just like PDF viewers xpdf and Evince. But even then, you&#8217;re right of course, we always need to stay vigilant.</p>
<p>Adam Williamson: Since the fonts are loaded in-process, the threat of thousands of font files is no different than the threat of, say, thousands of img tags in a page. There are sanity checks in place to avoid this becoming a problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Williamson</title>
		<link>http://www.atoker.com/blog/2008/01/18/advances-in-web-typography/#comment-4158</link>
		<dc:creator>Adam Williamson</dc:creator>
		<pubDate>Fri, 18 Jan 2008 17:59:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.atoker.com/blog/2008/01/18/advances-in-web-typography/#comment-4158</guid>
		<description>robert: my thoughts exactly.

Also, has anyone considers what happens if I create a page that specifies several thousand very small font files?

Or one *really big* one (for people on modems, or with bandwidth caps)?</description>
		<content:encoded><![CDATA[<p>robert: my thoughts exactly.</p>
<p>Also, has anyone considers what happens if I create a page that specifies several thousand very small font files?</p>
<p>Or one *really big* one (for people on modems, or with bandwidth caps)?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
