[bksvol-discuss] Re: Guidelines for prep of books for submission?

  • From: "Gerald Hovas" <geraldhovas@xxxxxxxxxxx>
  • To: <bksvol-discuss@xxxxxxxxxxxxx>
  • Date: Wed, 17 Aug 2005 23:51:00 -0500

Jill,

Kurzweil has the ability to read DAISY books, and I would expect does a much
better job than Victor Reader Soft.  I've never had much luck with Victor
Reader Soft myself and suspect the explanation is given in the name of the
file that you receive when downloading Victor Reader Soft.  The filename
suggests that it is a Beta version, which is a version of software that has
not completed testing and is not ready for release to the general public.

I don't think the administrative process has anything to do with the
problems that you are referencing.  They are more likely caused by
submitters and validators not cleaning the book up properly.  Many
volunteers rely on Kurzweil's Ranked Spelling feature as an indicator of
quality rather than reading the book, and Ranked Spelling does not indicate
problems of these types, but only gives an indication of how many words in
the file are spelled correctly.  In fairness to those volunteers, the
guidelines for validation do not say that a book must be read all the way
through, but that is what is necessary to insure that mistakes like the ones
you mentioned are caught.

Gerald


-----Original Message-----
From: bksvol-discuss-bounce@xxxxxxxxxxxxx
[mailto:bksvol-discuss-bounce@xxxxxxxxxxxxx]On Behalf Of Jill O'Connell
Sent: Wednesday, August 17, 2005 11:30 PM
To: bksvol-discuss@xxxxxxxxxxxxx
Subject: [bksvol-discuss] Re: Guidelines for prep of books for
submission?


I am primarily a braille reader and have never used DAISY. However, I have
occasionally listened to Kurzwweil read a book that I have had it download
for me. Iss there any difference in listening this way as opposed to using
Bookshare's DAISY. Yes, we are working too hard trying to defeat the
stripper, and at the same time I am finding books that are rated excellent
that are a mess with page duplications, occasional headers, etc. etc. so I
can't help wondering what happens while a book is undergoing administrative
approval. I hope this gets straightened out before we all get discouraged in
our efforts to create high quality books.
----- Original Message -----
From: "Deborah Kent Stein" <dkent5817@xxxxxxx>
To: <bksvol-discuss@xxxxxxxxxxxxx>
Sent: Tuesday, August 16, 2005 12:47 PM
Subject: [bksvol-discuss] Re: Guidelines for prep of books for submission?


>
>
> Hi again,
>
> Once again I feel I must weigh in on the discussion of the stripper
> problem - a discussion which has become for me increasingly painful and
> frustrating.  It saddens me tremendously to find us working so hard to
> come
> up with ways to protect our files by outwitting the stripper, when we have
> no actual guidelines from management on what to do.  We should not have to
> struggle with this at all, and our efforts seem to be inconsistent and not
> very effective.
>
> Through a couple of exchanges with Jim I have begun to get a sense of what
> is going on, from an engineering standpoint - although my understanding
> may
> well be imperfect.  It seems that the stripper "grabs" page numbers and
> chapter headings in order to create the "tags" which are so valuable to
> Bookshare readers who use DAISY files.  Therefore, DAISY files would be
> harmed if the stripper were turned off.  The BRF files are being stripped
> of
> page numbers and chapter headings because the stripper is using them to
> create DAISY tags.  I have been told that this is "an output problem"
> which
> might be handled by the engineering department by working with the Duxbury
> program, which is used to create the BRF files.  I am trying to get the
> names of people in engineering in order to exchange ideas about what can
> be
> done, and to find out about the time frame we can expect.
>
> I think it is very important for everyone who is concerned about the
> condition of the BRF files to contact Jim Fruchterman and Janice Carter.
> Unless they hear from us, clearly and directly, it is easy for this issue
> to
> be kept on the back burner indefinitely.  Right now DAISY seems to be a
> priority and BRF is a neglected stepchild.  Those of us who prefer Braille
> to audio need to make our voices heard - Braille users deserve the same
> level of quality as DAISY users do.
>
> Debbie
> ----- Original Message -----
> From: "Jill O'Connell" <jillocon@xxxxxxxxxxxx>
> To: <bksvol-discuss@xxxxxxxxxxxxx>
> Sent: Tuesday, August 16, 2005 12:00 PM
> Subject: [bksvol-discuss] Re: Guidelines for prep of books for submission?
>
>
>> I can see the advantage of placing the chapter number on a different line
>> from the word "chapter" but if the page number which is constantly
> changing
>> is on that same line, wouldn't you think the stripper would leave it
> alone?
>> ----- Original Message -----
>> From: "Mike Pietruk" <pietruk@xxxxxxxxx>
>> To: <bksvol-discuss@xxxxxxxxxxxxx>
>> Sent: Monday, August 15, 2005 5:02 PM
>> Subject: [bksvol-discuss] Re: Guidelines for prep of books for
>> submission?
>>
>>
>> > Jill
>> >
>> > "protecting" is as much an art as a science.
>> > Basically, the stripper is fond of doing its handy work near the top
>> > and
>> > bottom of pages.
>> > Hence, I attempt to keep the "Chapter" a few lines away from the top by
>> > first leaving a couple of blank lines at the top of the page,
>> > then a line of a couple of hypphens, then another blank line, then the
>> > page number, then a blank line, then a line with a couple of hyphens,,
>> > then the Chapter heading.
>> > The idea is to give the stripper something to work on that can be lived
>> > without.
>> > Another good idea is to place the word "chapter" on one line and the
>> > number of that chapter on the line below.
>> >
>> >
>> >
>> >
>> >
>> > --
>> > No virus found in this incoming message.
>> > Checked by AVG Anti-Virus.
>> > Version: 7.0.338 / Virus Database: 267.10.10/73 - Release Date:
> 8/15/2005
>> >
>> >
>>
>>
>>
>
>
>
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.338 / Virus Database: 267.10.10/73 - Release Date: 8/15/2005
>
>



Other related posts: