<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Readable Web &#187; Uncategorized</title>
	<atom:link href="http://readableweb.com/category/uncategorized/feed/" rel="self" type="application/rss+xml" />
	<link>http://readableweb.com</link>
	<description>Tracking The Move From Print To The Networked Screen</description>
	<lastBuildDate>Tue, 07 Sep 2010 12:50:42 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>Moving From Print To Screen: A Case Study From Joe Clark</title>
		<link>http://readableweb.com/moving-from-print-to-screen-a-case-study-from-joe-clark/</link>
		<comments>http://readableweb.com/moving-from-print-to-screen-a-case-study-from-joe-clark/#comments</comments>
		<pubDate>Wed, 22 Jul 2009 17:47:01 +0000</pubDate>
		<dc:creator>Richard Fink</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://readableweb.com/?p=1009</guid>
		<description><![CDATA[In the current issue of AlistApart, in an article titled Unwebbable, author Joe Clark analyzes the problem of translating a very task-&#8203;specific print format &#8211; in this case, a screenplay &#8211; into an HTML document. He writes: The web is replete with projects to “digitize legacy content”—patent applications, books, photographs, everything. While photographs might survive [...]


Related posts:<ol><li><a href='http://readableweb.com/fixing-web-fonts-a-case-study/' rel='bookmark' title='Permanent Link: Fixing Web Fonts, A Case Study'>Fixing Web Fonts, A Case Study</a></li>
<li><a href='http://readableweb.com/ten-great-free-fonts-cross-browser-a-case-study-in-font-face/' rel='bookmark' title='Permanent Link: Ten Great Free Fonts Cross-Browser: A Case Study In @Font-Face'>Ten Great Free Fonts Cross-Browser: A Case Study In @Font-Face</a></li>
<li><a href='http://readableweb.com/screen-resolution-and-readability-what-you-should-know/' rel='bookmark' title='Permanent Link: Screen Resolution And Readability: What You Should Know'>Screen Resolution And Readability: What You Should Know</a></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p></p><p id="sp">In the current issue of AlistApart, in an article titled <a href="http://www.alistapart.com/articles/unwebbable/">Unwebbable</a>, author <a href="http://blog.fawny.org/">Joe Clark</a> analyzes the problem of translating a very task-&#8203;specific print format &#8211; in this case, a screenplay &#8211; into an HTML document. </p>
<p>He writes:</p>
<blockquote><p>
The web is replete with projects to “digitize legacy content”—patent applications, books, photographs, everything. While photographs might survive well as JPEGs or TIFFs (disregarding accessibility issues for a moment), the bulk of this legacy content requires semantic markup for computers to understand it. A sheet of paper provides complete authorial freedom, but that freedom can translate poorly to the coarse semantics of HTML. The digitization craze—that’s what it is—crashes headlong into HTML semantics.</p></blockquote>
<p>But &#8220;the digitization craze&#8221;, as Joe describes it, is not a craze in the sense of a fad that will dissipate in time. It&#8217;s going to continue to occupy a lot of people&#8217;s time and attention and money. And keep us crazy for many <strong>decades</strong> to come. The world is moving from print to screen, what remains unanswered is, &#8220;How are we going to manage the transition?&#8221;</p>
<p>A must-read for anyone trying to figure out how to move print documents onscreen. And a great example of the kind of analysis that Readable Web is hoping to provide. You beat me to it, Joe!</p>
<h2>Addendum: Wait, There&#8217;s More!</h2>
<p>Turns out the article for AlistApart was heavily edited. A <a href="http://blog.fawny.org/2009/07/22/uncastoffable/">post</a> on Joe Clark&#8217;s blog explains, with links to the whole enchilada.</p>


<p>Related posts:<ol><li><a href='http://readableweb.com/fixing-web-fonts-a-case-study/' rel='bookmark' title='Permanent Link: Fixing Web Fonts, A Case Study'>Fixing Web Fonts, A Case Study</a></li>
<li><a href='http://readableweb.com/ten-great-free-fonts-cross-browser-a-case-study-in-font-face/' rel='bookmark' title='Permanent Link: Ten Great Free Fonts Cross-Browser: A Case Study In @Font-Face'>Ten Great Free Fonts Cross-Browser: A Case Study In @Font-Face</a></li>
<li><a href='http://readableweb.com/screen-resolution-and-readability-what-you-should-know/' rel='bookmark' title='Permanent Link: Screen Resolution And Readability: What You Should Know'>Screen Resolution And Readability: What You Should Know</a></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://readableweb.com/moving-from-print-to-screen-a-case-study-from-joe-clark/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
	</channel>
</rss>
