Right, I followed Kelly's message and between our two headaches I guess we got our wires crossed. Rose Combs rosecombs@xxxxxxxxx -----Original Message----- From: bksvol-discuss-bounce@xxxxxxxxxxxxx [mailto:bksvol-discuss-bounce@xxxxxxxxxxxxx] On Behalf Of Jana Jackson Sent: Sunday, July 03, 2005 9:31 PM To: bksvol-discuss@xxxxxxxxxxxxx Subject: [bksvol-discuss] Re: Validating Hi, Rose! You want to search for hyphen, backslash T or hyphen, backslash N. I think you've been using the forward slash. You want the backslash, right below the backspace key. Hopefully, this will help. Happy 4th! Jana ----- Original Message ----- From: "Rose Combs" <rosecombs@xxxxxxxxx> To: <bksvol-discuss@xxxxxxxxxxxxx> Sent: Sunday, July 03, 2005 11:14 PM Subject: [bksvol-discuss] Re: Validating > Message is not scrambled, but my brains are, and I know the headache > thing. > > It sits here and keeps showing me a -nl in for example me-chanical and I > have tried searching for -/n -/t -/t/n and it says there are none but I > am sitting here looking at one and more in the same paragraph. I have > been reading the manual, following your suggestions, and either I am > going to have to submit it the way it is because from reading I am not > finding spelling errors, missing pages or anything or I am going to have > to release it. > > I cannot devote a whole week to doing this task manually, it just won't > work that way. > > > > Rose Combs > rosecombs@xxxxxxxxx > > -----Original Message----- > From: bksvol-discuss-bounce@xxxxxxxxxxxxx > [mailto:bksvol-discuss-bounce@xxxxxxxxxxxxx] On Behalf Of Kellie > Hartmann > Sent: Sunday, July 03, 2005 1:16 PM > To: bksvol-discuss@xxxxxxxxxxxxx > Subject: [bksvol-discuss] Re: Validating > > > Hi Rose, > Wow, you're brave to take on a gigantic project like this for your first > validation effort. Your experience with medical terminology is a great > asset > for the Bookshare collection. Just make sure you do other more fun > validations too so you don't get Bookshare burnout. <grin> > Here are some instructions/suggestions for your situation. > > First, it may be that the tabs following the hyphens are throwing off > Kurzweil's auto-correction feature. Try replacing hyphen followed by tab > with just hyphen, then run the autocorrect again and see if it helps. > The > way to make a tab in the find/replace box is \t > If that doesn't work, what you might want to do is replace hyphen > followed > by newline, or hyphen followed by tab newline, whichever is occurring, > with > nothing. To do this in Kurzweil all you have to know is that the way to > make > a tab in the find/replace dialogue is \t and the newline character is \n > So to fix a hyphen followed by tab and linebreak you would hit ctrl-h to > enter the find/replace box, then type -\t\n and put nothing in the > replace > with field. After you've done a mass f/r such as this, it's always good > to > check around and make sure it didn't have any unintended consequences. > So I > would save any other changes you made before starting this so you won't > lose > any other changes you may have made if something goes funky with the > f/r. > > I'm sorry if this message is a bit scrambled, I've been dealing with a > three-day-long migraine, and between that and the unfortunately not as > effective as I'd like medicine I may not be running on all eight > cyllinders. > Kellie > > > > > > >