[bksvol-discuss] Re: Is the Braille Translator Messing Up Ellipses?
- From: "Mayrie ReNae" <mayrierenae@xxxxxxxxx>
- To: <bksvol-discuss@xxxxxxxxxxxxx>
- Date: Fri, 8 Apr 2011 10:14:43 -0700
Hi Lori,
I can't find it now either. And the only way I could find to make it work
was to type three periods, let Word create the ellipses character, then when
I'm done, go back and do a find and replace with that character in the find
box, and three periods in the replace box. It seems the autoformat only
happens as you type, not upon opening a document.
I know there's a way to change this and make Word not create the ellipses
character when you type three periods, but I can't remember how to do it
now, and can't find it in the menus either.
Frustrating! But finding one and replacing all of them in the document
works. Guess it's something to do at the very end of proofreading.
I'm sorry. I wish my memory weren't so awful!
See how bad it is that I proofread primarily using Kurzweil? I'd know this
if I used Word more!
Again, I'm sorry!
I'll bet Melissa, or Judy knows how to fix this! So, so sorry!
Mayrie
_____
From: bksvol-discuss-bounce@xxxxxxxxxxxxx
[mailto:bksvol-discuss-bounce@xxxxxxxxxxxxx] On Behalf Of Lori Castner
Sent: Friday, April 08, 2011 9:46 AM
To: bksvol-discuss@xxxxxxxxxxxxx
Subject: [bksvol-discuss] Re: Is the Braille Translator Messing Up Ellipses?
Mayrie,
I've looked everywhere under autoCorrect and autoFormat to verify that I
have ellipses turned off. I can't find it anywhere.
I have Word 2002.
Lori C.
----- Original Message -----
From: Mayrie <mailto:mayrierenae@xxxxxxxxx> ReNae
To: bksvol-discuss@xxxxxxxxxxxxx
Sent: Thursday, April 07, 2011 8:06 PM
Subject: [bksvol-discuss] Re: Is the Braille Translator Messing Up Ellipses?
Hi Evan,
I'm discovering messages in my folder of volunteer e-mails that I never saw
come in, so please forgive this very late answer to your probably long
forgotten note.
You ask about the ellipsis being inaccurately represented in brf copies of
Bookshare's books. One cause of this may be that the proofreader didn't
have the autoformatting feature of Word turned off that changes all ellipsis
typed as three periods into the ellipsis character. If this is not turned
off, when a person types three periods, or unites three periods separated by
spaces, the resulting thing will be the ellipsis character, which the
braille translator as yet can't translate properly. So, all proofreaders
using Word need to turn off that autoformatting feature.
Hope that makes sense.
Mayrie
_____
From: bksvol-discuss-bounce@xxxxxxxxxxxxx
[mailto:bksvol-discuss-bounce@xxxxxxxxxxxxx] On Behalf Of EVAN REESE
Sent: Sunday, September 12, 2010 8:33 PM
To: bksvol-discuss@xxxxxxxxxxxxx
Subject: [bksvol-discuss] Is the Braille Translator Messing Up Ellipses?
I don't normally read books I've scanned after they get approved, since I
either read through them before submitting them, or I scanned them for
someone else that I myself didn't want to read, but knew they would read
through completely before checking them in. Today though, I started reading
a book that I didn't read when I scanned it, but that Lissi thought I would
like. In the brf version of the book, I discovered that everywhere there is
an ellipsis, (three periods in a row without spaces, not the special
character ellipsis), the brf version of the file has not the three dot
threes that are supposed to be there, but just one dot three. I checked a
slightly older book that we did and found the same thing. I compared the brf
file I downloaded from Bookshare with the original file I scanned, so
there's no mistake. All the ellipses in the brf versions are just one dot
three.
I don't know how far back this goes. The book I originally discovered this
issue in was added to the collection on July 30, 2010. The slightly older
book I checked which has the same problem was added on April 16, 2010; so
it's been going on for at least several months, unless it's been fixed since
July 30. I'm sure that the brf versions used to have the ellipsis correct,
but at some point it seems that a bug was introduced.
Evan
Other related posts:
