[bksvol-discuss] Re: Problem with OpenBook

HI Evan:

Your understanding is correct. That's exactly what I would do.

Grace
  ----- Original Message ----- 
  From: Evan Reese 
  To: bksvol-discuss@xxxxxxxxxxxxx 
  Sent: Monday, February 13, 2006 10:53 PM
  Subject: [bksvol-discuss] Re: Problem with OpenBook


  Ok, from the 'Launch' menu.  I scanned a few pages and opened Wordpad from 
that menu and the pages came up in .rtf format looking the way they should.  So 
I guess if I understand you and Grace correctly, it would probably be best to 
just save in .ark format until the book is done, then launch Word or Wordpad 
and hopefully the .rtf version will look the way it should without the 
extraneous codes.  Please let me know if my understanding is faulty on this.

  Thanks, Grace and Jake.
    ----- Original Message ----- 
    From: Jake Brownell 
    To: bksvol-discuss@xxxxxxxxxxxxx 
    Sent: Monday, February 13, 2006 6:56 PM
    Subject: [bksvol-discuss] Re: Problem with OpenBook


    Hi Evan,
        OpenBook will simply open up whichever product you select and will pass 
along the text of the file your working on. Basically it'll be put into a 
default document in the other program. Word will default to .doc and WordPad 
will default to RTF. Of course you can use word's File > Save As command to 
save in RTF.

    I'll get back sometime soon (within the next day or so) with instructions 
on OpenBook. They're not complex, but I've got some stuff for class that needs 
my attention.

    Glad to be of service *grin*
    Jake
      ----- Original Message ----- 
      From: Evan Reese 
      To: bksvol-discuss@xxxxxxxxxxxxx 
      Sent: Monday, February 13, 2006 8:50 PM
      Subject: [bksvol-discuss] Re: Problem with OpenBook


      I guess I should have asked Grace, but doesn't Word or Wordpad have to be 
able to recognize .ark files to be able to load them and convert them?

      Also, I didn't know OpenBook worked with JAWS.  Yes, I would like to have 
a look at that stuff.  Your right, it may still crash, but the majority of 
problems I have are with the Viavoice errors that I was getting quite a lot of 
today.  And for the first time while using OpenBook I got an error from 
ssilexe.  I looked it up on Google and found out what it was, but I didn't know 
I had that on here until just today.

      Thanks, again, Jake.  Now where's that Jake keyboard macro? <grin>

        ----- Original Message ----- 
        From: Jake Brownell 
        To: bksvol-discuss@xxxxxxxxxxxxx 
        Sent: Monday, February 13, 2006 6:39 PM
        Subject: [bksvol-discuss] Re: Problem with OpenBook


        Hi Evan,
            OpenBook unstable? that's the understatement of the year. 
Unfortunately its architecture has not been maintained in today's computing 
environments.

        I strongly recommend saving as an ARK file until you are ready to 
submit the book, at which time you should go ahead and do the conversion. It's 
always a good idea to keep things in a programs native format, less issues can 
arise in use that way. BTW That's what I've always done and I haven't ever 
experienced the coding issue first hand.

        As Grace said you can attempt to launch the file into Word or WordPad 
and save as an RTF file there.

        I can send/post along instructions for using OpenBook with JAWS if you 
think you might be interested. It'll generally stop the IBM TTS crashes that 
can sometimes be quite numerous. OB will still crash more than you'd like, but 
at least its a partial improvement.

        HTH,
        Jake
          ----- Original Message ----- 
          From: Evan Reese 
          To: bksvol-discuss@xxxxxxxxxxxxx 
          Sent: Monday, February 13, 2006 8:33 PM
          Subject: [bksvol-discuss] Re: Problem with OpenBook


          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



----------------------------------------------------------------------


          No virus found in this incoming message.
          Checked by AVG Free Edition.
          Version: 7.1.375 / Virus Database: 267.15.6/258 - Release Date: 
2/13/2006



--------------------------------------------------------------------------


      No virus found in this incoming message.
      Checked by AVG Free Edition.
      Version: 7.1.375 / Virus Database: 267.15.6/258 - Release Date: 2/13/2006

Other related posts: