From: Jack Johnson <fragment@nas.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Proposed Aid for the nearly blind
Date: Thu, 29 Jan 2004 21:18:17 -0800 [thread overview]
Message-ID: <B602EFD5-52E3-11D8-93E2-000A95E29604@nas.com> (raw)
In-Reply-To: <Df6dnV5H1abbqIXdRVn-sQ@comcast.com>
I've always thought it would be rewarding to write software for the
blind.
Part of it is the challenge. Talk about a shift in thinking for user
interface (what the hell do you do with a mouse?). The other is
pondering what would actually be useful, and how I might (or might not)
adapt if it were ever to happen to me.
Knock on wood.
-Jack
On Jan 29, 2004, at 2:45 AM, Douglas A. Gwyn wrote:
> Donald Brownlee wrote:
>> They use software that converts text to speech.
>
> At Geotronics we had a blind programmer and tried out
> many of the available aids, including text-to-speech.
> It wasn't very useful when applied to C source text!
> There is also a fingertip pin array that tracks a
> scanner, allowing the operator to "feel" contrasty
> shapes. That was useful for examining plots but not
> very good for text.
> The best text aid we found was a VersaBraille
> terminal, which had a ticker-tape-like scrolling
> Braille display and chording Braille keyboard. It
> was very handy that the Unix terminal driver had
> decent support for monocase devices (think Teletype
> model 33), flagging uppercase output with \ prefix.
next prev parent reply other threads:[~2004-01-30 5:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 20:35 west9
2004-01-28 22:04 ` Donald Brownlee
2004-01-29 0:41 ` [9fans] " Jim Choate
2004-01-29 0:52 ` boyd, rounin
2004-01-29 10:45 ` [9fans] " Douglas A. Gwyn
2004-01-29 13:05 ` Martin C.Atkins
2004-01-29 18:03 ` Douglas A. Gwyn
2004-01-29 18:42 ` Jim Choate
2004-01-29 22:51 ` Michael H. Collins
2004-01-30 15:25 ` Jim Choate
2004-01-30 15:46 ` Michael H. Collins
2004-01-30 1:52 ` boyd, rounin
2004-01-29 14:57 ` Jim Choate
2004-01-29 17:49 ` Douglas A. Gwyn
2004-01-29 18:40 ` Jim Choate
2004-01-30 10:03 ` Douglas A. Gwyn
2004-01-30 5:18 ` Jack Johnson [this message]
2004-01-29 0:14 ` boyd, rounin
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=B602EFD5-52E3-11D8-93E2-000A95E29604@nas.com \
--to=fragment@nas.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).