Ah yes, but will it keep those three periods or will it immediately undo your replacements by reinserting the ellipsis character? I remember trying to replace those smart quotes with straight quotes back in 2006 when I first started with Bookshare using Word 2003. I was using OpenBook back then and it would insert opening and closing quotes instead of the straight quotes. So I wanted to undo that in MS Word, and it would tell me how many replacements it had made. But I found out that it was undoing my replacement of smart quotes with straight quotes by replacing my straight quotes with smart quotes until I went into some menu or other and told it to stop doing that. Not many of you will recall Jake’s site, but there was a tip up there that gave instructions on how to tell Word to stop insisting on using smart quotes, and the ellipsis character specifically because Word would not keep the replacements of those characters unless it was told to do so. Maybe Word 2013 is not quite so stubborn about that. I have that version here but I haven’t checked on that yet. Evan From: Kim Friedman Sent: Friday, May 23, 2014 6:00 PM To: bksvol-discuss@xxxxxxxxxxxxx Subject: [bksvol-discuss] Re: bksvol-discuss Digest V11 #116 Hi Evan, I’m running Word 2013 and you can still do a find-and-replace when Word puts in an ellipsis character. You can still write ^0133 in the find box and replace it with the three periods. (I can say this because I started proofreading something last night and had to do a couple of those find-and-replace jobs abovementioned. Regards, Kim Friedman. 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