View Single Post
Old 03-31-2016, 06:16 PM   #453
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,745
Karma: 30237526
Join Date: Mar 2012
Location: Sydney Australia
Device: none
On quite a lot of books we get the following pattern repeated dozens and dozens of times, maybe hundreds:

Dialogue-tag1, "Spoken sentence-1. Spoken sentence-2. Narrative-sentence. Dialogue-tag2, "Spoken sentence-3."

To fix the error 'all' one needs to to is to insert a closing quote at the end of Spoken sentence-2.

In addition, quite often Spoken sentence-3 is a response from a different speaker to Spoken sentence-1 & 2, which usually means a newline must be inserted -- either before Narrative-Sentence or before Dialogue-tag2 - or maybe both.

We have another way of tackling these books. A repetitive search for [“"]*["”] will highlight text between an opening and closing quote; of course, it highlights all dialogue, both properly and improperly formed. But where there are lots of errors of this sort its actually faster to use it, because it can be driven from entirely from the keyboard.

Whereas within the dialogue checker, after pressing/clicking 'P', I have to use the mouse to put the insertion point within the highlighted text, then use the keyboard to correct the text, and then the mouse again to get back to the procedure.

Ideally I'd prefer not have to use the mouse to position the insertion point. and return to the procedure - i.e. a mouse-free process. Maybe that's not possible within the context of a Word addin. If that's true then even if this suggestion were implemented I wouldn't be satisfied, so I'm questioning its merit -- seemed a good idea at the time

I fell into the trap of specifying a solution rather than stating requirements

BR
BetterRed is offline   Reply With Quote