[bksvol-discuss] Re: Some additions to the scanning and proofing manual

  • From: "Mayrie ReNae" <mayrierenae@xxxxxxxxx>
  • To: <bksvol-discuss@xxxxxxxxxxxxx>
  • Date: Thu, 13 Aug 2009 08:08:00 -0700

HI Paula,
    I do know that the blank lines surrounding page breaks can be created
using Kurzweil, but some folks were having trouble getting this to work, so
I opted to go for a sure thing, until we know that K1000 isn't glitching on
this process any more.  I didn't want to cause more frustration than
necessary.  But you are right, it should be able to be done.  Here's hoping
that problem is fixed in K1000 and reported to us soon!


From: bksvol-discuss-bounce@xxxxxxxxxxxxx
[mailto:bksvol-discuss-bounce@xxxxxxxxxxxxx] On Behalf Of Paula and James
Sent: Thursday, August 13, 2009 7:59 AM
To: Bkvol
Subject: [bksvol-discuss] Re: Some additions to the scanning and proofing

Hi, Mayrie,
    Thank you for tackling my multitude of questions! Smile.
    That's a great idea to search for pages without headers, and see if they
contain chapter titles that need to be fixed. I also didn't realize the
Bookshare tools could have trouble, if page breaks are not surrounded by
blank lines. In K1000, you should be able to replace backslash p with
backslash n, backslash p, backslash n. I mention this only because some
people may, like me, not be very proficient in Word. I think the section
breaks you mentioned are the only things that can't be fixed in K1000.
    As far as end-of-line hyphens, when you first open a book in K1000, you
can go to the Edit menu, and hit Enter on Apply Corrections. That should
reunite those words, provided Correction of End-of-line Hyphens is enabled
under the General Settings menu. I could be wrong about that, though.
    Anyway, thanks for all the good suggestions. I have a file with things
to do when proofreading, and now I have some more helpful notes to add to

----- Original Message ----- 
From: Mayrie  <mailto:mayrierenae@xxxxxxxxx> ReNae 
To: bksvol-discuss@xxxxxxxxxxxxx 
Sent: Wednesday, August 12, 2009 11:31 PM
Subject: [bksvol-discuss] Re: Some additions to the scanning and proofing

Hi Paula,
    Lots of good questions.  Let me preface by saying that there is often
more than one way to achieve any given goal.  So, if one way doesn't work,
but another does for you, please use it.  In creating the instructions about
which you speak, we would have had to write a novel to include every single
eventuality.  I'd have gone mad!  I might be there already.  Now, on to your
    First, as to an easy way to enlarge the font size of chapter headings.
There isn't a simple way to do this.  There are lots of options for
achieving it though.  As you say, you can just fix them as you read.  That
is the most straight forward.  However, here is what I do.  Please remember,
this is just my way of doing this and isn't by any means the only way.  
    Very often, the only way to know where chapter headings are or should be
is by the absence of a running header on that page.  So, If I'm lucky, and
the chapter heading actually contains the word "chapter" I can do a find on
that word, locate each chapter heading and enlarge it before I ever start
reading.  If the word chapter is not always present, or the font is weird
enough that that word doesn't scan clearly, I will page down through the
document and look for pages without headers.  Very often chapter headings
can be located and/or inserted this way, and enlarged as located or
    Those aren't really quick things to do, but they are what I know to do.
    Next, the end of line hyphens should be nonexistent if settings were set
properly when the scanner scanned the book.  However, doing this find and
replace just finds the problem and fixes it if the scanner did not have the
setting enabled.  Did I answer that one?
    The blank lines at the top of the pages exist to ensure that the tools
can locate page numbers properly.  The new tools are supposed to have less
trouble with this kind of thing than the old tools did, but since they have
had troubles with other things that were supposed to be fixed, I left this
step in the instructions.  In short, the blank lines surrounding page
numbers exist as a shout out to the conversion tools that "hello, yes, there
is a page number here that you need to do something about."  Sorry, kind of
vague, but the best I've got.  Please ask again if I need to elaborate more.
You are correct that using the find and replace to get rid of extra carriage
returns can cause lists to be united when they shouldn't if they do not have
an initial upper case letter.  This was one of the eventualities that we
didn't include in the instructions.  The lists can always be reunited when
reading if they get turned into straight text.  Another option is to read
the book before performing this step, either adding a space or an asterisk
before each list item beginning with a lower case letter to keep what you
are talking about from happening while you read, then perform the step once
you've finished reading to catch any extra paragraph marks that you might
not have noticed while reading.  

     Yes, the braille translator does still have trouble with some bullets.
I generally replace those with asterisks.  The braille translator knows
about those! 
    And finally, yes, replacing smart quotes with straight quotes can be
done using Kurzweil 1000 as you describe.  It's just another option.  And
honestly, when writing the instructions, I didn't and still don't, have any
clue for the sequence that would be used for an em dash.  So, I personally
have to do that replacement, if I want to do it quickly in Word. Just
another example of more than one way to skin a cat.  And if the book has
section breaks, that must be done in Word to the best of my knowledge.  So,
why not do a bunch of simple steps while you're already there?  But again,
that's just me.
    Thanks for all of the great questions.  Please ask again if I've left
out anything, or been unclear.  
Happy proofreading.

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4332 (20090813) __________

The message was checked by ESET NOD32 Antivirus.


Other related posts: