<?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 Dictionary of Bullshit</title>
	<atom:link href="http://www.kategriffin.net/2010/02/15/the-dictionary-of-bullshit/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kategriffin.net/2010/02/15/the-dictionary-of-bullshit/</link>
	<description>Fantasy Author Kate Griffin</description>
	<lastBuildDate>Fri, 03 Sep 2010 18:29:31 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jenz</title>
		<link>http://www.kategriffin.net/2010/02/15/the-dictionary-of-bullshit/comment-page-1/#comment-181</link>
		<dc:creator>Jenz</dc:creator>
		<pubDate>Thu, 11 Mar 2010 13:28:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.kategriffin.net/?p=430#comment-181</guid>
		<description>And how we are looking forward to this additional dictionary! I enjoyed the first one immensly. If it&#039;s as good as the first, I swear I&#039;ll pop over and cook you all another porter steak casserole.

All the best

Jenz</description>
		<content:encoded><![CDATA[<p>And how we are looking forward to this additional dictionary! I enjoyed the first one immensly. If it&#8217;s as good as the first, I swear I&#8217;ll pop over and cook you all another porter steak casserole.</p>
<p>All the best</p>
<p>Jenz</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AdrianH</title>
		<link>http://www.kategriffin.net/2010/02/15/the-dictionary-of-bullshit/comment-page-1/#comment-143</link>
		<dc:creator>AdrianH</dc:creator>
		<pubDate>Wed, 17 Feb 2010 00:54:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.kategriffin.net/?p=430#comment-143</guid>
		<description>Nice post, Kate, and your experience learned from your parents shows in the quality of your writing. As someone who&#039;s worked in publishing and print for most of his life, there is a person who I would say is just as important as the editor, because although a decision by the editor will be obvious to the author, but not nessessarily to the reader, a sloppy job by this person ruins the reading pleasure of the end user. That person&#039;s the proof reader. I&#039;ve done a fair bit, enough to be driven nuts by a crappy proofing job when I&#039;m reading a book: a big collected set of Arthur C. Clark&#039;s spoilt by an entire page left out near the end of a story, missing paragraphs, or paragraphs repeated, large numbers of literals and spelling errors and poor punctuation... Aaaarrrrrggg!
You seem to be blessed with a publisher who&#039;s doing a really good job, I haven&#039;t had any mistakes leap out at me in any of your books, which is great, and long may it continue, but sadly publishers are not doing so well with ebooks.
Your books are almost certainly digital right through to the printing press, so if they go on to be sold as ebooks, it should be simple to re-format a digital file.
Older books, however, are really suffering. I bought a collection of Larry Niven&#039;s ‘Gil the ARM&#039; stories via Stanza, and I couldn&#039;t finish the first story, it was just unreadable. More recently I bought ‘Diamond Age&#039;, by Neil Stephenson, via the Kindle app, which had errors all through the book, and it was the same ones cropping up every time. It&#039;s glaringly obvious that lazy publishers are getting an office junior to scan printed pages, then run the scans through OCR software, which is miss-reading certain letter combinations. It&#039;s very poor work, and the authors are being done a disservice by their publishers. Yours seem to be on the ball, but keep an eye open for things slipping, it&#039;s not fair on the author, and it&#039;s not at all fair on the customer.</description>
		<content:encoded><![CDATA[<p>Nice post, Kate, and your experience learned from your parents shows in the quality of your writing. As someone who&#8217;s worked in publishing and print for most of his life, there is a person who I would say is just as important as the editor, because although a decision by the editor will be obvious to the author, but not nessessarily to the reader, a sloppy job by this person ruins the reading pleasure of the end user. That person&#8217;s the proof reader. I&#8217;ve done a fair bit, enough to be driven nuts by a crappy proofing job when I&#8217;m reading a book: a big collected set of Arthur C. Clark&#8217;s spoilt by an entire page left out near the end of a story, missing paragraphs, or paragraphs repeated, large numbers of literals and spelling errors and poor punctuation&#8230; Aaaarrrrrggg!<br />
You seem to be blessed with a publisher who&#8217;s doing a really good job, I haven&#8217;t had any mistakes leap out at me in any of your books, which is great, and long may it continue, but sadly publishers are not doing so well with ebooks.<br />
Your books are almost certainly digital right through to the printing press, so if they go on to be sold as ebooks, it should be simple to re-format a digital file.<br />
Older books, however, are really suffering. I bought a collection of Larry Niven&#8217;s ‘Gil the ARM&#8217; stories via Stanza, and I couldn&#8217;t finish the first story, it was just unreadable. More recently I bought ‘Diamond Age&#8217;, by Neil Stephenson, via the Kindle app, which had errors all through the book, and it was the same ones cropping up every time. It&#8217;s glaringly obvious that lazy publishers are getting an office junior to scan printed pages, then run the scans through OCR software, which is miss-reading certain letter combinations. It&#8217;s very poor work, and the authors are being done a disservice by their publishers. Yours seem to be on the ball, but keep an eye open for things slipping, it&#8217;s not fair on the author, and it&#8217;s not at all fair on the customer.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
