Jamie, Yes, but I can convert it to rtf and still work on it in Kurzweil. With another word processing program there might not be a problem and I am looking for another one but at the moment I have WordPerfect and it can make a mess with a program faster than you can write a sentence. And if I submit it in kes then another person with kes will validate it and there is less room for program screw-up. As far as I can tell, Bookshare has not trouble converting kes files for the inclusion in the collection. Doing it all in Kurzweil means I can rescan if needed and send the rescanned page/s to the validator if need be which is another argument for the validator being able to contact the scanner. Plus the validator, if s/he has a copy of the book, he can rescan a page if needed or discuss a problem with the scanner. This can happen with books with dialect or technical language and similar problem areas. Amy omsm ----- Original Message ----- From: Jamie Yates To: bksvol-discuss@xxxxxxxxxxxxx Sent: Friday, August 24, 2007 10:37 PM Subject: [bksvol-discuss] Re: RTF format. But in the end, a KES submission STILL has to be converted to RTF format so it can go through the final processing, right? So what is the difference if the person who scans a book starts out with a KES file and converts to RTF to submit, or if the person who validates a KES file converts it to RTF for final approval? Somewhere, that KES file still has to be converted. Wouldn't you rather have whatever glitches are created by the conversion be fixed in the validation process, rather than have the glitches STAY in the file because it was converted at the time of the step 2 uploading? Jamie in Michigan Currently Reading - A Fistful of Rain - Greg Ruckar Groceries delivered to your home from Vons. Click here.