From: ccrawford@acb.org
To: speakup@braille.uwo.ca
Subject: Re: Gnome, gnopernicus, and X-Windows questions
Date: Tue, 17 Sep 2002 07:00:26 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0209170653050.3858-100000@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.33.0209161740380.14508-100000@localhost.localdomain>
It really rips me that we spend millions of dollars in government
to accomplish accessibility with esoteric and stupid projects that do
little more than create jobs for people who just love to process stuff,
while hard core progress could have been made with the FUI and access in
Linux. Why should we have to do all that installing and compiling to
simply get x-windows to talk right? I surely do appreciate the great
volunteer work that has been done to get the hooks in a development kit,
but it just drives me up a wall to think that we could have funded good
work and gotten it done much more quickly.
You all should know that I am telling folks in the funding world
that we simply have to pay reall attention to development rather than
another conference or train the damn trainer program. If we just bought
the package and had the access in the box, then how much money would we
not have to spend on another conference on how come we are not working?
OK, off the soap box but really; Speakup for example is a great
contribution to our lives and how come we are not getting the funding it
needs as well as other products? That hhas to change and while it may
take a little time, it will.
-- charlie Crawford.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020916195815.6860.27057.Mailman@speech.braille.uwo.ca>
` Thomas D. Ward
` ccrawford [this message]
` Ann Parsons
` Monty Lilburn
[not found] <20020917225302.15062.7560.Mailman@speech.braille.uwo.ca>
` Thomas Ward
` Steve Holmes
` Charles Crawford
` ccrawford
` Thomas Ward
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.44.0209170653050.3858-100000@localhost.localdomain \
--to=ccrawford@acb.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).