<?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: Bill Converted to Images so YOU can&#8217;t read it</title>
	<atom:link href="http://mpwilson.com/2009/02/13/bill-converted-to-images-so-you-cant-read-it/feed/" rel="self" type="application/rss+xml" />
	<link>http://mpwilson.com/2009/02/13/bill-converted-to-images-so-you-cant-read-it/</link>
	<description></description>
	<pubDate>Mon, 21 May 2012 20:36:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Light &#38; Dark</title>
		<link>http://mpwilson.com/2009/02/13/bill-converted-to-images-so-you-cant-read-it/#comment-2421</link>
		<dc:creator>Light &#38; Dark</dc:creator>
		<pubDate>Tue, 17 Feb 2009 06:59:59 +0000</pubDate>
		<guid isPermaLink="false">http://mpwilson.com/?p=3646#comment-2421</guid>
		<description>I had a quick look at the .gov page and had no trouble downloading a 650 page pdf that was regular text as expected - maybe I wasn't looking at the same thing you were talking about though.

And no surprise that a full text dissection effort is already in full swing :)

P</description>
		<content:encoded><![CDATA[<p>I had a quick look at the .gov page and had no trouble downloading a 650 page pdf that was regular text as expected - maybe I wasn&#8217;t looking at the same thing you were talking about though.</p>
<p>And no surprise that a full text dissection effort is already in full swing :)</p>
<p>P</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MikeWilson</title>
		<link>http://mpwilson.com/2009/02/13/bill-converted-to-images-so-you-cant-read-it/#comment-2419</link>
		<dc:creator>MikeWilson</dc:creator>
		<pubDate>Mon, 16 Feb 2009 21:18:38 +0000</pubDate>
		<guid isPermaLink="false">http://mpwilson.com/?p=3646#comment-2419</guid>
		<description>Well I think it's regrettably unknowable.  I tried D/Ling it but gave up.

PDFs don't bother me in the least.  It's a decent (if cumbersome) standard "formal" document format.

There's now a wiki with the full text and dissection efforts going on.</description>
		<content:encoded><![CDATA[<p>Well I think it&#8217;s regrettably unknowable.  I tried D/Ling it but gave up.</p>
<p>PDFs don&#8217;t bother me in the least.  It&#8217;s a decent (if cumbersome) standard &#8220;formal&#8221; document format.</p>
<p>There&#8217;s now a wiki with the full text and dissection efforts going on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Light &#38; Dark</title>
		<link>http://mpwilson.com/2009/02/13/bill-converted-to-images-so-you-cant-read-it/#comment-2418</link>
		<dc:creator>Light &#38; Dark</dc:creator>
		<pubDate>Mon, 16 Feb 2009 21:06:13 +0000</pubDate>
		<guid isPermaLink="false">http://mpwilson.com/?p=3646#comment-2418</guid>
		<description>This is paraphrased, but "don't ascribe to malice what can adequately be explained by ineptitude". I'm betting somebody who didn't really know what they were doing converted the doc to pdf.

I'd say the decision to distribute as PDF was actually the right one (though obviously not as images.) The statement that it should have been published as "a regular internet document" is actually pretty dumb too. PDF &lt;i&gt;is&lt;/i&gt; "a regular internet document". If what they mean is it should have been published as web pages as well as in a downloadable format, OK, but can you imagine the general Internet user trying to save all those web pages for offline reading, or trying to print it? And don't even get me started if what they meant was it should be published as a Word doc.

It's entirely possible they felt they didn't have time to prepare all the individual web pages (and heaven forbid they tried to publish it as all one page!) in time for initial release. (And hours to prepare it as a PDF? Gimme a break.) 

Best answer in my opinion would have been a properly tagged and bookmarked PDF as soon as it was ready, then a properly laid out, standards-compliant series of web pages as soon after as possible. Embarrassing that they didn't have the technical services available to do that for such an important document.

If they anybody really thought that publishing as images was going to keep it from being available in searchable format for more than a couple of hours, they really are incompetent (as you point out Mike, with how an hour or so's work in OCR would resolve that situation.)

I guess the real question in my mind is: did they get any benefit from releasing it, but in a format that wouldn't be searchable for a couple of hours? i.e. did the delay serve a tactical purpose?</description>
		<content:encoded><![CDATA[<p>This is paraphrased, but &#8220;don&#8217;t ascribe to malice what can adequately be explained by ineptitude&#8221;. I&#8217;m betting somebody who didn&#8217;t really know what they were doing converted the doc to pdf.</p>
<p>I&#8217;d say the decision to distribute as PDF was actually the right one (though obviously not as images.) The statement that it should have been published as &#8220;a regular internet document&#8221; is actually pretty dumb too. PDF <i>is</i> &#8220;a regular internet document&#8221;. If what they mean is it should have been published as web pages as well as in a downloadable format, OK, but can you imagine the general Internet user trying to save all those web pages for offline reading, or trying to print it? And don&#8217;t even get me started if what they meant was it should be published as a Word doc.</p>
<p>It&#8217;s entirely possible they felt they didn&#8217;t have time to prepare all the individual web pages (and heaven forbid they tried to publish it as all one page!) in time for initial release. (And hours to prepare it as a PDF? Gimme a break.) </p>
<p>Best answer in my opinion would have been a properly tagged and bookmarked PDF as soon as it was ready, then a properly laid out, standards-compliant series of web pages as soon after as possible. Embarrassing that they didn&#8217;t have the technical services available to do that for such an important document.</p>
<p>If they anybody really thought that publishing as images was going to keep it from being available in searchable format for more than a couple of hours, they really are incompetent (as you point out Mike, with how an hour or so&#8217;s work in OCR would resolve that situation.)</p>
<p>I guess the real question in my mind is: did they get any benefit from releasing it, but in a format that wouldn&#8217;t be searchable for a couple of hours? i.e. did the delay serve a tactical purpose?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

