From: Kenneth Albanowski <kjahds@kjahds.com>
To: Steve Holmes <sholmes@primenet.com>
Cc: blinux-list@redhat.com
Subject: Re: another idea for speech
Date: Sat, 28 Dec 1996 23:23:36 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.3.93.961228231947.388B-100000@kjahds.com> (raw)
In-Reply-To: <32c5461d.180075072@mailhost.primenet.com>
On Sat, 28 Dec 1996, Steve Holmes wrote:
> Well, since most of the other solutions are *FREE* for access to
> linux, I really doubt a company like Synthavoice would willingly
> develope a product for Linux. Most access vendors sell their
> DOS/Windows stuff for well over $500 so they would mostlikely charge a
> similar price for their Linux product. Since I'm just playing around
> with Linux here at home, I would not personally be willing to pay such
> a price.
Are there any solutions, are they free, and are they usable? More to the
point, do you _need_ the functions that Synthavoice could provide, and
would Linux be a good platform to work under? If so, $500 doesn't seem
impossible.
I don't see how any encouragement of development for blind access software
can be a bad thing, commercial or not. And the mere existance of
commercial software need not stop the amateurs.
--
Kenneth Albanowski (kjahds@kjahds.com, CIS: 70705,126)
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
Craig Martin
` Kenneth Albanowski
` Jim Rebman
` Sam Hartman
` Kenneth Albanowski
` Steve Holmes
` Kenneth Albanowski [this message]
` Mark Newbold
Lar Kaufman
` Jim Rebman
` Jason John Griffin White
` Craig Martin
` Ken Perry
` Joel Zimba
` Ben Van Poppel
michael malver
Travis Siegel
HRTC
` Travis Siegel
` Brian L. Sellden
` Travis Siegel
` Joel Zimba
` William Loughborough
` Travis Siegel
` Jim Rebman
` Travis Siegel
` Brian L. Sellden
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.3.93.961228231947.388B-100000@kjahds.com \
--to=kjahds@kjahds.com \
--cc=blinux-list@redhat.com \
--cc=sholmes@primenet.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).