Tag Archives: Editing

Added another link to my Editing Blogs collection

Terribly Write

Leave a comment

Filed under Grammar/Punctuation

Great book I found on bad writing

In my experience, books on writing haven’t been that useful to me. The ones I’ve read make a big deal about stories having a beginning, middle and end. Or they tell you things like “write every day” or “write what you know” or “use active voice.” Timeless advice found in any book on writing, but nothing new. Stephen King’s book was good, but mostly because I was interested in Stephen King. He had a few good tips in there, especially on editing out things like “that” and what not.

Yesterday, I stumbled upon a great book recommendation at my favorite editor’s blog (the Editor’s Blog). It’s called, “How not to write a novel.” In it, the authors go over all the things they hate to see in submitted works by the unpublished masses (like me). Not only don’t they pull punches, but they actively ridicule anyone who makes these mistakes (without naming names). It’s actually pretty funny. Just this morning, I got caught off guard by the observation that some writers dredge up vocabulary from “the darkest regions of the dictionary.” This caused me to snort, which caused my hand to jiggle, sending coffee dribbles spilling onto my shirt.

I’ve read about 2/3 since yesterday and I have to say: I’ve done many of the things they’re talking about, at one time or another. Recently, I committed the crime of writing what they call a “benign tumor.” A benign tumor, according to the authors, is when you write a scene that extends the book, but if you cut it out, absolutely nothing happens to the story. Imagine the good guy going to kill the villain and taking 5 pages to talk about a detour he was forced to take through a nice part of town, musing how after he kills the villain maybe he’d move there. Benign tumor.

Enjoy.

2 Comments

Filed under Publisher's Advice, Submission Tips, Writing in general

Preliminary homophone finder written in perl

I wrote this little perl script to find homophones in text documents, so if you save your word doc as a text file, in theory you can find all the homophones with it.  I’m using 943 homophones and running the first part of a Winston Churchill speech through it 🙂

To run the script, you’d need to know a little perl and how to use it. So for most people, this isn’t particularly user-friendly.  It’s more for fun, as well as a proof of concept on a hypothetical tool writers could use to keep silly mistakes out of their writing.  While the script runs, you hit ‘enter’ occasionally to go to the next line with one or more homophones in it.

The script needs:

  • words.txt – a list of homophones one after the other  (it makes sense to edit out of this any words you’d never mess up, for example, “I” vs. “eye” or “were” vs. “whirr”)
  • ms.txt –  your manuscript saved as a text file

First, the code:

#!/usr/bin/perl

open(WORDS,"words.txt") or die "Can't open words.txt: $!\n";
@words = <WORDS> ;
close(WORDS);

open(MS,"ms.txt") or die "Can't open ms.txt: $!\n";

while(<MS>) {
   chomp();
   $aline = $_;
   lc($aline);
   $match = 0;
   foreach $i (@words) {
        chomp($i);
      if ($aline=~/\s+$i\s+/g) {
        $match = 1;
        $uppercase = uc($i);
         $aline=~s/\s+$i\s+/ \*$uppercase\* /g;
      }
   }

   if ($match == 1) {
      print "$aline\n";
      print "[ hit enter to continue ]\n";
      $ans= <> ;
   }
}
close(MS);

Here’s what happens to the first part of this famous speech:

I spoke the other day of the colossal military disaster *WHICH* occurred when the French High Command failed *TO* withdraw the northern Armies from Belgium at the moment when they *KNEW* that the French front was decisively broken at Sedan and on the Meuse. This delay entailed the loss of fifteen *OR* sixteen French divisions and *THREW* out of action *FOR* the critical period the whole of the British Expeditionary Force. Our Army and 120,000 French troops *WERE* indeed rescued *BY* the British Navy from Dunkirk *BUT* only with the loss of *THEIR* cannon, vehicles and modern equipment. This loss inevitably took *SOME* weeks *TO* repair, and *IN* the first *TWO* of those weeks the battle *IN* France has *BEEN* lost. When *WE* consider the heroic resistance *MADE* *BY* the French Army against heavy odds *IN* this battle, the enormous losses inflicted upon the enemy and the evident exhaustion of the enemy, it may well *BE* the thought that these 25 divisions of the best-trained and best-equipped troops *MIGHT* have turned the scale. However, General Weygand had *TO* fight without them. Only three British divisions *OR* *THEIR* equivalent *WERE* able *TO* stand *IN* the line with *THEIR* French comrades. They have suffered severely, *BUT* they have *FOUGHT* well. We *SENT* every man *WE* could *TO* France as fast as *WE* could re-equip and transport *THEIR* formations.
[ hit enter to continue ]

I am *NOT* reciting these facts *FOR* the purpose of recrimination. That *I* judge *TO* *BE* utterly futile and even harmful. We cannot afford it. *I* recite them *IN* order *TO* explain why it was *WE* did *NOT* have, as *WE* could have had, between twelve and fourteen British divisions fighting *IN* the line *IN* this *GREAT* battle instead of only three. Now *I* put *ALL* this aside. *I* put it on the shelf, from *WHICH* the historians, when they have time, will select *THEIR* documents *TO* tell *THEIR* stories. We have *TO* think of the future and *NOT* of the past. This also applies *IN* a small *WAY* *TO* *OUR* own affairs at home. There are many who *WOULD* hold an inquest *IN* the House of Commons on the conduct of the Governments-and of Parliaments, *FOR* they are *IN* it, too-during the years *WHICH* *LED* up *TO* this catastrophe. They seek *TO* *INDICT* those who *WERE* responsible *FOR* the guidance of *OUR* affairs. This also *WOULD* *BE* a foolish and pernicious process. There are *TOO* many *IN* it. Let each man search his conscience and search his speeches. *I* frequently search mine.
[ hit enter to continue ]

Leave a comment

Filed under Grammar/Punctuation, Tools for Writers

Fiction editing tip – leverage your Kindle Fire

I just finished my second official edit of my novel and I thought I’d pass along the experience.  We’ve all heard the various ways you should edit your book:

1) wait a month and read it fresh.

2) change the font and read it fresh.

3) Read it out loud and hear it fresh.

The common theme?  Reading it fresh, or differently than you are used to.  So here’s a new one:

4) publish it to your Kindle Fire and read it fresh!

If you go to your amazon account and click “manage my kindle”, you’ll see a section for personal documents.  Somewhere in the settings you can specify what email addresses can send documents to your amazon account.  There are better resources on how to do the exact steps, but in a nutshell you:

1) save-as your document to “stripped html” or (in office 2011 for mac) just html.

2) send it to <emailaddress@kindle.com>

3) publish to kindle

Once it arrives on your kindle you can read it as an ebook.  The best part is: while you are reading it, you can add notes DIRECTLY ON YOUR KINDLE.  You can highlight bad sections with “the the” or “your” when it should be “you’re”, etc. etc.  After re-reading your book and editing it up, you can easily go through it note by note and put it all back in your document.

That’s what I did this weekend.

Quick notes:

1) publishing to your kindle costs like 2 bucks (or something, very cheap)

2) you can also do this on your other kindle devices (it’s just easier on the Kindle Fire).

3) I’m guessing you can do it on other ebook readers, but that’s just a big fat guess, now ain’t it?

4 Comments

Filed under Tools for Writers