<?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: Author query: The good and the bad of copyediting</title>
	<atom:link href="http://deannahoak.com/2006/10/01/author-query-the-good-and-the-bad-of-copyediting/feed/" rel="self" type="application/rss+xml" />
	<link>http://deannahoak.com/2006/10/01/author-query-the-good-and-the-bad-of-copyediting/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=author-query-the-good-and-the-bad-of-copyediting</link>
	<description>SF/F Copyeditor</description>
	<lastBuildDate>Fri, 11 May 2012 10:50:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: The good and the bad of copyediting &#171; Web Writer</title>
		<link>http://deannahoak.com/2006/10/01/author-query-the-good-and-the-bad-of-copyediting/comment-page-1/#comment-4187</link>
		<dc:creator>The good and the bad of copyediting &#171; Web Writer</dc:creator>
		<pubDate>Tue, 17 Oct 2006 13:10:39 +0000</pubDate>
		<guid isPermaLink="false">http://deannahoak.com/2006/10/01/author-query-the-good-and-the-bad-of-copyediting/#comment-4187</guid>
		<description>[...] Author query: The good and the bad of copyediting at Deanna Hoak [...]</description>
		<content:encoded><![CDATA[<p>[...] Author query: The good and the bad of copyediting at Deanna Hoak [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patricia Bray</title>
		<link>http://deannahoak.com/2006/10/01/author-query-the-good-and-the-bad-of-copyediting/comment-page-1/#comment-3610</link>
		<dc:creator>Patricia Bray</dc:creator>
		<pubDate>Wed, 04 Oct 2006 16:11:47 +0000</pubDate>
		<guid isPermaLink="false">http://deannahoak.com/2006/10/01/author-query-the-good-and-the-bad-of-copyediting/#comment-3610</guid>
		<description>When I was writing Regency romances I once had a copyeditor who replaced the majority of my commas with semicolons, apparently on a whim.  She was also bored by the manuscript or pressed for time, since she gave up the semi-colon replacement about halfway through the manuscript, and from that point on there were only a handful of corrections that she bothered to make. 

Chatting with other authors at that publisher revealed that I wasn&#039;t the only one who&#039;d experienced the semicolon queen, and our frantic pleas to our editors meant that she was eventually dropped from the list of freelancers.

The other problem I ran into was that the copyeditors were frequently unfamiliar with period language and usage.  For example, the Earl of Endicott is correctly addressed as Lord Endicott.  He will never be referred to as Lord Stephen Endicott.  Not even if the copyeditor feels that Lord Endicott is too stiff and formal, and decides to change all the heroine&#039;s references to him to &quot;Lord Stephen&quot; instead.

That publisher was known for wildly inconsistent copyedits, so I wasn&#039;t alone in my frustration with them.  Since I&#039;ve moved to writing fantasy for Bantam, my experiences have been overwhelmingly positive.</description>
		<content:encoded><![CDATA[<p>When I was writing Regency romances I once had a copyeditor who replaced the majority of my commas with semicolons, apparently on a whim.  She was also bored by the manuscript or pressed for time, since she gave up the semi-colon replacement about halfway through the manuscript, and from that point on there were only a handful of corrections that she bothered to make. </p>
<p>Chatting with other authors at that publisher revealed that I wasn&#8217;t the only one who&#8217;d experienced the semicolon queen, and our frantic pleas to our editors meant that she was eventually dropped from the list of freelancers.</p>
<p>The other problem I ran into was that the copyeditors were frequently unfamiliar with period language and usage.  For example, the Earl of Endicott is correctly addressed as Lord Endicott.  He will never be referred to as Lord Stephen Endicott.  Not even if the copyeditor feels that Lord Endicott is too stiff and formal, and decides to change all the heroine&#8217;s references to him to &#8220;Lord Stephen&#8221; instead.</p>
<p>That publisher was known for wildly inconsistent copyedits, so I wasn&#8217;t alone in my frustration with them.  Since I&#8217;ve moved to writing fantasy for Bantam, my experiences have been overwhelmingly positive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michele</title>
		<link>http://deannahoak.com/2006/10/01/author-query-the-good-and-the-bad-of-copyediting/comment-page-1/#comment-3592</link>
		<dc:creator>Michele</dc:creator>
		<pubDate>Wed, 04 Oct 2006 02:38:13 +0000</pubDate>
		<guid isPermaLink="false">http://deannahoak.com/2006/10/01/author-query-the-good-and-the-bad-of-copyediting/#comment-3592</guid>
		<description>My experience is limited to technical writing. In some respects I&#039;m lucky... typically the editor (performing a copyedit) marks up changes on the PDF, and I make the changes in my source files.

I get great comments and catches - but when I disagree, it&#039;s easier to question than to get a change &quot;undone&quot;. 

I think the best edit I received was on an article I wrote for a technical writing e-zine. I had written an article about how to get more out of a common tech-writer&#039;s tool. The editor (Deborah Ray) suggested revisions to change the intro into a problem/solution format. It was a new way of thinking about how I organized my writing, and that guidance helped me with more than just that article.</description>
		<content:encoded><![CDATA[<p>My experience is limited to technical writing. In some respects I&#8217;m lucky&#8230; typically the editor (performing a copyedit) marks up changes on the PDF, and I make the changes in my source files.</p>
<p>I get great comments and catches &#8211; but when I disagree, it&#8217;s easier to question than to get a change &#8220;undone&#8221;. </p>
<p>I think the best edit I received was on an article I wrote for a technical writing e-zine. I had written an article about how to get more out of a common tech-writer&#8217;s tool. The editor (Deborah Ray) suggested revisions to change the intro into a problem/solution format. It was a new way of thinking about how I organized my writing, and that guidance helped me with more than just that article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deanna Hoak</title>
		<link>http://deannahoak.com/2006/10/01/author-query-the-good-and-the-bad-of-copyediting/comment-page-1/#comment-3589</link>
		<dc:creator>Deanna Hoak</dc:creator>
		<pubDate>Wed, 04 Oct 2006 00:57:51 +0000</pubDate>
		<guid isPermaLink="false">http://deannahoak.com/2006/10/01/author-query-the-good-and-the-bad-of-copyediting/#comment-3589</guid>
		<description>Aw, thanks, Danny. I hadn&#039;t seen that yet. :-)</description>
		<content:encoded><![CDATA[<p>Aw, thanks, Danny. I hadn&#8217;t seen that yet. :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danny Adams</title>
		<link>http://deannahoak.com/2006/10/01/author-query-the-good-and-the-bad-of-copyediting/comment-page-1/#comment-3588</link>
		<dc:creator>Danny Adams</dc:creator>
		<pubDate>Wed, 04 Oct 2006 00:28:14 +0000</pubDate>
		<guid isPermaLink="false">http://deannahoak.com/2006/10/01/author-query-the-good-and-the-bad-of-copyediting/#comment-3588</guid>
		<description>Not exactly on topic, but sent because we love you, if you haven&#039;t seen it already...

http://community.livejournal.com/cranky_editors/352145.html</description>
		<content:encoded><![CDATA[<p>Not exactly on topic, but sent because we love you, if you haven&#8217;t seen it already&#8230;</p>
<p><a href="http://community.livejournal.com/cranky_editors/352145.html" rel="nofollow">http://community.livejournal.com/cranky_editors/352145.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wendy S. Delmater</title>
		<link>http://deannahoak.com/2006/10/01/author-query-the-good-and-the-bad-of-copyediting/comment-page-1/#comment-3562</link>
		<dc:creator>Wendy S. Delmater</dc:creator>
		<pubDate>Tue, 03 Oct 2006 12:22:40 +0000</pubDate>
		<guid isPermaLink="false">http://deannahoak.com/2006/10/01/author-query-the-good-and-the-bad-of-copyediting/#comment-3562</guid>
		<description>I like to think  that one of the reasons for the uptick in postive reviews for Abyss &amp; Apex since I took the helm is that we don&#039;t just put up stories as-is. If something took extensive rewrites but had a dynamite story underneath worth getting to, we did the work with the authors to make  it so. It might be something as subtle as insisting on circularity like I did with &quot;Museum Beetles&quot;or as draconian as the six months of hair pulling that resulted in the agreed-upon final version of &quot;Emmet, Joey &amp; the Beelz.&quot; 

As for horror stories? Let&#039;s just say I had an author that was so dificult to work with I am inserting a kill-fee clause in our contracts. And I will never buy another thing from the person again. It may be art, but your story is also _product_ and entertainment. If no one &quot;gets&quot; what you are trying to do, I think you need to rethink the whole publication process. Self publish your navel-gazing and be done with it.</description>
		<content:encoded><![CDATA[<p>I like to think  that one of the reasons for the uptick in postive reviews for Abyss &amp; Apex since I took the helm is that we don&#8217;t just put up stories as-is. If something took extensive rewrites but had a dynamite story underneath worth getting to, we did the work with the authors to make  it so. It might be something as subtle as insisting on circularity like I did with &#8220;Museum Beetles&#8221;or as draconian as the six months of hair pulling that resulted in the agreed-upon final version of &#8220;Emmet, Joey &amp; the Beelz.&#8221; </p>
<p>As for horror stories? Let&#8217;s just say I had an author that was so dificult to work with I am inserting a kill-fee clause in our contracts. And I will never buy another thing from the person again. It may be art, but your story is also _product_ and entertainment. If no one &#8220;gets&#8221; what you are trying to do, I think you need to rethink the whole publication process. Self publish your navel-gazing and be done with it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ilona</title>
		<link>http://deannahoak.com/2006/10/01/author-query-the-good-and-the-bad-of-copyediting/comment-page-1/#comment-3519</link>
		<dc:creator>ilona</dc:creator>
		<pubDate>Mon, 02 Oct 2006 10:15:02 +0000</pubDate>
		<guid isPermaLink="false">http://deannahoak.com/2006/10/01/author-query-the-good-and-the-bad-of-copyediting/#comment-3519</guid>
		<description>You know mine :)</description>
		<content:encoded><![CDATA[<p>You know mine :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deanna Hoak</title>
		<link>http://deannahoak.com/2006/10/01/author-query-the-good-and-the-bad-of-copyediting/comment-page-1/#comment-3509</link>
		<dc:creator>Deanna Hoak</dc:creator>
		<pubDate>Mon, 02 Oct 2006 07:48:15 +0000</pubDate>
		<guid isPermaLink="false">http://deannahoak.com/2006/10/01/author-query-the-good-and-the-bad-of-copyediting/#comment-3509</guid>
		<description>Michele: You can use nonfiction; just note that&#039;s what it is.</description>
		<content:encoded><![CDATA[<p>Michele: You can use nonfiction; just note that&#8217;s what it is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Archangel Beth</title>
		<link>http://deannahoak.com/2006/10/01/author-query-the-good-and-the-bad-of-copyediting/comment-page-1/#comment-3502</link>
		<dc:creator>Archangel Beth</dc:creator>
		<pubDate>Mon, 02 Oct 2006 02:37:49 +0000</pubDate>
		<guid isPermaLink="false">http://deannahoak.com/2006/10/01/author-query-the-good-and-the-bad-of-copyediting/#comment-3502</guid>
		<description>When my short story got into Sofawolf&#039;s _Best In Show_, they asked me about the capitalization of one of the alien terms I&#039;d used. (I replied that, reconstructing my intent, one was capitalized and meant &quot;Starship Captain,&quot; and the other was lowercased and meant &quot;tribal leader.&quot; But that I wasn&#039;t insistent on either and would be happy if they decided to change &#039;em. Without looking at the book, I believe that they actually kept the differing capitalizations, for which I coo.)

I&#039;ve never had true copyedits that I disliked, on my fiction. (Now, on my work-for-hire, I&#039;ve had a word cut that totally changed my intent -- &quot;large minority&quot; to &quot;minority&quot;... Grr.)</description>
		<content:encoded><![CDATA[<p>When my short story got into Sofawolf&#8217;s _Best In Show_, they asked me about the capitalization of one of the alien terms I&#8217;d used. (I replied that, reconstructing my intent, one was capitalized and meant &#8220;Starship Captain,&#8221; and the other was lowercased and meant &#8220;tribal leader.&#8221; But that I wasn&#8217;t insistent on either and would be happy if they decided to change &#8216;em. Without looking at the book, I believe that they actually kept the differing capitalizations, for which I coo.)</p>
<p>I&#8217;ve never had true copyedits that I disliked, on my fiction. (Now, on my work-for-hire, I&#8217;ve had a word cut that totally changed my intent &#8212; &#8220;large minority&#8221; to &#8220;minority&#8221;&#8230; Grr.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michele</title>
		<link>http://deannahoak.com/2006/10/01/author-query-the-good-and-the-bad-of-copyediting/comment-page-1/#comment-3501</link>
		<dc:creator>Michele</dc:creator>
		<pubDate>Mon, 02 Oct 2006 02:03:44 +0000</pubDate>
		<guid isPermaLink="false">http://deannahoak.com/2006/10/01/author-query-the-good-and-the-bad-of-copyediting/#comment-3501</guid>
		<description>Are you looking only for comments about fiction copyedits? So far, my experience has been in technical writing.</description>
		<content:encoded><![CDATA[<p>Are you looking only for comments about fiction copyedits? So far, my experience has been in technical writing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

