From: Monty Lilburn <monty@bc.cx>
To: <blinux-list@redhat.com>
Subject: Re: braille output hardware (jf)(long post)
Date: Wed, 13 Mar 2002 15:36:03 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.30.0203131526210.28120-100000@millennium.bc.cx> (raw)
In-Reply-To: <3C89EDF9.87FA6AF2@dynolink.org>
Hi Jan and list,
I have recently wrapped up my involvement with a project investigating
the usefulness of refreshable braille. The study took place over a 1.5
year period and examined several aspects of Braille displays and how they
are used. Though Linux wasn't a particular focus of this study, the final
report may encourage the use of refreshable Braille displays within the
Linux community.
The project URL is: http://www.bc.cx/brl-net
Monty
--------------------------------------------------------------
SUBMERGED IN THE 6o4 AREA CODE
A proud user of the LINUX Operating System!
----------------------------------------------------------------------
prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
emc.er
` Dave Mielke
` Jonathan Chetwynd
[not found] ` <Pine.LNX.4.30.0203090745220.24680-100000@dave.private.miel ke.cc>
` Brent Harding
` Monty Lilburn [this message]
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.0203131526210.28120-100000@millennium.bc.cx \
--to=monty@bc.cx \
--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).