From: craig martin <clmartin@kc.rr.com>
To: Greg Keto <gorgotek@gte.net>
Cc: cpt.kirk@1tree.net, speakup@braille.uwo.ca
Subject: Re: PDA's
Date: Sun, 12 Mar 2000 14:45:46 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.21.0003121442170.1248-100000@wa0wpj> (raw)
In-Reply-To: <38C9E43A.D79E0065@gte.net>
the only problem with speech input is noise and memory
requirements. Speech output was done on the Comodore 64 and amega series
back in the early ninties. so we just have to solve the resource problem
on speech input. C would lend itself to this since it works on Linux, and
the speaker and microphone are treated as files like any other device in
the /dev directory.
prev parent reply other threads:[~ UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
PDA's Buddy Brannan
` PDA's cpt.kirk
` PDA's Buddy Brannan
` PDA's cpt.kirk
` PDA's Kirk Reiser
` PDA's cpt.kirk
` PDA's Geoff Shang
` PDA's craig martin
` PDA's Greg Keto
` PDA's Kirk Reiser
` PDA's Greg Keto
` PDA's Kirk Reiser
` PDA's cpt.kirk
` PDA's Greg Keto
` craig martin [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.21.0003121442170.1248-100000@wa0wpj \
--to=clmartin@kc.rr.com \
--cc=cpt.kirk@1tree.net \
--cc=gorgotek@gte.net \
--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).