Feeds:
Posts
Comments

Posts Tagged ‘novel writing’

Kurt R.A. Giambastiani

This edit only addresses the items highlighted in the original, and while I feel it is an improved version, there are still other problems–some of those “macro” level problems of the type I mentioned way back when I started this series. Problems like, say what? a new character halfway through a short story? Problems like, it’s just a bit dry and non-descript in places; too bland and banal. Problems like, it’s got a little too much sci-fi gimcrackery around the edges.

I’ll address these issues in a final rewrite, but for now, feel free to read and compare this to the original version.

(more…)

Read Full Post »

Kurt R.A. Giambastiani

Here is the original version of “Cast in Stone,” a trunk story I wrote about 20 years ago (Good lord, has it been that long?) If you missed the history of this piece, go read the Preamble to this edit-fest.

And to remind you of the color codes for each error type:

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

(more…)

Read Full Post »

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?

 

Read Full Post »

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.” (more…)

Read Full Post »

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

Read Full Post »

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.

(more…)

Read Full Post »

Stack of BooksThus far, I’ve covered the most offensive types of errors I’ve seen in fiction on the web, and now I’ll get down to things that are merely bad or that are just annoying. But just because an error doesn’t stand up and slap you in the face, it doesn’t mean an editor will let you get away with it. She shouldn’t and she won’t.

From here on, though, the problem with these errors is that–more so than the topics of previous posts–frequently they aren’t errors at all. Don’t you just hate that? As we move on, keep in mind that all of the word usages I list here–all of them–often have a legitimate place in prose. There will be times that you specifically want what they provide; the key is to understand the danger they pose, and use them knowingly.

And so, onward to “wiggle words.”

(more…)

Read Full Post »

« Newer Posts - Older Posts »