Yup, I expect so.
Evan
From: Roger Loran Bailey (Redacted sender "rogerbailey81" for DMARC)
Sent: Saturday, June 18, 2016 3:06 PM
To: bksvol-discuss@xxxxxxxxxxxxx
Subject: [bksvol-discuss] Re: should I put spaces where they are not?
Nevertheless, though, a screen reader will probably render it as gibberish.
On 6/18/2016 10:05 AM, Evan Reese wrote:
I wouldn’t add any spaces. That’s a deliberate decision by the author and I
think it would be wrong to change it. The text to speech chips will just have
to fall where they may I’m afraid.
There’s nothing to prevent you from putting a scanner’s note in brackets
before the text begins mentioning that this occurs though so that readers know
that it’s not sloppy scanning or proofreading. And definitely put that into the
Comments section when you submit the book so the proofreader doesn’t “correct”
them.
Evan
From: john.falter
Sent: Saturday, June 18, 2016 7:23 AM
To: bksvol-discuss@xxxxxxxxxxxxx
Subject: [bksvol-discuss] should I put spaces where they are not?
[scanner's note: This book contains many segments where whole sentences are
run together as a single word. This is intended to indicate something done at a
frantic pace. I left these as they are, per the usual instructions, but I
wonder how well that will work in text to speech.
Also, the OCR made the word I into the number 1 in many cases. I fixed all
that I noticed, but there could still be some.]
------------------------------------------------------------------------------
This email has been checked for viruses by Avast antivirus software.
www.avast.com