[bksvol-discuss] Re: Headers
- From: "Sarah Van Oosterwijck" <curiousentity@xxxxxxxxxxxxx>
- To: <bksvol-discuss@xxxxxxxxxxxxx>
- Date: Fri, 11 Jun 2004 13:45:57 -0500
Thanks.
I encluded that request in a message to Kurzweil recently, too. Since they
know you, I am sure your request will get attention just a tiny bit better
than mine, and more than one squawk can't hurt. <bg>
Sarah Van Oosterwijck
curious entity at earthlink dot net
----- Original Message -----
From: "Guido Corona" <guidoc@xxxxxxxxxx>
To: <bksvol-discuss@xxxxxxxxxxxxx>
Sent: Friday, June 11, 2004 12:09 PM
Subject: [bksvol-discuss] Re: Headers
> Sarah, I have a call into K to request the info. If the feature is not
> available, I will suggest it.
>
> G.
>
>
> Guido D. Corona
> IBM Accessibility Center, Austin Tx.
> IBM Research,
> Phone: (512) 838-9735
> Email: guidoc@xxxxxxxxxxx
>
> Visit my weekly Accessibility WebLog at:
> http://www-3.ibm.com/able/weblog/corona_weblog.html
>
>
>
>
>
> "Sarah Van Oosterwijck" <curiousentity@xxxxxxxxxxxxx>
> Sent by: bksvol-discuss-bounce@xxxxxxxxxxxxx
> 06/11/2004 11:56 AM
> Please respond to
> bksvol-discuss
>
>
> To
> <bksvol-discuss@xxxxxxxxxxxxx>
> cc
>
> Subject
> [bksvol-discuss] Re: Headers
>
>
>
>
>
>
> Do you know if there is a way to type a character to represent a page
> break
> in the Kurzweil search dialog? i have looked for such a thing in the
> manual, but I didn't find it. I can only find directions for finding new
> line and tab characters. It would greatly reduce the work involved in
> removing those headers semi-manually if that were possible, and now I know
> that manual, or semi-manual, removal seems to be the only alternative.
>
> Sarah Van Oosterwijck
> curious entity at earthlink dot net
>
>
> ----- Original Message -----
> From: "Guido Corona" <guidoc@xxxxxxxxxx>
> To: <bksvol-discuss@xxxxxxxxxxxxx>
> Sent: Friday, June 11, 2004 11:41 AM
> Subject: [bksvol-discuss] Re: Headers
>
>
> > By the way, the Kurzweil stripper is over eager as well. I prefer to
> > strip my headers manually even on Kurzweil. I.e. I manually remove
> > repeating words in page headers, but leave and repair page numbers and
> > try to do repair any corrupted chapter headers, including the word
> > 'CHAPTER'.
> >
> > Guido
> >
> >
> > Guido D. Corona
> > IBM Accessibility Center, Austin Tx.
> > IBM Research,
> > Phone: (512) 838-9735
> > Email: guidoc@xxxxxxxxxxx
> >
> > Visit my weekly Accessibility WebLog at:
> > http://www-3.ibm.com/able/weblog/corona_weblog.html
> >
> >
> >
> >
> >
> > "Sarah Van Oosterwijck" <curiousentity@xxxxxxxxxxxxx>
> > Sent by: bksvol-discuss-bounce@xxxxxxxxxxxxx
> > 06/11/2004 11:27 AM
> > Please respond to
> > bksvol-discuss
> >
> >
> > To
> > <bksvol-discuss@xxxxxxxxxxxxx>
> > cc
> >
> > Subject
> > [bksvol-discuss] Re: Headers
> >
> >
> >
> >
> >
> >
> > Grrr! It seems that bookshare's header stripper has a slightly
> different
> > idea about what headers are, and it isn't acceptable. It probably
> > wouldn't
> > strip if the chapters had titles, but they only had the word chapter and
> > the
> > number. When I read with Kurzweil it did seem to read properly once I
> > fixed
> > them. It read chapter and skipped the title or author that was on the
> top
> > of every page.
> > Now i wonder what I can do to solve the problem. I don't want Kurzweil
> to
> > do the stripping because it would be best if the page numbers stayed at
> > least until validation. I also don't like experimenting, because a lot
> of
> > things can be messed up before you ever know what happened in the end,
> and
> > it takes a lot of time for the whole process to be completed. <sigh>
> > Any ideas, anyone?
> >
> > Sarah Van Oosterwijck
> > curious entity at earthlink dot net
> >
> > ----- Original Message -----
> > From: "Tracy Carcione" <carcione@xxxxxxxxx>
> > To: <bksvol-discuss@xxxxxxxxxxxxx>
> > Sent: Friday, June 11, 2004 10:51 AM
> > Subject: [bksvol-discuss] Re: Headers
> >
> >
> > > Sarah,
> > > Indeed it is Survivors' Quest. There are no page headers, which I
> > > appreciate, but, so far, no chapter headers either.
> > >
> > > I am going by what Kurzweil tech once told me, that a header is
> defined
> > as
> > a
> > > line at the top of the page, followed by a blank line.
> > > I thought putting a blank line or two before a chapter heading would
> to
> > the
> > > trick, but now you've got me worried.
> > > Tracy
> > >
> > > At 10:31 AM 6/11/04 -0500, you wrote:
> > > >I just want to make sure the book you are reading is not Star Wars
> > > >Survivor's Quest, which I submitted, because that would mean that my
> > > >attention to the headers did not succeed. I have started making sure
> > that
> > > >there is a blank line after each page header, and that every header
> is
> > > >against the top of the page. I put one blank line between the top of
> > the
> > > >page and a chapter heading. If page numbers are at the bottum of the
> > page I
> > > >put a blank line between the last line of text and the page number. I
> > want
> > > >to make sure this method works all right.
> > > >
> > > >
> > > >
> > > >----- Original Message -----
> > > >From: "Tracy Carcione" <carcione@xxxxxxxxx>
> > > >To: <bksvol-discuss@xxxxxxxxxxxxx>
> > > >Sent: Friday, June 11, 2004 7:24 AM
> > > >Subject: [bksvol-discuss] Headers
> > > >
> > > >
> > > >> I'm going to talk again about headers. I think it's very important
> > to
> > go
> > > >> through and put a blank line or two between the top of a page and a
> > > >chapter
> > > >> title. I am reading a Star Wars book (and enjoying it very much,
> > thanks!)
> > > >> and all the chapter headings are missing. I think that the chapter
> > title
> > > >> was at the top of the page, followed by a blank line, so
> Bookshare's
> > > >> automatic header-deleter flagged it as a header and deleted it. In
> > this
> > > >> particular book, it's no big deal, but in books with meaningful
> > chapter
> > > >> headings, or a book needed for school, it could make a significant
> > > >difference.
> > > >> Tracy
> > > >>
> > > >>
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
> >
> >
>
>
>
>
Other related posts:
