public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Dave Mielke <dave@mielke.cc>
To: <blinux-list@redhat.com>
Subject: Re: braille output hardware (jf)(long post)
Date: Sat, 9 Mar 2002 08:06:15 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.30.0203090745220.24680-100000@dave.private.mielke.cc> (raw)
In-Reply-To: <3C89EDF9.87FA6AF2@dynolink.org>

[quoted lines by emc.er on March 9, 2002, at 05:11]

Here are answers to some of your questions.

>1. Is a keyboard with scrolling braille 'home' keys available anywhere
>today?

Not that I'm aware of.

>2. Will speech output displace the braille tty completely?

No. Each has its advantages and disadvantages. Deaf-blind people cannot use
speech. Braille provides random access whereas speech provides sequential
access.

>2a. Is braille reading speed faster than listening to audio?

Yes for some, and no for some. The one big advantage of braille insofar as
speed is concerned is the ability to jump to any place on the screen at will.

>3. Do all braille tty's cost many many thousands of dollars?

Yes (almost). There's an eight-cell display made by Handy Tech Elektronik
(Germany), brand-named the Bookworm, which isn't too expensive. There's also a
prototype display made by NIST (National Institute for Standards in
Technology), a division of the US government, which, if manufactured, should be
fairly cheap; you can check it out at:

    http://www.itl.nist.gov/div895/isis/projects/brailleproject.html

>3a. If they were one tenth the cost would they become more prolific?

Yes, if sufficiently functional.

>5b.  Is it easier or necessary to use 2 or more fingers to read???

Braille can be read with one finger, but it's more reliably read with two. Each
can spare the other during moments of fatigue, the extra redundancy increases
error correction, and no time is wasted when ending one line and starting the
next.

>6. Do the graphic output grids work? There is a 64 by 64? grid for sale.

They're useful when non-text is encountered, but braille is much easier to read
than print. A graphic display would be most useful if it were able to
automatically (with an override) switch to braille when on text.

>7. Is there any braille tty that even scrolls the characters past your
>fingers?

See above regarding the NIST prototype. It uses a rotating wheel with several
braille cells around its perimeter. The top half (roughly) is exposed for
reading, and there's a single pin-repositioning mechanism at the bottom.

-- 
Dave Mielke           | 2213 Fox Crescent | I believe that the Bible is the
Phone: 1-613-726-0014 | Ottawa, Ontario   | Word of God. Please contact me
EMail: dave@mielke.cc | Canada  K2A 1H7   | if you're concerned about Hell.
http://familyradio.com




  reply	other threads:[~ UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 emc.er
 ` Dave Mielke [this message]
   ` Jonathan Chetwynd
     [not found] ` <Pine.LNX.4.30.0203090745220.24680-100000@dave.private.miel ke.cc>
   ` Brent Harding
 ` Monty Lilburn

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.30.0203090745220.24680-100000@dave.private.mielke.cc \
    --to=dave@mielke.cc \
    --cc=blinux-list@redhat.com \
    /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).