<?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: Proofreading the Public Domain</title>
	<atom:link href="http://strange.corante.com/2009/04/01/proofreading-the-public-domain/feed" rel="self" type="application/rss+xml" />
	<link>http://strange.corante.com/2009/04/01/proofreading-the-public-domain</link>
	<description>Picking out patterns in the chaos</description>
	<pubDate>Tue, 22 May 2012 21:00:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Proofreading the public domain &#124; Quill &#38; Quire</title>
		<link>http://strange.corante.com/2009/04/01/proofreading-the-public-domain#comment-5387</link>
		<dc:creator>Proofreading the public domain &#124; Quill &#38; Quire</dc:creator>
		<pubDate>Thu, 09 Apr 2009 18:08:30 +0000</pubDate>
		<guid isPermaLink="false">http://strange.corante.com/2009/04/01/proofreading-the-public-domain#comment-5387</guid>
		<description>[...] in the private, alpha phase, so to sign up, you need to have a valid invitation code (posted here, here, and here). Upon first use, the Book-Size Edits module seems clean, easy to use, and indeed, [...]</description>
		<content:encoded><![CDATA[<p>[...] in the private, alpha phase, so to sign up, you need to have a valid invitation code (posted here, here, and here). Upon first use, the Book-Size Edits module seems clean, easy to use, and indeed, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse Marchand</title>
		<link>http://strange.corante.com/2009/04/01/proofreading-the-public-domain#comment-5361</link>
		<dc:creator>Jesse Marchand</dc:creator>
		<pubDate>Tue, 07 Apr 2009 13:27:30 +0000</pubDate>
		<guid isPermaLink="false">http://strange.corante.com/2009/04/01/proofreading-the-public-domain#comment-5361</guid>
		<description>Whee! I've taken 74a4o4rN.</description>
		<content:encoded><![CDATA[<p>Whee! I&#8217;ve taken 74a4o4rN.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Suw Charman-Anderson</title>
		<link>http://strange.corante.com/2009/04/01/proofreading-the-public-domain#comment-5339</link>
		<dc:creator>Suw Charman-Anderson</dc:creator>
		<pubDate>Sat, 04 Apr 2009 09:33:40 +0000</pubDate>
		<guid isPermaLink="false">http://strange.corante.com/2009/04/01/proofreading-the-public-domain#comment-5339</guid>
		<description>Alhireth-Hotep, found the code, thanks for listing it! 

I do find it really interesting to read books in random order. It's really weird when it's a book you've read and know! Lots of fun though. :D</description>
		<content:encoded><![CDATA[<p>Alhireth-Hotep, found the code, thanks for listing it! </p>
<p>I do find it really interesting to read books in random order. It&#8217;s really weird when it&#8217;s a book you&#8217;ve read and know! Lots of fun though. <img src='http://strange.corante.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alhireth-Hotep</title>
		<link>http://strange.corante.com/2009/04/01/proofreading-the-public-domain#comment-5334</link>
		<dc:creator>Alhireth-Hotep</dc:creator>
		<pubDate>Fri, 03 Apr 2009 22:14:27 +0000</pubDate>
		<guid isPermaLink="false">http://strange.corante.com/2009/04/01/proofreading-the-public-domain#comment-5334</guid>
		<description>Ignore the last post; I was wrong.  I think I grabbed a code from the Chocolate and Vodka post instead -- but I've lost track of which one!  Sorry!</description>
		<content:encoded><![CDATA[<p>Ignore the last post; I was wrong.  I think I grabbed a code from the Chocolate and Vodka post instead &#8212; but I&#8217;ve lost track of which one!  Sorry!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alhireth-Hotep</title>
		<link>http://strange.corante.com/2009/04/01/proofreading-the-public-domain#comment-5333</link>
		<dc:creator>Alhireth-Hotep</dc:creator>
		<pubDate>Fri, 03 Apr 2009 22:13:23 +0000</pubDate>
		<guid isPermaLink="false">http://strange.corante.com/2009/04/01/proofreading-the-public-domain#comment-5333</guid>
		<description>I grabbed code 1EVSwIR9, and am actively going through a bio of James Madison.  Favorite snippet so far: when, trying to demonstrate his position of liberality, he proposed a ratio of five to three (for counting slaves as people, you might recall).  I'm looking forward to big things from Book Oven.</description>
		<content:encoded><![CDATA[<p>I grabbed code 1EVSwIR9, and am actively going through a bio of James Madison.  Favorite snippet so far: when, trying to demonstrate his position of liberality, he proposed a ratio of five to three (for counting slaves as people, you might recall).  I&#8217;m looking forward to big things from Book Oven.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Suw Charman-Anderson</title>
		<link>http://strange.corante.com/2009/04/01/proofreading-the-public-domain#comment-5324</link>
		<dc:creator>Suw Charman-Anderson</dc:creator>
		<pubDate>Thu, 02 Apr 2009 17:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://strange.corante.com/2009/04/01/proofreading-the-public-domain#comment-5324</guid>
		<description>Ardobbs, the reason you got a "Mr." all by itself was probably that the sentence cutting algorithm saw the full stop and thought that it was the end of the sentence. I don't think we have a way to prevent that at the moment. In the original text, the line probably wasn't broken, it's just been chopped in an unfortunate manner. 

Regarding the seemingly orphaned quote marks, whether beginning or end, the best bet is to leave them. There is a way for reviewers to look at entire chapters (and eventually the whole book) as one piece, so they will then spot badly broken lines, inappropriate paragraphs and missing quote marks. For now, the Bite Size Edits is really just about looking for stuff that's plainly wrong. 

Glad you like the interface. It does get addictive after a while. I've been using it a while now, and it still draws me in!</description>
		<content:encoded><![CDATA[<p>Ardobbs, the reason you got a &#8220;Mr.&#8221; all by itself was probably that the sentence cutting algorithm saw the full stop and thought that it was the end of the sentence. I don&#8217;t think we have a way to prevent that at the moment. In the original text, the line probably wasn&#8217;t broken, it&#8217;s just been chopped in an unfortunate manner. </p>
<p>Regarding the seemingly orphaned quote marks, whether beginning or end, the best bet is to leave them. There is a way for reviewers to look at entire chapters (and eventually the whole book) as one piece, so they will then spot badly broken lines, inappropriate paragraphs and missing quote marks. For now, the Bite Size Edits is really just about looking for stuff that&#8217;s plainly wrong. </p>
<p>Glad you like the interface. It does get addictive after a while. I&#8217;ve been using it a while now, and it still draws me in!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ardobbs</title>
		<link>http://strange.corante.com/2009/04/01/proofreading-the-public-domain#comment-5323</link>
		<dc:creator>ardobbs</dc:creator>
		<pubDate>Thu, 02 Apr 2009 02:47:47 +0000</pubDate>
		<guid isPermaLink="false">http://strange.corante.com/2009/04/01/proofreading-the-public-domain#comment-5323</guid>
		<description>qHRed4d0 -- I've used that code.
I do see a problem, aside from the appalling addictiveness, even with dry tomes -- the pleasant design and flowing dissolve from one to the next to the next ... yes, actually, bite-size indeed ... you begin the next snippet before you realize the first has gone, like popcorn at the movies. I had a line that was Mr. That's all, just Mr. And then Madison began the next line. Skip is a great option, where it's physically impossible to delete the line break and force the following line to join up with the Mr. But then there was a line with an end quote and no beginning quote in that line or the preceding. I made a guess then, based on the feel of the language there, that it was not an error; but there's no certainty in that.

Anyway -- it's a lovely editing environment. Well done!!</description>
		<content:encoded><![CDATA[<p>qHRed4d0 &#8212; I&#8217;ve used that code.<br />
I do see a problem, aside from the appalling addictiveness, even with dry tomes &#8212; the pleasant design and flowing dissolve from one to the next to the next &#8230; yes, actually, bite-size indeed &#8230; you begin the next snippet before you realize the first has gone, like popcorn at the movies. I had a line that was Mr. That&#8217;s all, just Mr. And then Madison began the next line. Skip is a great option, where it&#8217;s physically impossible to delete the line break and force the following line to join up with the Mr. But then there was a line with an end quote and no beginning quote in that line or the preceding. I made a guess then, based on the feel of the language there, that it was not an error; but there&#8217;s no certainty in that.</p>
<p>Anyway &#8212; it&#8217;s a lovely editing environment. Well done!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Revealing a Bit of the Book Oven</title>
		<link>http://strange.corante.com/2009/04/01/proofreading-the-public-domain#comment-5321</link>
		<dc:creator>Revealing a Bit of the Book Oven</dc:creator>
		<pubDate>Wed, 01 Apr 2009 19:43:47 +0000</pubDate>
		<guid isPermaLink="false">http://strange.corante.com/2009/04/01/proofreading-the-public-domain#comment-5321</guid>
		<description>[...] The codes went fast! You can find more codes here and here. It&#8217;s late for Suw in the UK, so you may need to try a few codes if they are taken [...]</description>
		<content:encoded><![CDATA[<p>[...] The codes went fast! You can find more codes here and here. It&#8217;s late for Suw in the UK, so you may need to try a few codes if they are taken [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

