Feeds:
Posts
Comments

Kurt R.A. GiambastianiMy story, “Cast in Stone,” was written in the early ’90s, and is probably the third or fourth story I ever wrote. I wrote it for a themed anthology about “deaders,” brain-dead humans who were animated via software to become servants and workers. The anthology accepted the story, but the money fell through and it was never published.

I then submitted the story to OMNI, back when OMNI was (a) a real magazine and (b) still publishing fiction under the incomparable editorial hand of Ellen Datlow. One of Ms. Datlow’s assistant editors, Robert K.J. Killheffer, read the story, and liked it enough to take the extraordinary step of leading me through several rewrites. (I have to say, after boiler-plate/check-list rejection letters, it was a thrill to get a letter for a rewrite!) He provided me with guidance each time through, suggesting changes in everything from the title (original title: “Statuesque Revisions”…ick) to structure and style.

We went through about four iterations, if memory serves, with Rob sending me up two pages or so of typewritten comments, and me improving the story each time. In the end, the story was still rejected, but this all tells you how much work went into the version I present to you here.

And even with all that editing, all that mentorship, it still has so many problems that I wince to read parts of it.

So, what I will be presenting here is “Cast in Stone,” in its original, post-OMNI form. I have changed not a word, but I have highlighted the major errors and issues of the type I’ve talked about in this series of posts. I’ve given each a color code as follows:

  • Telling, not showing
  • Clunky phrasing/naming names
  • Exposition
  • Bad metaphors/similes/adjectives
  • Wiggle words
  • Echoes

Then, I’ll present a rewritten version where I’ll fix them and (possibly) some of the larger, structural problems the story has.

Ready?

 

Stack of BooksThis is the last specific topic I’m going to post in this series on common mistakes that plague new/untrained writers. But, I’ve decided that the final post is gong to be an experiment. I’m going to take an old trunk story and post it here, warts and all, highlighting the errors I’ve been complaining about here. Then I’m going to edit it, rewriting it to see how much better it might be. Then, you can be the judge of whether or not my advice given here is of any value.

But that’s later. For today, I’ll lay out my last gripes about unpolished writing: repetition, assonance, and alliteration. Like last time, these are hard to find in editing, and not something I can spot by scanning a work. But I find that if I keep my “ear” open as I read, I’ll hear them.

By “repetition,” I mean the re-use of a specific word in close proximity. Naturally, I have to re-use words, but most words don’t cause a problem because they’re so common. We’re accustomed to their being repeated over and over within a paragraph or even within a sentence. It’s the unusual words that, when repeated, cause a problem, and the more unusual the word, the more it sticks in the reader’s mind. Editors I’ve worked with call this an “echo,” and I’ve had “echoes” called out chapters away from each other.

Example: If I use the word “diaphanous” in Chapter 1, and then again in Chapter 2, you’ll remember it. You’ll probably remember it if I use it in Chapter 10. If I use the words “bifurcate” or “spavined” more than once in the entire book, you’ll remember it. But even common words, when used in close juxtaposition, can create a problem of “echoes.” Continue Reading »

Stack of BooksA follow-up to my earlier post about reformatting print-ready files for e-book readers…

In case these two points didn’t register in that post, here they are again:

  • Take Your Time…
  • Check Your Work…

I spent many hours over the past couple of days struggling with the files for FC Books II-V. I took my own advice (see above) and carefully and deliberately went through each reformation step, file by file. Then I uploaded the reformatted files and downloaded the KDP-converted files (in MOBI format) Then I previewed each MOBI file, using the Kindle Previewer, taking care to preview each file in each of the possible devices, from Kindle DX to iPad.

What I found was that while everything was fine on Kindle hardware, something was throwing off all the formatting when the MOBI file was ported to the iOS hardware. On iPads and iPhones, all my careful font styles were dropped and the whole shebang popped up in Courier New monospaced font. Ick.

Luckily, I had one file that was working on iOS (FC:I) so it was just a matter of comparing that file to the other files and trying to find the one thing that was causing the KDP conversion software to have a hissy-fit. I don’t know exactly what it was or exactly why, and I won’t bore you with details too tedious to be suffered. Suffice it to say that I was able to create files that work on all devices.

However, I still have not released FC:II-V into the e-book wild. I’m taking even more time, and will upload them all to my Kindle account, so I can see them on a Kindle, an iPad, and an iPhone for myself.

But it brings home my admonitions: Take Your Time and always Check Your Work.

That is all.

k

Winter’s Edge

Misty MorningOur drive west to the ocean is quiet, the road hissing beneath our tires, the drizzle hiding the greater world around us. It is just us, the dashed stripe down the pavement, and the last vestiges of winter along the highway’s edge.

Washington is the Evergreen State, and it is always, ever, green; winter or summer, rain or sunshine, something is always green. In this season, it is the cedars, pines, firs, and spruce. They covered the hillsides and the slopes between us and the limits of the grey-misted world: tall, shaggy, dark green sentinels ranked in thick forest ranks, or short, stripling, pale green youngsters rising from the steaming refuse of clear-cut acreage. But not everything is green.

Continue Reading »

The Reformation

As promised, I’ve begun to release the Fallen Cloud Saga in e-book format. And, just as I decided on CreateSpace to be my “publisher,” I’ve decided on the Kindle for my e-book format. The reasons are basically the same as before: ease of use, platform reach of the product, and essential friendliness of the agreement. Amazon’s Kindle Direct Publishing (KDP) website is easy and reliable.

But I just can’t take my print-ready files and use them to build an e-book. Well, okay, I can, but I shouldn’t. Print-ready files are just that: print-ready, not e-book ready. To work best, e-books need to be reformatted; not much, just a little more here, a little less there, but they need it and it’s important to the reading experience.

Fortunately for those of us who are heading into the world of self-publishing, Amazon has given us a primer.

Continue Reading »

Kurt R.A. GiambastianiThis week, I’m on “stay-cation,” which means we get to laze around the house for several days, go on outings, catch up on our reading, and watch a lot of movies. We started the week off by bingeing on the first season of a new series distributed by Netflix…yes, Netflix; they’re in the movie-making biz, now.

“House of Cards” stars Kevin Spacey and Robin Wright in the two lead roles, and when we started off, I was immediately hit with a sense of déjà vu. Something was familiar, but I couldn’t place it. But then a reporter speculated about the meaning behind a recent shift in power. When Frank Underwood (Spacey) drawled the answer, “You might very well think that; I, however, could not possibly comment,” it all clicked.

Continue Reading »

Warning, Warning

Whew. That was close.

To all dear friends and readers, this is a reminder.

BACK UP YOUR WORK!

Also, Windows users, make a system repair disk.

I spent the morning recovering from a Windows Non-Start…not the Blue Screen of Death (thankfully) but the Blue Screen of Heavenly Light that Windows goes to when one of its critical start-up files has been corrupted.

Corrupted how? Not a virus, not malware, not a hacker…my anti-virus/firewall software is strong and current. So who knows? Random cosmic rays? Dust particles? Static discharge from the cat rubbing up against the tower? Perhaps. But it doesn’t matter.

I’d become complacent in my backup routine, and hadn’t done a full backup for a while. Had it been bad, I might have lost tax information, and all my Kindle e-book work-in-progress. Not tragic, but a serious patootie-pain.

So, no post for today, other than this caution: Practice Defensive Computing! Back up your work!

Best,

k