Analysing Sentences
Using code to help with editing
As I first mentioned in The Editor’s Assistant, I’ve been writing macros for MS Word for many years.
A little more than ten years after I wrote the macro mentioned in that post, I encountered the concept of “Glue Index” (and therefore “sticky sentences”). Also, around the same time, I discovered the existence of guidelines for balanced sentence length to aid comprehension and “comfortable” reading.
While this varies by audience and the nature of the writing, and – with fiction – from genre to genre, as a general principle it’s wise to keep average sentence length to between 20 and 25 words. Variety is good too. You don’t want large collections of short sentences, which can make the read feel “choppy”. It’s good for action passages, to give a sense of urgency/danger/etc, but you can’t keep that up for too long. It’s emotionally exhausting. Similarly long passages of overlong sentences can tire a reader out, or even worse annoy them. Hence “average.”
If you’ve read that previous post it’ll come as no surprise that I coded this up.

My AnalyseSentences macro runs through a document counting the words in each sentence and adding them to an Excel table, after which it’s easy to create the kind of graph seen above. In this case it’s a run against my latest manuscript – A Flame In The North – which currently sits at 107,000 words. The run took eleven minutes.
From that visual it’s easy to see that the average sentence length is somewhere around 10-15 words*, which is great, but you can also see quite a few outliers. Several between 50-60 words and one behemoth of over 70 words. This is another drafting tic. I will have let my mind run riot while writing, just basically recording a kind of stream of consciousness. It clearly needs some serious editing!
But help is at hand, because as well as writing these sentence lengths into Excel, AnalyseSentences highlights the long sentences it finds, so it’s easy to scan through the document, find them, and chop them up a bit.

I use red for long sentences – anything over 25 words – and cycle through four different shades of red because often consecutive sentences have the same problem and this method makes it easier to differentiate them. I’ll read each one and decide whether it can stay as it is (for example if it’s one long sentence in a group of shorter ones), or needs to be split up. Run-on sentences are particularly easy to handle in this context – they are almost always stronger when split into two parts.
I also flag “outlier” sentences (longer than 50 words) in bright red because I can’t allow them to persist into the published work. They have to be split up or rewritten.
Sticky Sentences
Since this macro is handling sentences, I also calculate the Glue Index (you can Google it) of each one and highlight any that have a GI of 45% or higher in grey. Once again I cycle through four shades of gray (not 50!) for clarity. With short sentences (5-10 words) the GI is often unrepresentative. They’re not usually a problem. But many longer ones with high GI can be strengthened and I do switch some of them up during the read through.
Poor Style
Finally, four shades of green highlight two style issues: starting a sentence with a pronoun, or with a participle (I simply check for any word ending -ing). These aren’t hard-and-fast grammatical rules. Years ago some grammarians frowned on pronoun starts, but it’s very common in fiction and no longer considered a problem. But like so many things, it can be overdone, and this is especially true when drafting. Too much “he did this, she did that, they did the other” becomes repetitive and boring. So I flag them up for consideration, while at the same time being conscious that many (most) of them won’t need changing.
It’s a similar story with participles. “Rounding the corner, I encountered a man in a dark jumpsuit and a mask.” No problem. But again a little of this goes a long way. If every sentence starts like that it can be mind-numbing. And there’s the constant danger of dangling participles. Ain’t nobody needs that! So here again the highlighting draws my attention to something that may need to be checked out, but which will probably be OK.
*Having all the data in Excel makes it very easy to calculate this post-hoc. The actual average sentence length for this novel is 11.2 words.
Addendum: a sad glitch with Word2007
Shortly after I first wrote AnalyseSentences in 2019, I added a dialog box at the start of the run to make to analysis a little more flexible.
This made it easier to vary where the results were recorded, and change the values of the sentence lengths (defaulted to 25 and 50 as mentioned above) that would be flagged. It worked fine for several years, until…
Earlier this year when I attempted to run it against A Shadow On The Water. It crashed Word. I didn’t have time to diagnose the problem back then, but I have now. It crashes on the point of displaying this dialog.
I had a few attempts at fixing the fault, but in the end I’ve concluded it’s probably down to my set-up. I’m still using Word 2007 – 17 years old and out of support for some time. My PC runs Windows 2010 and the .NET framework too has changed considerably, so it’s seems likely that some combination of all of that makes the dialog barf.
But in all honesty moving away from the defaults was only a “nice to have.” It was a simple change to comment out use of the dialog, and set all the default values in a short chunk of code, which is easy to change if I ever feel the need to wander off piste. In that revised state, it runs just fine. But it does give me sad face to see physical evidence that my time using Visual Basic to make some aspects of life easier may be coming to an end.
Karbekidi – A Game of Stones
Life aboard ship – Part 2
I can’t remember when I first thought of having the crew and passengers spend some of their time in A Shadow On The Water playing a local game, but it must have been very early on in the plotting stage. I’ve read a few fantasy novels involving long sea voyages and it’s always seemed to me that it’s very easy for the journey to turn into a tedious tale if there aren’t enough diversions for the sailors.
In my time honoured way of near-infinite procrastination, I’d finished the draft before I finally planted myself in my chair to invent the game. That draft was littered with notes like [see the game played here for the first time], [first game aboard ship], and [explain the rules here but not as an infodump], so I knew what I needed and where to put it, but I left it until the last possible moment.
Because inventing a new game is hard.
I’m not going to claim this invented game is perfect. It can’t possibly be — at the time of writing, no-one has played it. So really, I don’t even know if the rules stand up to scrutiny. I had a kind of boyish fantasy that some entrepreneurial game manufacturer would pick up the idea and run with it, and we could share the undoubtedly massive royalties that would result. I doubt that will happen. Developing a new game takes a lot of investment, and many iterations of the rules to zero in on the best playability. I suspect this one, in its current form, is miles away from being playable, and that’s mainly because I only needed to understand it well enough to write about it in a believable way.
Still, you know, if there is anyone out there who would like to develop it further, please do drop me a line.
But for now, this is what it looks like:
Karbekidi is conceived as a stones game, similar to Mancala, that can be played on a marked table, but more usually on a purpose-made board (which is essential aboard ship to prevent stones rolling off the table due to wave action).
The game is played between 2-8 players.
A set comprises 8 Keystones and 64 Lumstones divided into 8 Wards, with each Ward having a Keystone and 8 Lumstones. Wards may be differentiated by colour, shape, or kinds of stone, depending on the style of the set.
The board has three zones. The outer ring — known as the “Lower Deck” or Karb — has 8 “home” positions or Drums, set at the corners and centres of the roughly square board (with rounded corners in Burman’s board). In between any two Drums are two smaller positions known as Cups.
The inner ring — known as the “Upper Deck” or Kidi — has a similar arrangement of Drums and Cups, but in this case only 4 Drums. The final zone, or Top Deck, contains a single Drum known as Top Drum. The objective of the game is for a player to move (one of) their Keystone(s) into the Top Drum position. This move wins the game.
And that’s more than enough description for a blog post! If you’d like to read a more detailed set of rules, including the sequence of play and variations to allow for a longer or shorter game, and perhaps even play it for yourself, you can download the full set of rules as a Word document by clicking on the graphic above.
If you do play, and you find one or more rules that don’t work, or you’d like to suggest any improvements, please do send me an email. I’d love to hear from you!
The Tam Baleng – Deck Plan
Life aboard ship
I wasn’t very far into the draft of A Shadow On The Water before I realised I was going to need a deck plan.
The reasons are both obvious, and very similar to why I drew up a map of Tenfir Abarad (which I’ve shared with you) and Duske Akdakalon (which I haven’t). When writing about where people are in a relatively small space, how they move around, and whether or not they can see each other, it’s very easy to lose track, make mistakes, and confuse the reader.
Adapting an existing deck plan I found on a sailing website was time well spent. I drew it up early enough to inform the draft and even suggest scenes that I hadn’t conceived in the original plot notes, and which made the story much stronger.
It’s included in all versions of the book, but being mindful of the limitations of Kindle and print copies, I wanted to make it available here for you too. As it’s a line drawing, there isn’t really a “hi-res” version, but even so you can still click on this image and download a local copy for yourself.
Kilautan – The Silver Sea
Final Fantasy Map for the Chronicles
Post contains minor spoilers for Book 2 – A Shadow On The Water.
I was really getting into the swing of having a map for every occasion by this time, and the ocean voyage undertaken by our heroes and their new friends was something else I thought absolutely demanded a map.
It was a challenge for my cartographer, but once again she came through in fine style, giving a clear impression of the distances involved while at the same time including enough detail to support the story.
This is the last map I will commission for this world. The whole of the final book of this second trilogy — due for publication in a couple of months — takes place in the land of Nanegria. But its detailed topography will remain shrouded in mystery. Readers will have to engage their imaginations to conjure up a more detailed picture of it than what appears in this map.
Click on the image to download the high resolution version (17MB download)
The Northern Territories
Fantasy Maps for the Second Chronicles
At the time of writing, my second trilogy set in the world of Berikatanya is about to conclude, so I thought it was time to make the maps accessible to a wider audience. Minor spoilers follow for anyone who hasn’t read these books yet.
Having found a fabulous fantasy cartographer for the first trilogy, I didn’t waste any time commissioning her to do the maps for these books. At the beginning of the story our heroes travel by various means into the “Northern Territories” which — at least in the early days — comprise little more than the town of Tenfir Abarad, where Jann spent some time while engaged on his personal quest.
As before, you may click on the image to download the full-size version (4MB download)
Since much of the action in the first book of the Second Berikatanyan Chronicles takes place in Tenfir, I thought it essential to also provide a town map, to give a clearer idea where the key buildings are, and which homes are occupied by the principal players.
In this case, the high-res version is slightly larger at 5MB. Again, click the image to download your own copy.
