<?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: The 5 Steps of Intelligent Proofreading</title>
	<atom:link href="http://www.teleread.com/ebooks/typos-and-intelligent-proofreading/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.teleread.com/ebooks/typos-and-intelligent-proofreading/</link>
	<description>News &#38; views on e-books, libraries, publishing and related topics</description>
	<lastBuildDate>Wed, 19 Jun 2013 02:04:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Michael W. Perry</title>
		<link>http://www.teleread.com/ebooks/typos-and-intelligent-proofreading/comment-page-1/#comment-1225342</link>
		<dc:creator>Michael W. Perry</dc:creator>
		<pubDate>Sun, 23 Dec 2012 20:28:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.com/?p=75850#comment-1225342</guid>
		<description>I&#039;ll second Marilyn&#039;s remark about the value of text-to-speech. By using another sense, it gets around the problem of seeing what we think is there rather than what is really there.  The best way is to have the text read to you while you follow along. The most dangerous sorts of typos are those that make grammatical sense. I once found one where &quot;now&quot; was substituted for &quot;not.&quot; With practice, you can even develop and ear that picks up the difference in pause, in some text-to-speech software,  between a period and a comma. 

SBT is also right about regular expression searches. I once had to clean up an OCRed document for Microsoft that was filled with the letter l substituted for the number 1. The two didn&#039;t look that different, so finding them by eye would have been a pain. Instead, I did massive search and replaces. That was much quicker and error free.

I&#039;d add another suggestion for those who&#039;ve got an epaper reader or a tablet. Export what you&#039;re proofing to it. The change in appearance from your computer screen will make many typos pop out just as effectively as printing to paper and without the expense of paper.</description>
		<content:encoded><![CDATA[<p>I&#8217;ll second Marilyn&#8217;s remark about the value of text-to-speech. By using another sense, it gets around the problem of seeing what we think is there rather than what is really there.  The best way is to have the text read to you while you follow along. The most dangerous sorts of typos are those that make grammatical sense. I once found one where &#8220;now&#8221; was substituted for &#8220;not.&#8221; With practice, you can even develop and ear that picks up the difference in pause, in some text-to-speech software,  between a period and a comma. </p>
<p>SBT is also right about regular expression searches. I once had to clean up an OCRed document for Microsoft that was filled with the letter l substituted for the number 1. The two didn&#8217;t look that different, so finding them by eye would have been a pain. Instead, I did massive search and replaces. That was much quicker and error free.</p>
<p>I&#8217;d add another suggestion for those who&#8217;ve got an epaper reader or a tablet. Export what you&#8217;re proofing to it. The change in appearance from your computer screen will make many typos pop out just as effectively as printing to paper and without the expense of paper.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SBT</title>
		<link>http://www.teleread.com/ebooks/typos-and-intelligent-proofreading/comment-page-1/#comment-1225165</link>
		<dc:creator>SBT</dc:creator>
		<pubDate>Sat, 22 Dec 2012 19:04:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.com/?p=75850#comment-1225165</guid>
		<description>I am also just a happy amateur, but I have found great use for regular expressions when proofreading. They can test for nonsense like a capital letter immediately after a lower case one, a numeral immediately after a letter, a punctuation mark immediately before a letter, all isolated letters except &#039;a&#039; etc. etc.

When proofreading, I like to create a document with the scan as an image on one side and the OCR&#039;ed text on the other, so it is straightforward to compare the OCR with the source. The problem with proofreading without the source immediately available is that errors are not always readily apparent from the ocr text; even complete lines can go missing sometimes and the text will still make sense.</description>
		<content:encoded><![CDATA[<p>I am also just a happy amateur, but I have found great use for regular expressions when proofreading. They can test for nonsense like a capital letter immediately after a lower case one, a numeral immediately after a letter, a punctuation mark immediately before a letter, all isolated letters except &#8216;a&#8217; etc. etc.</p>
<p>When proofreading, I like to create a document with the scan as an image on one side and the OCR&#8217;ed text on the other, so it is straightforward to compare the OCR with the source. The problem with proofreading without the source immediately available is that errors are not always readily apparent from the ocr text; even complete lines can go missing sometimes and the text will still make sense.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marilynn Byerly</title>
		<link>http://www.teleread.com/ebooks/typos-and-intelligent-proofreading/comment-page-1/#comment-1225145</link>
		<dc:creator>Marilynn Byerly</dc:creator>
		<pubDate>Sat, 22 Dec 2012 16:14:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.com/?p=75850#comment-1225145</guid>
		<description>I&#039;m not a professional proofreader, but I&#039;ve done the electronic galleys of all my books before they were published.  Here&#039;s my usual recommendations to other writers.  They can use only one method or do several proofs using different methods each time.

Use text to speech, all computers come with it, to have your computer read it aloud.  In the preferences, set the talking speed a bit faster than usual so you won&#039;t lose focus.  

Change the font and text size.  Make it much bigger than normal so those misplaced commas really stand out.  If you begin to skim, change the size again.  

If you have an ereader, transfer your book to it.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not a professional proofreader, but I&#8217;ve done the electronic galleys of all my books before they were published.  Here&#8217;s my usual recommendations to other writers.  They can use only one method or do several proofs using different methods each time.</p>
<p>Use text to speech, all computers come with it, to have your computer read it aloud.  In the preferences, set the talking speed a bit faster than usual so you won&#8217;t lose focus.  </p>
<p>Change the font and text size.  Make it much bigger than normal so those misplaced commas really stand out.  If you begin to skim, change the size again.  </p>
<p>If you have an ereader, transfer your book to it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Database Caching using disk: basic
Object Caching 351/381 objects using disk: basic

Served from: www.teleread.com @ 2013-06-18 23:07:26 -->