Yah, I have been saving as .rtf as I go along; that is, doing a hundred pages or so, then recognizing and saving incrementally as I go along. I was doing that in case OpenBook does one of its voice failures - which I get from time to time - and it stops talking. The only thing I can do when this happens is close OpenBook and start again. It does bring up a dialogue box, which I can read with JAWS cursor asking me if I want to save the file before I quit, but since OpenBook itself isn't talking, I can't be sure what button I'm on to close the program. I'm sorry to say it, but from my experience, OpenBook is not the most stable program I have ever used. ----- Original Message ----- From: Silvara To: bksvol-discuss@xxxxxxxxxxxxx Sent: Monday, February 13, 2006 5:46 PM Subject: [bksvol-discuss] Re: Problem with OpenBook Evan: I have experienced this a few times. Somehow it's revealing the hidden codes or something. The only solution I found was to launch the file in to Word and then save it as rtf. Are you scanning and saving the file as rtf? I found that it was better to keep saving in ark format until I finished scanning. Grace ----- Original Message ----- From: Evan Reese To: bksvol-discuss@xxxxxxxxxxxxx Sent: Monday, February 13, 2006 7:32 PM Subject: [bksvol-discuss] Problem with OpenBook Hi, everyone, I'm having an intermittent problem with OpenBook and I was wondering if anyone else here has had a similar experience. It started just this morning, when saving as .rtf, I'm getting a file that looks like one long line with \par \par where the paragraphs should begin. But that's not all: It is also giving me a \rquote that extra space is there deliberately - where each apostrophe should be. Where a title is located, there is a whole raft of similar-looking stuff. The problem is worse because I can't seem to create it at will. Also, it doesn't always happen. It started just this morning after I began playing with the contrast setting - I had kept it on automatic up to now, but I can't see how that could have anything to do with it, and I am currently on setting 150 because it is giving good results in the text recognition department and I'm not getting these characters now. That's the frustrating part: I can't cause the problem. I haven't changed any other settings that I recall, but I can't swear it. The first page of the book starts like this: {\rtf1\ansi\ansicpg1252\uc1 \page \fs24 etc. (The etc. is not part of the sample.) A few weeks ago, someone - I think it was on the other list - said that he had seen this, but I think it was in a file he was validating, not one he had scanned. At the time, I said that it looked like something viewed in one file format that was intended to be read by another program, like reading a file in a native word processor format such as .doc or wp5 in a text reader. It looks as though OpenBook is saving the file in .rtf but not actually converting it; but it has never done that before, and that's just a guess. Anyone had OpenBook or another scanner doing this, and know how to cause it, and better how to prevent it? Thanks for any feedback. ---------------------------------------------------------------------------- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.15.7/259 - Release Date: 2/13/2006 ------------------------------------------------------------------------------ No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.15.7/259 - Release Date: 2/13/2006