<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Booksquare &#187; Tools and Craft</title>
	<atom:link href="http://booksquare.com/tags/tools-and-craft/feed/" rel="self" type="application/rss+xml" />
	<link>http://booksquare.com</link>
	<description>Dissecting the publishing industry with love and skepticism</description>
	<lastBuildDate>Wed, 08 Feb 2012 05:29:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Doing It The Write Way</title>
		<link>http://booksquare.com/doing-it-the-write-way/</link>
		<comments>http://booksquare.com/doing-it-the-write-way/#comments</comments>
		<pubDate>Mon, 30 Oct 2006 15:53:13 +0000</pubDate>
		<dc:creator>Kassia Krozser</dc:creator>
				<category><![CDATA[Tools and Craft]]></category>

		<guid isPermaLink="false">http://www.booksquare.com/archives/2006/10/30/2195/</guid>
		<description><![CDATA[Today&#8217;s rant is courtesy of the husband. He casually mentioned that he was reading Copyblogger &#8212; a great post about ending your articles &#8212; and he noted something irritating in the comments section: a writing coach insisting that there was only one good way to brainstorm: hers. As he discussed writing with the ending in [...]]]></description>
			<content:encoded><![CDATA[<p>Today&#8217;s rant is courtesy of the husband. He casually mentioned that he was reading <strong>Copyblogger</strong> &#8212; <a href="http://www.copyblogger.com/closing-call-to-action/">a great post about ending your articles</a> &#8212; and he noted something irritating in the comments section: a writing coach insisting that there was only one good way to brainstorm: hers.</p>
<p>As he discussed writing with the ending in mind, <strong>Copyblogger</strong> noted that some people might benefit from a quick outline. Then came the comment, one we cannot resist quoting:</p>
<blockquote><p>
NO! Outlines are death for writers.
</p></blockquote>
<p><span id="more-2195"></span><br />
Uh, this is not true. We know a lot of writers who use outlines, and, to the best of our knowledge, they remain alive and productive. Our hapless commenter says that mindmapping is the only way to go. The. Only. Way. To. Go. </p>
<p>Yeah. That&#8217;s the ticket. Trade one rule for another. The truth of the matter is that all writers are built differently. Some take to mindmapping (we, alas, do only sometimes). Some fly by the seat of the their pants and, hopefully, fix it in the mix (we do this one, too). Some are strict outliners (again, us sometimes). Others use a blend of techniques, choosing the right tool for the project (this is our preferred technique).</p>
<p>Anytime someone tells you the &#8220;rules&#8221; of writing, run for the hills. Rules are often made up by people who have found success doing things one way, and remain closed to the possibility that other people might achieve similar success in a different way. Thus, they establish rules and swear those rules are the only path to glory. Tools, not rules, we like to say. It&#8217;s like our yoga teacher used to say, &#8220;Take what you can use and throw the rest away.&#8221;</p>
<p>It&#8217;s good advice when you&#8217;re trying to stand on one leg, twisted sideways, one arm raised to the sky, and the other reaching toward the front of the room while trying to focus really hard on pushing energy out through your raised heel&#8230;and it&#8217;s good advice when you&#8217;re writing. Nothing more frustrating than trying to <em>mindmap</em> when your instincts tell you to just go ahead and outline the damn thing. Forcing your brain into a method that feels counter-intuitive almost always ends in frustration.</p>
<p>Endings are important &#8212; we often don&#8217;t consider them enough in our own work &#8212; but there&#8217;s no need to force rules upon other writers. We have enough anxiety as it is.</p>
]]></content:encoded>
			<wfw:commentRss>http://booksquare.com/doing-it-the-write-way/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Highly Effective Blogging: Just Like Highly Effective Writing</title>
		<link>http://booksquare.com/highly-effective-blogging-just-like-highly-effective-writing/</link>
		<comments>http://booksquare.com/highly-effective-blogging-just-like-highly-effective-writing/#comments</comments>
		<pubDate>Fri, 26 May 2006 16:21:20 +0000</pubDate>
		<dc:creator>Booksquare</dc:creator>
				<category><![CDATA[Tools and Craft]]></category>

		<guid isPermaLink="false">http://www.booksquare.com/archives/2006/05/26/1978/</guid>
		<description><![CDATA[Though we are (typically) late to the game, we are going to play along with ProBlogger&#8217;s &#8220;Habits of Highly Effective Bloggers&#8221; game. This, of course, suggests that we are a highly effective blogger. As it turns out, the habits that make for good blogging also make for good writing. Who knew? So, what does make [...]]]></description>
			<content:encoded><![CDATA[<p>Though we are (typically) late to the game, we are going to play along with <strong>ProBlogger&#8217;s</strong> &#8220;Habits of Highly Effective Bloggers&#8221; game. This, of course, suggests that we are a highly effective blogger. As it turns out, the habits that make for good blogging also make for good writing. Who knew?</p>
<p>So, what does make a blogger highly effective? Heck if we know, but this is what works around here:</p>
<p><span id="more-1978"></span></p>
<ol>
<li><strong>Consistency</strong>: Writing every day (or as close to every day as is humanly possible). While we&#8217;ve settled on a Monday through Friday schedule, with weekend posts as the spirit moves us, we believe that still qualifies as &#8220;every day&#8221;, office worker-style.</li>
<li><strong>Point-of-View</strong>: While we cover the same ground as many other LitBloggers, we have our own perspective. A lot of writers are very protective of their ideas. It&#8217;s not the idea&#8230;it&#8217;s the execution.</li>
<li><strong>Voice</strong>: The mother likes to say that we were born talking (correction: we were born complaining) and haven&#8217;t stopped since. There are a lot of competent writers in this world; what makes writing compelling to us is voice. Readers have to connect with your voice in some manner. To us, voice is intrinsic, not something you can acquire. It is something you pull from inside and hone. Voice is also faceted: you do not have the exact same tone and style for every piece of work. There&#8217;s consistent core, yes, but also variety as the situation demands.</li>
<li><strong>Fun</strong>: Sure there are times when we look at this site as a chore. Those are rare moments and usually indicate that we need a) food, b) sleep, or c) a long vacation on a tropical island. All of which can be readily accommodated. We&#8217;re writing about a topic we love and that keeps us motivated.</li>
<li><strong>Focus</strong>: While this site sometimes wanders out to the far edges of our varied interests, mostly we stay focused on writing and publishing. You aren&#8217;t coming here to learn about the care and feeding of cats (though we can certainly help there), and we believe most people leave with the information they&#8217;re seeking. If not that, then at least they&#8217;ve had a good time. We have found that sometimes you need more than one blog/site/place to accommodate your writing needs &#8212; hence <a href="http://www.medialoper.com">Medialoper</a>, <a href="http://www.paperbackreader.net">PaperbackReader</a>, and our regular stint at <a href="http://www.romancingtheblog.com">Romancing the Blog</a>.</li>
<li><strong>Community</strong>: Writing is a solitary business. You can work with another person, sure, but ultimately the words come from your head (or fingers, depends). Blogging offers a chance for writers to connect with a community. We have made <a href="http://lbc.typepad.com/">a lot of wonderful friends</a> via this site, and we have managed to maintain relationships with <a href="http://jillmonroe.blogspot.com">friends we&#8217;ve had for </a>a <a href="http://www.susangable.com">long time</a>. This community offers support, food for thought, and even <a href="http://davidthayer.booksquare.com">help</a> when we need someone to drive the blog while we sit on that tropical island.</li>
</ol>
<ul>
<li><a href="http://www.problogger.net/archives/2006/05/23/habits-of-effective-bloggers-group-writing-project/">Habits of Highly Effective Bloggers &#8211; Group Writing Project</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://booksquare.com/highly-effective-blogging-just-like-highly-effective-writing/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>In Praise of the Serial Comma</title>
		<link>http://booksquare.com/in-praise-of-the-serial-comma/</link>
		<comments>http://booksquare.com/in-praise-of-the-serial-comma/#comments</comments>
		<pubDate>Thu, 09 Feb 2006 17:13:09 +0000</pubDate>
		<dc:creator>Booksquare</dc:creator>
				<category><![CDATA[Tools and Craft]]></category>

		<guid isPermaLink="false">http://www.booksquare.com/archives/2006/02/09/1802/</guid>
		<description><![CDATA[Far be it for us to name names (Jill), but there are people out there who don&#8217;t take the serial comma seriously (Jill). They see it, at best, as something redundant (Jill). They see its omission as a way to raise the blood pressure of perfectly nice people (BS). Some people see its absence as [...]]]></description>
			<content:encoded><![CDATA[<p>Far be it for us to name names (Jill), but there are people out there who don&#8217;t take the serial comma seriously (Jill). They see it, at best, as something redundant (Jill). They see its omission as a way to raise the blood pressure of perfectly nice people (<acronym title="Booksquare">BS</acronym>). Some people see its absence as no big deal (Jill).</p>
<p>Like we say, we&#8217;re too classy to name names. Leaving that third or fourth comma out is failed experiment in reworking the punctuation rules &#8212; sort of like new math, whatever that was.</p>
<p>Brenda Coulter takes her serial commas seriously. So seriously that she points us to a entire article about the beauty and joy that is the serial comma. In a sentence, that final comma is your best friend: it makes your meaning clear.</p>
<blockquote><p>
Many times the comma may seem unnecessary because the writer may believe there is no room for confusion in the sentence.  If we were to write, for example, â€œThe table was covered with food, gifts and flowers,â€ the meaning would be quite clear without the serial comma.  But as writers, we are usually poor judges of our own writing and may be ill suited to judge its clarity, so play it safe and use the serial comma every time.
</p></blockquote>
<ul>
<li><a href="http://brendacoulter.blogspot.com/2006/02/serial-comma-killers.html">Serial comma killers</a></li>
<li><a href="http://www.getitwriteonline.com/archive/021201.htm">Comma before &#8220;and&#8221;</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://booksquare.com/in-praise-of-the-serial-comma/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Yeah, But What&#8217;s For Dessert?</title>
		<link>http://booksquare.com/yeah-but-whats-for-dessert/</link>
		<comments>http://booksquare.com/yeah-but-whats-for-dessert/#comments</comments>
		<pubDate>Wed, 11 Jan 2006 16:58:47 +0000</pubDate>
		<dc:creator>Booksquare</dc:creator>
				<category><![CDATA[Tools and Craft]]></category>

		<guid isPermaLink="false">http://www.booksquare.com/archives/2006/01/11/1736/</guid>
		<description><![CDATA[Far too many writers have longed for the opportunity to suffer from Second Novel Syndrome, only to discover the disease is at least as debilitating as puberty. And like adulthood, SNS may be something you live with until a kind-hearted friend takes you aside and says, &#8220;Dude, seriously, people are getting creeped out by you [...]]]></description>
			<content:encoded><![CDATA[<p>Far too many writers have longed for the opportunity to suffer from Second Novel Syndrome, only to discover the disease is at least as debilitating as puberty. And like adulthood, SNS may be something you live with until a kind-hearted friend takes you aside and says, &#8220;Dude, seriously, people are getting creeped out by you sleeping with such a young book.&#8221;</p>
<blockquote><p>
The conventional view on SNS [Second Novel Syndrome] is that it is a seizure caused by a loss of innocence. Don DeLillo said a first novel comes to the writer as a gift and he doesn&#8217;t necessarily know how he wrote it. It&#8217;s the second novel that teaches him how to write. British editor Simon Prosser once said, &#8220;When you write your first book, you don&#8217;t know who you&#8217;re writing for or what awaits you. With the second book, if your work has been digested in the press, you think, &#8216;Oh, is my writing really like that?&#8217; It&#8217;s impossible to ignore the consciousness of your work being out there and people reading it and thinking things about it.&#8221;
</p></blockquote>
<p>Setting aside the notion of time-shifting in novels &#8212; your first book may not necessarily be your first book, setting up the possibility that your second book might be your first book while your third book could be your second book or your fifth &#8212; the beauty of your first published novel is that no bars have been set. You are a genius with great promise. The future is wide open, baby.</p>
<blockquote><p>
He [Jeffrey Eugenides] said: &#8220;No one is waiting for you to write your first book. No one cares if you finish it. But after your first, if it goes well, everyone seems to be waiting. You&#8217;re suddenly considered to be a professional writer, a fiction machine, but you know very well that you&#8217;re just getting going. You go from having nothing to lose to having everything to lose, and that&#8217;s what creates the panic.&#8221;
</p></blockquote>
<p>There are many ways to overcome SNS. You must choose yours. While we suggest telling the world to go bother someone else for a while, there is one surefire (if drastically permanent) method:</p>
<blockquote><p>
John Kennedy O&#8217;Toole died before A Confederacy of Dunces was published &#8211; a deft way of evading questions about how he was going to follow it up.
</p></blockquote>
<ul>
<li><a href="http://www.smh.com.au/news/books/lost-for-words/2006/01/05/1136387558132.html?page=fullpage#contentSwap1">Lost For Words: Panic after a first successful novel is perfectly natural, but what if it never passes?</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://booksquare.com/yeah-but-whats-for-dessert/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Judging Writing</title>
		<link>http://booksquare.com/judging-writing/</link>
		<comments>http://booksquare.com/judging-writing/#comments</comments>
		<pubDate>Thu, 08 Dec 2005 16:15:29 +0000</pubDate>
		<dc:creator>Booksquare</dc:creator>
				<category><![CDATA[Tools and Craft]]></category>

		<guid isPermaLink="false">http://www.booksquare.com/archives/2005/12/08/1691/</guid>
		<description><![CDATA[In an article in the New York Press, Sam Sacks takes exception with writing workshops. Where one once found creativity and free-flowing ideas, the experience now lends itself to to an inevitable sense of sameness. He cites Best New American Voices 2006 as Exhibit A of workshopping gone wrong. The question Sacks dances around is [...]]]></description>
			<content:encoded><![CDATA[<p>In an article in the <strong>New York Press</strong>, Sam Sacks takes exception with writing workshops. Where one once found creativity and free-flowing ideas, the experience now lends itself to to an inevitable sense of sameness. He cites <strong>Best New American Voices 2006</strong> as Exhibit A of workshopping gone wrong.</p>
<p>The question Sacks dances around is that of objectivity versus subjectivity. Writing is absolutely a creative endeavor. If you need to prove this, engage in the age-old exercise of listing three objects and having each member of a small group write a paragraph including those objects. Or just one object. Or ten. Each writer will take a different tack. Some may even forego the paragraph as we know it for something else. You never know.</p>
<p>For those enrolled in <acronym title="Master of Fine Arts"> MFA</acronym> programs, there is a split goal. First, of course, is the creativity. Second, is the need to apply objective rules to judge success. Sacks summarizes this aspect of the workshop process quite well:</p>
<blockquote><p>
A Story, as it progresses, is counterbalanced by a Backstory, which informs the reader what of importance happened beforehand. Both Story and Backstory must have a pronounceable Why Now, a meaningful reason that they are being toldâ€”something must be At Stake. Regarding meaning and significance, the writer should Show Not Tell through recurring Central Metaphor rather than through dry explanation of what is being felt. Furthermore, a good story has an apt and memorable Voice and conveys a strong Sense of Place.
</p></blockquote>
<p>The rules of the classroom game &#8212; and of writing contests, writers do love their contests &#8212; agree that the full breadth of Craft, as outlined above, should be present almost before the reader finishes the first paragraph. This inevitably leads some writers to mistake classroom requirements for art. It is natural that Rules will evolve:</p>
<blockquote><p>
The class I taught was assigned a course packet and there, on the first page, were more rules: Never begin a story with a character waking up in bed. Never write a scene where a character looks at himself in a mirror. Never use the word &#8220;stuff.&#8221;
</p></blockquote>
<p>In reading the <strong>New American</strong> anthology, Sacks came away uninspired. The stories, he senses, were workshopped to death.</p>
<blockquote><p>
Without ignoring the occasional flashes of verve, the stories included are so monotonous that they seem to have been written by a single person of middling talent. All but one of them are written in the first person; a similar percentage hinge upon the narrator&#8217;s difficulties with dysfunctional or deceased members of his or her family, or with ex-lovers. The tone is always confessional and saturated with self-pity. The plot and action are always negligible: one story takes place on a road trip to a presidential birthplace, another while moving apartments, another at a wedding, another while opening presents in front of the Christmas tree. None of this much matters anyway, because the things the characters do are always mundane and largely incidental to their psychological conflicts. From time to time a structural innovation appears to offer an interesting novelty, but under the packaging the same old formula is always to be found.
</p></blockquote>
<ul>
<li><a href="http://www.newyorkpress.com/18/48/books/SamSacks.cfm">The Fiction Machine: The Workshop and the hacks.</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://booksquare.com/judging-writing/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Finally</title>
		<link>http://booksquare.com/finally/</link>
		<comments>http://booksquare.com/finally/#comments</comments>
		<pubDate>Mon, 05 Dec 2005 16:23:01 +0000</pubDate>
		<dc:creator>Booksquare</dc:creator>
				<category><![CDATA[Books/Mags/Blogs]]></category>
		<category><![CDATA[Tools and Craft]]></category>

		<guid isPermaLink="false">http://www.booksquare.com/archives/2005/12/05/1687/</guid>
		<description><![CDATA[Some authors simply don&#8217;t end well. Neal Stephenson, for example. The man will write forever to avoid ending a book. Also, he seems to have a lot of extra paper or maybe stock in a paper factory. His books tend to rip-roar (in a very broad sense of the term) along before doing everything they [...]]]></description>
			<content:encoded><![CDATA[<p>Some authors simply don&#8217;t end well. Neal Stephenson, for example. The man will write forever to avoid ending a book. Also, he seems to have a lot of extra paper or maybe stock in a paper factory. His books tend to rip-roar (in a very broad sense of the term) along before doing everything they can to avoid coming to &#8220;The End&#8221;. This problem affects more authors than you&#8217;d think, which is rough because how you end a book is so very important.</p>
<blockquote><p>
The deepest rooted of last lines is the childhood one: &#8220;And they all lived happily ever after.&#8221; Unlike the first line of such stories, &#8220;Once upon a time,&#8221; it isn&#8217;t just a formula. It&#8217;s a reassurance that the result the story has achieved will remain in place even now the story-telling has finished. But more than that, it acknowledges what the story was about all along. Folk tales that end like that have, all along, been about happiness and challenges to it; the subject of the story is there in its last line.
</p></blockquote>
<p>There are many ways to end a novel, some more successful than others. You have a reminder that this is just a story &#8212; authorial intrusion as a way of returning to reality. You have endings that make no sense at all. You have sad endings. You have happy endings. You have endings that turn the entire story in another direction. But at some point, you must end. Unless you have Guinness Book of World Records aspirations. We do not judge.</p>
<p>When it comes to finishing, yours may vary. We find the best approach is this:</p>
<blockquote><p>
Certainly, that&#8217;s my habit when writing a novel. Even if, in the event, the ending changes, I always like to have a draft of a last paragraph tucked away in the notebook somewhere by the time I&#8217;m halfway through. It is rather a comfort, and an idea of something to work towards, like a distant life raft in the uncharted ocean you&#8217;re swimming towards. And I guess most decent endings had the same sort of life; treasured up through the working process, slowly polished with much more care, to tell the truth, than the more conspicuous opening gambit.
</p></blockquote>
<ul>
<li><a href="http://www.arts.telegraph.co.uk/arts/main.jhtml?xml=/arts/2005/11/20/bohensher.xml&#038;sSheet=/arts/2005/11/13/bomain.html"> The end. At last.</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://booksquare.com/finally/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Building An Intimate Relationship: Writing Partnerships</title>
		<link>http://booksquare.com/building-an-intimate-relationship-writing-partnerships/</link>
		<comments>http://booksquare.com/building-an-intimate-relationship-writing-partnerships/#comments</comments>
		<pubDate>Mon, 14 Nov 2005 16:27:28 +0000</pubDate>
		<dc:creator>Booksquare</dc:creator>
				<category><![CDATA[Tools and Craft]]></category>

		<guid isPermaLink="false">http://www.booksquare.com/archives/2005/11/14/1659/</guid>
		<description><![CDATA[In our long career, the only writing partner we&#8217;ve had is the husband. As far as collaborative processes go, it worked surprisingly well. Unlike traditional fiction partnerships, we wrote in a shared editing environment. This, of course, meant the poor man had to wait until we were satisfied with his commas and apostrophes before we [...]]]></description>
			<content:encoded><![CDATA[<p>In our long career, the only writing partner we&#8217;ve had is the husband. As far as collaborative processes go, it worked surprisingly well. Unlike traditional fiction partnerships, we wrote in a shared editing environment. This, of course, meant the poor man had to wait until we were satisfied with his commas and apostrophes before we started the next section.</p>
<p><strong>MediaBistro</strong> takes a look at the process of writing with a partner. Though we know you&#8217;re going to pop right over and read the whole thing, we feel compelled to summarize: communication. Oh sure, you&#8217;re always right and have never made a wrong decision. This does not allow you to make all the choices when it comes to a joint work.</p>
<blockquote><p>
To future authorial teams, [Lisa] Papademetriou suggests: &#8220;Go Zen. It&#8217;s really important to listen to what the other person is saying, rather than getting defensive. When Chris and I talked through our ideas, we almost always came out with something better than what either one of us had come up with on our own. Also, it&#8217;s important to find someone who works in the same way that you do. If you&#8217;re a deadline person, and your writing partner is more hang loose, you&#8217;re going to have some tension.&#8221;
</p></blockquote>
<ul>
<li><a href="http://www.mediabistro.com/articles/cache/a6170.asp?c=mbennf">It Takes Two To Make A Book Go Right: Are two authors better than one?</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://booksquare.com/building-an-intimate-relationship-writing-partnerships/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Interesting, But Off-Base</title>
		<link>http://booksquare.com/interesting-but-off-base/</link>
		<comments>http://booksquare.com/interesting-but-off-base/#comments</comments>
		<pubDate>Thu, 15 Sep 2005 15:26:13 +0000</pubDate>
		<dc:creator>Booksquare</dc:creator>
				<category><![CDATA[Tools and Craft]]></category>

		<guid isPermaLink="false">http://www.booksquare.com/archives/2005/09/15/1580/</guid>
		<description><![CDATA[We like radical notions (especially those that start with, &#8220;Maybe we should go out for Chinese food tonight&#8221;), but prefer solid plans (&#8220;Let&#8217;s go out for Chinese food tonight&#8221;). A plan to deal with the morass that is book returns certainly would catch our attention, but as we read one publisher&#8217;s call to arms, we [...]]]></description>
			<content:encoded><![CDATA[<p>We like radical notions (especially those that start with, &#8220;Maybe we should go out for Chinese food tonight&#8221;), but prefer solid plans (&#8220;Let&#8217;s go out for Chinese food tonight&#8221;). A plan to deal with the morass that is book returns certainly would catch our attention, but as we read one publisher&#8217;s call to arms, we were struck by the missing details.</p>
<p>Angela Hoy, who runs the <strong>Writers Weekly</strong> newsletter and owns <strong>Booklocker</strong>, a print-on-demand publisher, is suggesting that all all books be non-returnable. Her logic is that print-on-demand technology and smarter ordering would reduce the accounting nightmare that is returns.</p>
<blockquote><p>Accepting returns ultimately hurts the author and the publisher and costs the bookstores very little (except when they agree to pay shipping or a small percentage of the loss as a penalty). Grocery stores aren&#8217;t allowed to return unsold food to manufacturers and your local department store isn&#8217;t allowed to return unsold clothes to the factory. So, why should bookstores be allowed to over-order and then return items while expecting the publisher or self-published author to bear the expense of their poor judgment? And think of all the trees that were wasted on those books that will never sell! </p></blockquote>
<p><span id="more-1580"></span></p>
<p>Now we&#8217;re very much in favor of trees, but also know there&#8217;s a little thing called human nature. Books cannot be equated with groceries or clothing*. And customers certainly can return these items, resulting in credit to the stores. Though we are not familiar with the ins and outs of every business, we do know it is possible to negotiate returns on unsold items (the store to the manufacturer). This is, of course, not factoring the wild and woolly returns policies related to music and motion picture products. Whoo hoo!</p>
<p>The fact remains that print-on-demand is not truly print-on-demand. If it were, then, sure, a bookstore could stock a large number of well-thumbed products, producing a fresh copy while the customer&#8217;s credit card is processed. Unlike clothing, you cannot try an item on, twisting and turning and cursing the fact that dressing room mirrors do not reflect a reality found on this planet.</p>
<p>Books can be tried on &#8212; we all do it &#8212; but the equivalent notion would be reading a good portion of the book (must see  how it looks, front and back, not to mention the side view). Some might put the book, all stretched seams and hidden stains from dirty thumbs, back on the shelf. Others might take the book home and model it for the family before deciding it just doesn&#8217;t fit.</p>
<p>Our analogy, much to your relief, is going to break down now. Clothing can be marked-down until someone says, &#8220;Hey, that pink blouse with rust stripes is a good deal.&#8221; Books don&#8217;t undergo the same process. And, needless to say, once books are remaindered, authors suffer.</p>
<p>Hoy&#8217;s main argument seems mainly centered on the fact that bookstores get suckered into making unwise purchases &#8212; purchases that result in the little risk borne by the store and lots of risk borne by the publisher/author. She cites this example:</p>
<blockquote><p>We heard one story about an author (not a booklocker.com author!) who convinced a huge, well-known discount store (you probably have one in your neighborhood) to buy 300,000 copies of his book. He was apparently related to someone in the higher ranks at that store. The publisher naively agreed to accept returns and processed the order. Well, when dealing with 300,000 copies of an unknown author&#8217;s books, you can probably guess what happened. Almost all of the books were eventually returnedâ€¦at the expense of the publisher. </p></blockquote>
<p>While this story has the quality of an urban legend, it also doesn&#8217;t represent life as we know it. Very rarely are well-known discount stores going to put out for 300,000 copies of a book on a whim. A business-savvy publisher isn&#8217;t going to put their financial future at risk in such a manner either. We do not make it a habit to comment upon the intelligence of our fellow humans (much), but someone wasn&#8217;t using both sides of the brain here.</p>
<p>Hoy then notes about the above scenario (and this is where she lost us completely):</p>
<blockquote><p>By the time the books were returned, the publisher may have already paid royalties to the author. When something like this happens, what do you think a publisher&#8217;s chances are of recovering that lost money? Zero.</p></blockquote>
<p>Again, a business-savvy publisher has factored risk into the equation, in this case by holding substantial reserves against returns. By substantial, we&#8217;re thinking percentages that start with a 9 and end with a 9. Contracts also, in that icky fine print, often provide mechanisms for recovering overpayments, should they happen. It doesn&#8217;t happen often, but it&#8217;s a possibility. The only real way we can see that the publisher would be out cash (other than printing costs) is if they&#8217;d been dumb enough to give the author a non-refundable advance.</p>
<p>Returns are a real problem in the publishing industry. Too many items are produced, stores are convinced to stock large quantities (book buying is largely a matter of gut, and it&#8217;s not always easy to gauge customer reaction), reserves are held far longer than is reasonable, and the window for returning product is far too open. The print-on-demand idea works better for non-impulse purchases &#8212; and how many books are impulse purchases? &#8212; and with online retailers whose customers don&#8217;t expect instant gratification.</p>
<p>Going with the print-on-demand model doesn&#8217;t address the real problems that accompany liberal returns policies and practices. Returns shouldn&#8217;t be abolished &#8212; they should be reformed. Seriously reformed.</p>
<p>* &#8211; Okay, we see your point, but there will come a moment when starvation is a real option.</p>
<ul>
<li><a href="http://www.writersweekly.com/the_latest_from_angelahoycom/002947_09142005.html">Why All Books Should Be Non-Returnable</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://booksquare.com/interesting-but-off-base/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>The Secret Life of Apostrophes</title>
		<link>http://booksquare.com/the-secret-life-of-apostrophes/</link>
		<comments>http://booksquare.com/the-secret-life-of-apostrophes/#comments</comments>
		<pubDate>Mon, 29 Aug 2005 14:48:07 +0000</pubDate>
		<dc:creator>Booksquare</dc:creator>
				<category><![CDATA[Tools and Craft]]></category>

		<guid isPermaLink="false">http://www.booksquare.com/archives/2005/08/29/1541/</guid>
		<description><![CDATA[Today&#8217;s first post comes courtesy of the husband. While in some households, his accompanying statement would be taken as a joke, we never jump to conclusions: &#8220;How come nobody told me about the rule where you&#8217;re supposed to put an apostrophe after words that end in vowels? That could come in handy.&#8221; Bob&#8217;s Quick Guide [...]]]></description>
			<content:encoded><![CDATA[<p>Today&#8217;s first post comes courtesy of the husband. While in some households, his accompanying statement would be taken as a joke, we never jump to conclusions: &#8220;How come nobody told me about the rule where you&#8217;re supposed to put an apostrophe after words that end in vowels? That could come in handy.&#8221;</p>
<ul>
<li><a href="http://www.angryflower.com/bobsqu.gif">Bob&#8217;s Quick Guide to the Apostrophe, You Idiots</a> (Poster-sized version helpfully available at <a href="http://www.angryflower.com/">The Official Bob the Angry Flower Web Site</a>)</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://booksquare.com/the-secret-life-of-apostrophes/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Helpful Tips: How To Guarantee Rejection</title>
		<link>http://booksquare.com/helpful-tips-how-to-guarantee-rejection/</link>
		<comments>http://booksquare.com/helpful-tips-how-to-guarantee-rejection/#comments</comments>
		<pubDate>Fri, 26 Aug 2005 00:31:38 +0000</pubDate>
		<dc:creator>Booksquare</dc:creator>
				<category><![CDATA[Agents]]></category>
		<category><![CDATA[Tools and Craft]]></category>

		<guid isPermaLink="false">http://www.booksquare.com/archives/2005/08/25/1537/</guid>
		<description><![CDATA[Though some authors seem to know instinctively the best, most expeditious, ways to get rejected, others require a primer. For those souls, Deidre Knight and Justin Knight of The Knight Agency have put together a helpful list of things to do to ensure immediate rejection: But weâ€™ll confine ourselves to encouraging writers with ways to [...]]]></description>
			<content:encoded><![CDATA[<p>Though some authors seem to know instinctively the best, most expeditious, ways to get rejected, others require a primer. For those souls, Deidre Knight and Justin Knight of The Knight Agency have put together a helpful list of things to do to ensure immediate rejection:</p>
<blockquote><p>But weâ€™ll confine ourselves to encouraging writers with ways to get themselves turned down by agents or publishers, and trust that youâ€™ll understand how to apply these lessons in a broader context. Nor are we going to insult anybodyâ€™s intelligence by telling you about the really basic, simple ways that a writer can ensure that no one will read her query letter, let alone her manuscript. Weâ€™re sure you already know about obvious things like using unusual fonts and paper, though we will point out that a really fuzzy, beat-up printer for your letter and manuscript is certainly a plus. Extra points if you could dig up a dot-matrix, though of course the real prize goes to those who handwrite their letters. That takes a special person.</p></blockquote>
<ul>
<li><a href="http://www.romancingtheblog.com/blog/?p=341">Screwtape Takes the Comm</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://booksquare.com/helpful-tips-how-to-guarantee-rejection/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

