[bookshare-discuss] Re: Question About OpenBook and Hard Returns
- From: "Evan Reese" <mentat1@xxxxxxxxxxxxxx>
- To: <bookshare-discuss@xxxxxxxxxxxxx>
- Date: Sun, 5 Feb 2006 22:21:14 -0800
Yes, that was it. I scanned the same page with collumn detection on and off,
and the problem disappeared with collumns enabled.
The irony is that I always keep column detection enabled. This is a Science
Fiction book, and at the beginning is a list of units of time in terms of light
speed, such as light-year, light-month, light-day, etc. and the equivalent
distance. OpenBook broke this up into collumns, so I turned collumn detection
off and neglected to turn it on again. I just figured, "What difference would
it make since there are no collumns in the book anyhow." But it does make a
difference, and I won't forget this in the future.
I'm going to submit this book anyhow. It is _CUSP_ by Robert A. Metzger. I'm
pretty sure that people who like hard SF will really enjoy it. I know I did,
and I've read a lot of this kind of stuff. Because besides this issue the text
is in nearly perfect shape. (I would say it is in perfect shape, since I have
read every word and corrected every error I found. But I'm not a certified
proofreader, and sometimes I miss things when I'm really enjoying a book. My
brain just sometimes seems to fix things in my head without telling me
something's wrong on the page.) But I can say that the text is very, very
good. Also, following the advice of you and others on this list, the book
contains all page numbers and all page breaks - including all blank pages. I
just hope that the result doesn't look too terrible for Braille readers.
Thanks, again.
----- Original Message -----
From: Jake Brownell
To: bookshare-discuss@xxxxxxxxxxxxx
Sent: Sunday, February 05, 2006 8:53 PM
Subject: [bookshare-discuss] Re: Question About OpenBook and Hard Returns
Hi Evan,
You might try toggling the Recognize columns recognition setting.
Generally you want this enabled unless scanning something like a table of
contents.
Let me know if this is the culpret, if not I'll dig out my laptop and fire up
a copy of OB and see if I can find any other setting that might apply.
HTH,
Jake
----- Original Message -----
From: Evan Reese
To: bookshare-discuss@xxxxxxxxxxxxx
Sent: Sunday, February 05, 2006 10:13 PM
Subject: [bookshare-discuss] Question About OpenBook and Hard Returns
I just finished a book, and while I was reading through it on my Braille
displayI noticed that I was getting many short lines. My Braille display fills
up, then the remainder of the print line is carried over to the next partial
Braille line. It seems that in .rtf format, not only does OpenBook put a blank
line between each paragraph - two hard returns - but it also seems to put one
at the end of each line of print. Also, after a hyphenated word at the end of
a line, it puts a hard return, so you get a hard return and a space where the
hyphenated word ends on the next line. I've looked through all the settings in
OpenBook and haven't found anything that will change what it does at the end of
a line, and this problem with hyphenation just seems to be a bug. I didn't
notice this before because it doesn't seem to happen in standard .txt format -
although there is an option for text with line breaks which may do the same
thing. I haven't used that, though.
I was able to fix these hard return space goofs easily enough, and in
future books I can do a couple search-and-replace operations to strip out the
hard returns from the ends of lines, leaving only those at the ends of
paragraphs and in other obvious places. But in the book I just finished, I
pulled many of them out by hand so the Braille lines would look better, at
least on my display; although I'm sure I missed many if the line wasn't really
short. What will the Braille translator do with this? The only way to be sure
of getting them all out is to go through the book line by line, something I
have no desire to do. Or, I could just leave them in in future scans. For
speech readers reading continuously, of course, this is of no importance, but
for Braille readers it may look pretty horrible since the length of the Braille
display probably won't agree with whatever margins I set - since they aren't
all the same - and grade two translation also has an effect on line length.
Besides, setting shorter margins will just create half-empty lines in the
original .rtf file, and setting wider margins will do nothing.
I need advice from Braille readers out there and those who know about
Bookshare's Braille translator, or from anyone who knows how to fix this
problem in OpenBook - assuming it should be fixed. That's one of the things I
need to know.
Thanks for any help anyone has to offer.
----------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.15.2/251 - Release Date: 2/4/2006
Other related posts:
