<?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: Apple and Microsoft In Talks On Web Font Protections</title>
	<atom:link href="http://readableweb.com/apple-and-microsoft-in-talks-on-web-font-protections/feed/" rel="self" type="application/rss+xml" />
	<link>http://readableweb.com/apple-and-microsoft-in-talks-on-web-font-protections/</link>
	<description>Tracking The Move From Print To The Networked Screen</description>
	<lastBuildDate>Tue, 31 Aug 2010 20:02:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: Richard Fink</title>
		<link>http://readableweb.com/apple-and-microsoft-in-talks-on-web-font-protections/comment-page-1/#comment-6</link>
		<dc:creator>Richard Fink</dc:creator>
		<pubDate>Fri, 12 Jun 2009 22:20:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.readableweb.com/?p=24#comment-6</guid>
		<description>@bowerbird
What you see here right now, at Readable Web, is a typical WordPress installation with a typical theme. It is subject to many deficiencies. But it is free of charge, easy to use, and enables me to publish to the entire world. In view of this, refinements can move to the back-burner for awhile. (This seems to fit the pattern of most emerging technologies: the technology lacks refinement but grows like crazy anyway. And then, when the technology propagates out to near it&#039;s limits,  those back-burner issues move to the fore.)
At Readable Web I make no claim to readability.
The blog is about exactly what the tag line says: &quot;Moving from print, to the networked screen&quot;. At least that&#039;s the plan today. When the &quot;Beta&quot; label comes off in a few weeks, it might have been adjusted.
Cheers,
rich</description>
		<content:encoded><![CDATA[<p>@bowerbird<br />
What you see here right now, at Readable Web, is a typical WordPress installation with a typical theme. It is subject to many deficiencies. But it is free of charge, easy to use, and enables me to publish to the entire world. In view of this, refinements can move to the back-burner for awhile. (This seems to fit the pattern of most emerging technologies: the technology lacks refinement but grows like crazy anyway. And then, when the technology propagates out to near it&#8217;s limits,  those back-burner issues move to the fore.)<br />
At Readable Web I make no claim to readability.<br />
The blog is about exactly what the tag line says: &#8220;Moving from print, to the networked screen&#8221;. At least that&#8217;s the plan today. When the &#8220;Beta&#8221; label comes off in a few weeks, it might have been adjusted.<br />
Cheers,<br />
rich</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bowerbird</title>
		<link>http://readableweb.com/apple-and-microsoft-in-talks-on-web-font-protections/comment-page-1/#comment-5</link>
		<dc:creator>bowerbird</dc:creator>
		<pubDate>Fri, 12 Jun 2009 21:29:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.readableweb.com/?p=24#comment-5</guid>
		<description>wow.

your headings have very little air,
your subheadings have _no_ air,
and your paragraphs have no indents.

_this_ is your idea of a &quot;readable web&quot;?

wow.

-bowerbird</description>
		<content:encoded><![CDATA[<p>wow.</p>
<p>your headings have very little air,<br />
your subheadings have _no_ air,<br />
and your paragraphs have no indents.</p>
<p>_this_ is your idea of a &#8220;readable web&#8221;?</p>
<p>wow.</p>
<p>-bowerbird</p>
]]></content:encoded>
	</item>
</channel>
</rss>
