Category Archives: Grammar/Punctuation

Why Indie Book Quality is Important

I read this today and totally agree. It’s sort of a big deal.

2 Comments

Filed under Grammar/Punctuation, Indie Publishing, Writing Market

Writing ebooks has changed a lot since the 80’s

Ahh…I remember it so clearly, back in the 80’s…

I’d just gotten home from school, sat down on my Commodore 64 and brought up Amazon (formerly called “river-in-south-america.com”) to check my sales report: 20 downloads!  Where did they come from?  Back then, we didn’t have any cool sales statistics like KDP does today. You know, with that tiny little map and lightly shaded areas indicating that humans with ebooks had at one time downloaded something.  And Google wasn’t Google back then, it was simply called “a-whole-bunch.com.”  Still, it was all we had, and we were happy to have it.

So anyway, I pulled up A-Whole-Bunch and clicked around with my joystick and guess what? Turns out Michael Jackson, fresh from his Victory Tour, had been Tweeting (Twatting) and Digging (called Dig-Dugging) and Tumbling-Upon (Nudging-Along) all day long, telling people it was awful and not to buy it!  Apparently he’d downloaded a very early, incredibly preliminary version of Kick, which I’d uploaded before it was ready because I heard you could make millions of dollars (hundreds, in 80’s money).  Back then, the working title was “Bop.”  At the time, I  thought it was best not to respond to critics so I ignored Michael Jackson’s attacks.

Maybe a day later, a strange man in a suit showed up at my house and demanded I come out.

“What do you want?” I said.

“I demand that you take “Bop” off of river-in-south-america.com immediately! ” he said.

“And why would I do that?”

“Copyright infringement, you pathetic fool!”

“Who’s copyright am I infringing upon?” I said.

The man laughed mysteriously, adroitly, and emphatically all at the same time, then switched to a maniacal laugh that set my teeth on the edge of my seat, causing my eyes to drop in mesmerizing, ecstatic, anticipatory wonder at him.

“Funny you should ask,” he said. Then he spun around three times, whipped off his glasses and coat, still spinning, and a wind picked up outside and suddenly he was Michael Jackson, hands spread out to his side, yelling, “Hee heeeeeee!

“Wow,” I said.  “You’re Michael Jackson!”

“Shamon,” he said.

“So how am I copyright infringing you?”

“I’m the King of Pop…the name of your book is Bop–it’s too similar.”

“What if I changed it to ‘Beat?'” I said.

“Nice try–my biggest hit was Beat It.”

I thought about it.

“How about Kick?”

He did that kicky move thing he always does and I rolled my eyes.  “Ok, yeah, you got that too.”

“Hey,” he said.  “Why don’t you call it–Hee heeee!

I blinked at him.  “But I thought that was one of your little catchphrase things?”

“No, not ‘Hee heeeee,’ I meant to say–Hee heeeeeee!

Now I was really confused. He’d just said he didn’t mean “Hee heeeee,” and then he’d suggested I use “Hee heeeee.”

“But you just said…”

Hee heeeeee!” he said again.  “Can’t Hee heeeeee! say anything Hee heeeeeeeee! else because Hee heeeeeeeee!”

And suddenly it was clear to me what was going on.

“Come on in, Mike,” I said.

I sat him down, got him a Coke (he flinched when I offered Pepsi), put on his Thriller video, we watched it, it scared him, Heeeeee-cups cured, he said I could call the book “Kick,” and I rushed this blog post to it’s happy/sad/laughed/cried/amazing yet subtle conclusion, with very little editing, and hit “Publish.”

Leave a comment

Filed under Funny, Grammar/Punctuation

Smartquotes, Apostrophes, and which way to turn

So, I’m working on polishing up a manuscript, and guess what? My apostrophes were pointing the wrong way for certain kinds of contractions: Shoot ’em, ‘nother one for the road, ‘fraidy pants.

Think of apostrophes as the number 9

Think of a left single quote as a letter 6

So, words that start with an apostrophe should start with the letter 9.

Leave a comment

Filed under Grammar/Punctuation

Find unbalanced smart quotes in HTML using Perl

So I’m brushing up an HTML document so I can publish it on the Kindle and I’ve discovered lots of unbalanced smart quotes. Smart quotes are double quotes that face to the right or the left, rather than just straight up and down. In HTML, they are rendered as “ldquo” and “rdquo” with an ampersand in front of each and a trailing semi-colon. I wrote a little script to make sure that for every left side I had a right side, and print out the lines in which they do not match.

Here you go:

#!/usr/bin/perl

open(FILE,"./file.html") or die "Can't open file.html: $!\n";

while(<FILE>) {
   chomp();
   $line = "$_";

   $l = "ldquo";
   $r = "rdquo";   
   $lc = 0;
   $rc = 0;   

   $lc = () = $line =~ /$l/g;
   $rc = () = $line =~ /$r/g;

   print "Lc = $lc  Rc = $rc\n";
   if ($lc != $rc) {
      print "\n$line\n";
   }
}
close(FILE);

3 Comments

Filed under Grammar/Punctuation, Tools for Writers

Added another link to my Editing Blogs collection

Terribly Write

Leave a comment

Filed under Grammar/Punctuation

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

Looking for some good proofreading checklists

I found one with good tips on using search/replace:

http://www.fictionfactor.com/guests/agentsubmit.html

Here’s a list of homophones:

http://copywriterscrucible.wordpress.com/2009/09/01/41-commonly-misused-english-words/

From my blogroll, here’s an amazing list of crap that can be snipped from your writing.

http://theeditorsblog.net/2013/01/22/cut-the-flab-make-every-word-count/

She has a lot to say about numbers, too:

http://theeditorsblog.net/2013/01/13/numbers-in-fiction/

I’m working on a style sheet of my own, tailored to the mistakes I make.  When it’s done, I’ll post it.

Leave a comment

Filed under Grammar/Punctuation