<?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: Cites &amp; Insights 9:4 (March 2009) now available</title>
	<atom:link href="http://walt.lishost.org/2009/02/cites-insights-94-march-2009-now-available/feed/" rel="self" type="application/rss+xml" />
	<link>http://walt.lishost.org/2009/02/cites-insights-94-march-2009-now-available/</link>
	<description>The library voice of the radical middle.</description>
	<lastBuildDate>Sun, 12 Feb 2012 16:45:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: walt</title>
		<link>http://walt.lishost.org/2009/02/cites-insights-94-march-2009-now-available/comment-page-1/#comment-35948</link>
		<dc:creator>walt</dc:creator>
		<pubDate>Sun, 22 Feb 2009 22:44:23 +0000</pubDate>
		<guid isPermaLink="false">http://walt.lishost.org/?p=1071#comment-35948</guid>
		<description>Joe, I don&#039;t know if you&#039;re new to Cites &amp; Insights or if you&#039;re just fond of kicking gift horses in the teeth, but:

Cites &amp; Insights is designed &lt;i&gt;as a print publication,&lt;/i&gt; distributed via the web.

At the request of several readers, I&#039;m providing HTML versions of most essays--but the HTML is absolutely, 100%, deliberately an afterthought. Done the only trivially-easy way I know how, which means switching Word templates and writing out filtered HTML. (Suggestions for various tools and workstreams I could use to generate prettier HTML output not accepted unless you can demonstrate that it would take me less than half an hour per issue to do that, at no cost for new software or platforms.)

So my answer&#039;s simple: If you find it unreadable &lt;b&gt;don&#039;t read it.&lt;/b&gt; I&#039;m reasonably proud of the typography and layout for Cites &amp; Insights itself, but the HTML version is &lt;b&gt;an afterthought.&lt;/b&gt; 

I do appreciate the nature of the wording, though: It clarifies your interest in a constructive discussion. &quot;Atrocious&quot; is such a nice opening point.</description>
		<content:encoded><![CDATA[<p>Joe, I don&#8217;t know if you&#8217;re new to Cites &#038; Insights or if you&#8217;re just fond of kicking gift horses in the teeth, but:</p>
<p>Cites &#038; Insights is designed <i>as a print publication,</i> distributed via the web.</p>
<p>At the request of several readers, I&#8217;m providing HTML versions of most essays&#8211;but the HTML is absolutely, 100%, deliberately an afterthought. Done the only trivially-easy way I know how, which means switching Word templates and writing out filtered HTML. (Suggestions for various tools and workstreams I could use to generate prettier HTML output not accepted unless you can demonstrate that it would take me less than half an hour per issue to do that, at no cost for new software or platforms.)</p>
<p>So my answer&#8217;s simple: If you find it unreadable <b>don&#8217;t read it.</b> I&#8217;m reasonably proud of the typography and layout for Cites &#038; Insights itself, but the HTML version is <b>an afterthought.</b> </p>
<p>I do appreciate the nature of the wording, though: It clarifies your interest in a constructive discussion. &#8220;Atrocious&#8221; is such a nice opening point.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Clark</title>
		<link>http://walt.lishost.org/2009/02/cites-insights-94-march-2009-now-available/comment-page-1/#comment-35946</link>
		<dc:creator>Joe Clark</dc:creator>
		<pubDate>Sun, 22 Feb 2009 22:33:11 +0000</pubDate>
		<guid isPermaLink="false">http://walt.lishost.org/?p=1071#comment-35946</guid>
		<description>Itâ€™s â€œnot as readableâ€Â because your typography is atrocious. Wall-to-wall Palatino with almost zero whitespace and not enough lead makes for unreadable copy.</description>
		<content:encoded><![CDATA[<p>Itâ€™s â€œnot as readableâ€Â because your typography is atrocious. Wall-to-wall Palatino with almost zero whitespace and not enough lead makes for unreadable copy.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

