From: Frank Carmickle <frankiec@braille.uwo.ca>
To: speakup@braille.uwo.ca
Cc: Ari Johnson <ari@lusis.org>
Subject: Re: suggested changes to 1.4.1
Date: Sun, 8 Jul 2001 07:20:09 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0107080709311.3932-100000@localhost> (raw)
In-Reply-To: <Pine.LNX.4.21.0107080657150.287-100000@hudson.mhonline.net>
Hi Ari Chuck and all
I don't think that a separate development tree is required for something
like this. Generally what people find when doing development that
includes the needs of blind users is that everyone benefits. I have only
tried version 1.9. I did find it quite difficult to use. I think with a
bit of tweaking it could be quite user friendly.
On Sun, 8 Jul 2001, Charles Hallenbeck wrote:
> <smile> I personally do not have a problem with the name, but do not be
> surprised if some do. The Linux Gazette has a link for downloading an
> entire issue which is called "twdt" for "the whole damn thing" and they
> get flak for that!
>
> I am nervous about a special version for the blind though. My nervousness
> is related to the fallacy that separate is equal. In the past there have
> been special versions of word processors, of spread sheets, of comm
> programs, etcetera, all based on the theory that they could be fine tuned
> and maximized for a special population, and in each case they have
> stagnated while their mainstream counterparts continued on a course of
> development.
--
Frank Carmickle
phone: 412 761-9568
email: frankiec@dryrose.com
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0107080144460.13636-100000@godspeed.lusis.org>
` Charles Hallenbeck
` Frank Carmickle [this message]
[not found] <Pine.LNX.4.21.0107071656190.12469-100000@godspeed.lusis.org>
` Charles Hallenbeck
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.0107080709311.3932-100000@localhost \
--to=frankiec@braille.uwo.ca \
--cc=ari@lusis.org \
--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).