From: "Victor Tsaran" <vtsaran@nimbus.ocis.temple.edu>
To: <speakup@braille.uwo.ca>
Subject: Re: A comment on Slashdot that concerns me
Date: Fri, 24 Mar 2000 14:01:56 -0500 [thread overview]
Message-ID: <001101bf95c3$6ce56ec0$beeef79b@default> (raw)
In-Reply-To: <14555.47231.32921.800996@crosswinds.net>
HI, Mat!
I cannot hold my anger inside. You haven't done anything wrong and, vice
versa, we all are grateful to you for your gracious offer. Even though I
myself gave up on UMSDOS-based Linux, due to the inferiority of UMSDOS file
system, I very much value and praise people who put their own time in order to
make life easier for others.
I think we should post our strong oposition to what this guy said. He
mentioned something about Aple. Everyone knows that Aple has done nothing to
make their operating system accessible to the blind.
Terrible to know that such people, like the author of that message, exist.
WHere was this posted?
Regards,
Victor
----- Original Message -----
From: "Matthew Campbell" <mattcamp@crosswinds.net>
To: <speakup@braille.uwo.ca>
Sent: Friday, March 24, 2000 1:48 PM
Subject: A comment on Slashdot that concerns me
| Here is one comment that was posted on Slashdot regarding ZipSpeak and
| probably Speakup in general:
|
| (begin quote)
|
| This is nothing but a threat to independent producers, and
| "slashdot"'s unquestioning boosting of a LinusX technology in this
| specialised and delicate market is inappropriate. Although the goal of
| having universal access to LinusX is laudable, that is not what this
| product offers. Rather, it offers access for the blind so long as they
| buy a speech synthesiser which is on the approved list. Those of us
| who make speech syntehsisers which didn't make it onto this hallowed
| team end up losing a whole chunk of our market because, even though
| our synthesisers offer a lot of important functionality for the blind
| ("easy listening" modulated voices, automatic timbre management,
| etc.), we didn't promote our product at the right time to the right
| developer.
|
| This product is particularly cruel as it locks in people forever to an
| inferior technology, by exploting the fact that they need speech
| synthesis if they are to run Linux at all. Zipspeak should be forced
| to provide support for all speech synthesiser by writing the
| appropriate drivers, and should forfeit their FDA approval and the
| tax-deductibility of their product if they continue to tilt the
| playing field for synthesisers. It is wholly irresponsible of them to
| come into an orderly marketplace and shake things up like this. We
| never had these problems with Apple (a company which, IMO, really
| "gets it" with regard to open standards) and only a few with
| Microsoft. What a shame that the so-called "altruists" of the LinusX
| community couldn't be a bit more understanding.
|
| Stephen Mundy
|
| --Murrinco
|
| (end quote)
|
| What have we done wrong? Or what have I done wrong? Should I have
| delayed my release of ZipSpeak until there were drivers for all known
| synthesizers? Or should I have spent my spring break writing
| synthesizer drivers? I probably couldn't anyway, because I know
| little about kernel programming and don't have any documentation for
| synthesizers other than the DoubleTalk (though I could have learned
| some from Emacspeak driver code). Perhaps I should release an updated
| ZipSpeak with the new drivers which are on the Speakup FTP site, even
| though they're not yet in the official Speakup release. But I figured
| that since they're not in the official Speakup release, they probably
| aren't ready for general use yet.
|
| I really didn't mean any harm to the makers of unsupported speech
| synthesizers, but I guess this person doesn't think so. What do you
| all think?
|
| --
| Matt Campbell <mattcamp@crosswinds.net>
| Web site: http://www.crosswinds.net/~mattcamp/
| ICQ #: 33005941
|
|
| _______________________________________________
| Speakup mailing list
| Speakup@braille.uwo.ca
| http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
Matthew Campbell
` cpt.kirk
` Victor Tsaran [this message]
` Mike Gorse
` cpt.kirk
` cpt.kirk
` Tommy Moore
` Victor Tsaran
` Kirk Reiser
` cpt.kirk
` Victor Tsaran
` Janina Sajka
` Dave Talmage
` kestrell
` Brian Borowski
` Ron Kassen
` Peter Persuric
Martin G. McCormick
` Tommy Moore
Martin G. McCormick
` Tommy Moore
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='001101bf95c3$6ce56ec0$beeef79b@default' \
--to=vtsaran@nimbus.ocis.temple.edu \
--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).