[bksvol-discuss] Re: bksvol-discuss Digest V11 #116
- From: "Evan Reese" <mentat1@xxxxxxxxxxxxxx>
- To: <bksvol-discuss@xxxxxxxxxxxxx>
- Date: Fri, 23 May 2014 17:27:30 -0400
Hi Madeleine,
Ouch! Thanks for this. So there’s really nothing we can do on our end to make
the ellipsis come out right in braille as there used to be. Even though this is
not good news, it’s still good to know so we at least know what’s going on.
Evan
From: Madeleine Linares
Sent: Friday, May 23, 2014 4:50 PM
To: bksvol-discuss@xxxxxxxxxxxxx
Subject: [bksvol-discuss] Re: bksvol-discuss Digest V11 #116
Hi Evan,
Thanks for responding. I shared this with our staff person who’s actually doing
the testing and here’s her response:
“I have tested three periods in a row – making sure that it does NOT get
automatically converted to the ellipsis character. The converter is apparently
seeing three periods as an ellipsis and converting it the same way it
incorrectly converts an ellipsis character.
It may have worked in the past differently of course, but that is what it is
doing now.”
We have put in a request to engineering to fix this.
Best,
Madeleine
From: bksvol-discuss-bounce@xxxxxxxxxxxxx
[mailto:bksvol-discuss-bounce@xxxxxxxxxxxxx] On Behalf Of Evan Reese
Sent: Friday, May 23, 2014 1:41 PM
To: bksvol-discuss@xxxxxxxxxxxxx
Subject: [bksvol-discuss] Re: bksvol-discuss Digest V11 #116
Minor correction:
The ellipsis *character* is not being converted correctly by the braille
translator. Three periods in a row, without spaces, are rendered in braille
just fine. So a viable solution to rendering ellipses correctly in braille is
to simply use three periods, four periods without spaces if the ellipses in the
book is followed by a period. This has always worked. The problem is that MS
Word will automatically substitute the ellipsis character for the three periods
if it isn’t told not to. At least the 2003 version I used to use did that. I
don’t know whether newer versions of MS Word will do that or not, but I
strongly suspect that they will.
The ultimate solution of course is to add the ellipsis character to the
translation table in the braille translator, (along with other higher value
ANSI characters such as fractions). That is up to whoever wrote the program;
or, if it is open source, then anyone with the source code could do it. I have
no idea on that score. But it would sure be nice if, here in the year 2014, our
braille translator could handle these kinds of things.
Evan
From: Madeleine Linares
Sent: Friday, May 23, 2014 4:28 PM
To: bksvol-discuss@xxxxxxxxxxxxx
Subject: [bksvol-discuss] Re: bksvol-discuss Digest V11 #116
Hi all,
Here is the latest of what I have so far:
a. Ellipses
i. These
can be written as three periods in a row OR as the ellipsis character. Both are
recognized
ii. The
ellipsis should have no space before it and the word preceding it, and one
space after before the next word
1. Example: The ellipsis rule can be confusing… but hopefully these
instructions help!
iii. If there
is a period after the ellipsis in the text, add the period directly after the
three dots. There should be four dots in a row, a space, and then the beginning
of the next sentence. DO NOT add a period after an ellipsis if the original
text hasn’t added one
1. Example: Hopefully we can clarify this ellipsis rule enough…. I think
these instructions might help!
iv. Please note
that at this time (5/15/14) ellipses are not being converted into BRF correctly
at all and we are working to fix this. While one solution can be to add spaces
between the dots in the ellipsis, this causes problems when it is read aloud in
other readers so it isn’t a solution
b. Em-Dashes
i.
Em-dashes can be EITHER the em-dash character or two dashes. Both will convert
to two dashes
ii. Make sure
that there is EITHER one space on either side of the dash(es) or no spaces on
either side. Make sure this is consistent throughout the text
c. Dashes (simple)
i. Do not
put a space before or after the dash because if you do, some readers will read
out the word after the dash letter by letter
d. Quotation Marks
i. Single
(straight, opening, or closing) are converted to straight quotation marks
ii. Double
(straight, opening, or closing) are converted to straight quotation marks
iii. Use
whichever version the print copy uses, but both will be recognized
Judy already posted information about footnotes. We will be testing the issue
of putting a space between a superscript number and a word, so I will share
that clarification when I know.
Best,
Madeleine Linares
Volunteer Coordinator
Bookshare, a Benetech Initiative
650-644-3459
volunteer@xxxxxxxxxxxxx
From: bksvol-discuss-bounce@xxxxxxxxxxxxx
[mailto:bksvol-discuss-bounce@xxxxxxxxxxxxx] On Behalf Of Jack Teeter
Sent: Friday, May 23, 2014 7:04 AM
To: bksvol-discuss@xxxxxxxxxxxxx
Subject: [bksvol-discuss] Re: bksvol-discuss Digest V11 #116
How about some concrete examples?
Seems there are changes to:
1. elipses
2. quotes
3. em dashes
4. footnotes
Please provide a sample page that presents a clear example of each. In the case
where more than one solution is acceptable give only the preferred solution --
I can adapt if I can see exactly what I need to do to comply.
Regards,
Jack Teeter
Brighton, IL
Other related posts:
