public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Kirk Wood <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: Re: What I did on my summer holidays.
Date: Sun, 27 Jan 2002 22:11:21 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.21.0201272159550.12020-100000@lbear> (raw)
In-Reply-To: <Pine.LNX.4.44.0201272201390.1679-100000@toccata.dsl092-170-083.wdc1.dsl.speakeasy.net>

On Sun, 27 Jan 2002, Janina Sajka wrote:
> Part of the problem is that creating braille or tape versions is generally 
> a "one-off" done by hand from a printed page. Not very efficient. What 
> we're trying to eingineer with NISO/DAISY, and with our participation in 
> the OEBF, is access to the underlying text in a well-marked-up XML (or 
> SGML). If we can get publishers to:
> 
> 1.)	Use good markup;
> 2.)	Allow us to build a server-based delivery system;

So is there anything to prevent agencies already doing braille translation
from the publisher files to put their work out in DAISY format? Having
helped some with the group that does most of the textbooks for k-12 in
this area, I can tell how they do it. They get the text book in electronic
format. They also get two copies of the book in print and correction
sheets.

They then have sigted people ensure that any corrections from the sheets
are marked in the print versions. They translate the braille from the
electronic version. One of the print books is available to the translator
to ensure that formatting is correct. The other goes to the proof
reader. Then the book is embossed.

Two come to mind here. The first, is that the embossing seems most
wastefull. While expansive, I feel they should move to refreshable
braille. This would allow the student to carry the entire text book as
sigted students do.

The second thing is that I find it bothersome that the same can't be done
in other situations. The small group near me translates well over 100
texts a year. Most of this is done in a matter of 4 months. It astounds
(and saddens) me that given this ability, more books aren't
available. I hope that the DAISY format can perhaps speed this up and
perhaps work toward having most books available to the blind comunity.

=======
Kirk Wood
Cpt.Kirk@1tree.net

Nowlan's Theory:
        He who hesitates is not only lost, but several miles from
        the next freeway exit.




  reply	other threads:[~ UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Kirk Reiser
 ` Janina Sajka
   ` Saqib Shaikh
     ` Thomas Ward
       ` Amanda Lee
     ` Janina Sajka
       ` Kirk Wood [this message]
         ` Geoff Shang
         ` Janina Sajka
           ` Kirk Wood
   ` Victor Tsaran
     ` Geoff Shang
       ` Janina Sajka
         ` Victor Tsaran
           ` Janina Sajka
         ` Geoff Shang
           ` Janina Sajka
             ` Kirk Wood
     ` Janina Sajka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.21.0201272159550.12020-100000@lbear \
    --to=cpt.kirk@1tree.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).