There is or may be a good reason for keeping a file scanned in Kurzweil to remain a kes file. I am going to have to rescan two books because after I converted the completed scan to rtf and I had uploaded it, the files that remained I kept in both the Kurzweil and WordPerfect and the latter kept converting everything to read-only with backups that were also wordpad and read only and the kes versions started also having problems. The rtf file I uploaded was good and was validated but apparently it then started being weird and after 3 people turned it back for validation I downloaded what turned out to be an unusable file as it was 3.62 mb and too larger to be opened. I had to reject it and now since all of my copies were corrupted somehow I will begin again with a new scan. Same type of problem I had with the other book so I am rescanning two books and keeping them in Kurzweil. I will only convert them to rtf if I absolutely must and even then I plan to work on it in Kurzweil if possible or keep a kes copy as back-up. And I will never again eliminate all my good copies unless and until it is in the Bookshare collection and not in progress. 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.