yes, I find no fault with dazie and infact that would be much better than rtf. You use a table of contents at the top and link it so that each page is paired with one of the items i call them name and number tags. You can even draw some sort of breakin lines if you like. I'm sure it would not be too difficult to have duxbury recognize this. ----- Original Message ----- From: "John J. Boyer" <director@chpi.org> To: <blinux-list@redhat.com> Sent: Friday, June 14, 2002 2:04 PM Subject: Re: Book Share and Linux David, How would you separate pages with anchor text? After all, Daisy must have some means of indicating page breaks and page numbers, and I think it's XML. Thanks. John On Fri, 14 Jun 2002, David Poehlman wrote: > I beg your pardon, page break info can be maintained in html. There are > several ways to do it two of them being to put each page on a page and > to separate each page with anchor text. > > ----- Original Message ----- > From: "John J. Boyer" <director@chpi.org> > To: <blinux-list@redhat.com> > Sent: Friday, June 14, 2002 1:08 PM > Subject: Re: Book Share and Linux > > > Hello, > Alison's response sounds good to me. Since I run a transcription > operation that produces math and science books in Braille, I am keenly > aware of the importance of preserving page breaks. > I hope AFS from maplefish will be adequate for editing rtf. I've been so > busy following this thread that I haven't tried it yet. > John > On Fri, 14 Jun > 2002, Janina Sajka wrote: > > > I have forwarded some of the mail on this thread to Book Share. I > > am now forwarding the response I received to this list, because I > > think it both instructive and responsive to the needs of Linux > > users: > > > > NOTE: I've edited out some personal points in the message I > > received. > > >From Alison@benetech.org Fri Jun 14 12:36:51 2002 > > From: Alison Lingane <Alison@benetech.org> > > Thanks so much for passing along the posts to us - we're glad to know > what > > people's concerns are. > > > > HTML was definitely considered when we chose one format, but the > drawback it > > has is that it loses page break information if it is in the original > file. > > This is important to maintain in books, especially for students who > have > > assignments based on page numbers. > > > > To explain to you in a little more detail, the book conversion process > goes > > like this: > > > > 1. Volunteer submits a file in any format > > 2. Another volunteer (or staff) converts the file to RTF. We chose > RTF > > because it keeps as much markup information as possible, but isn't a > > proprietary format, and most programs have a "save as RTF". Knowing > the > > answer to John's post of what files can be used with Linux to > accomplish > > this would be helpful. Volunteers can also re-submit as ASCII, but > this > > loses any markup present in the book. (If the book was submitted in > ASCII, > > we try to have it resubmitted in ASCII so false markup isn't added.) > > 3. Our software converts RTF to the XML content file of the DAISY > standard. > > 4. Our automated software tools run on this XML file - quality > assessment, > > OCR correct, etc. > > 5. Our tools then convert this XML file to DAISY, BRF (actually, we > use > > Duxbury for this), and in the case of public domain books, HTML and > ASCII. > > > > Hopefully this explains things a little more, but I'm happy to answer > other > > questions! > > > > Alison > > > > > > > > > > -- > Computers to Help People, Inc. > http://www.chpi.org > 825 East Johnson; Madison, WI 53703 > > > > > _______________________________________________ > > Blinux-list@redhat.com > https://listman.redhat.com/mailman/listinfo/blinux-list > > > > _______________________________________________ > > Blinux-list@redhat.com > https://listman.redhat.com/mailman/listinfo/blinux-list > -- Computers to Help People, Inc. http://www.chpi.org 825 East Johnson; Madison, WI 53703 _______________________________________________ Blinux-list@redhat.com https://listman.redhat.com/mailman/listinfo/blinux-list