From: Uday S Reddy <u.s.reddy@cs.bham.ac.uk>
To: help-gnu-emacs@gnu.org
Subject: Re: Can emacsspeak receive voice orders?
Date: Wed, 19 May 2010 22:11:45 +0100 [thread overview]
Message-ID: <ht1k71$rds$1@dough.gmane.org> (raw)
In-Reply-To: <20100518065413.GA32310@tomas>
On 5/18/2010 7:54 AM, tomas@tuxteam.de wrote:
>
> Thanks for clarification. The following links might be of interest
> regarding speech recognition proper:
>
> <http://en.wikipedia.org/wiki/Speech_recognition>
> -- a good oveerview about what's the state of the art
>
> <http://www.tldp.org/HOWTO/Speech-Recognition-HOWTO/software.html>
> -- a list of Free and non-Free software packages
>
And this one for voice commands
http://vocola.net/
Cheers,
Uday
next prev parent reply other threads:[~2010-05-19 21:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 14:13 Can emacsspeak receive voice orders? filebat Mark
2010-05-13 16:12 ` tomas
2010-05-13 16:13 ` filebat Mark
2010-05-14 8:23 ` tomas
2010-05-18 3:16 ` Jason White
2010-05-18 6:54 ` tomas
2010-05-19 21:11 ` Uday S Reddy [this message]
[not found] <mailman.3.1273760027.6488.help-gnu-emacs@gnu.org>
2010-05-13 22:36 ` Tim X
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ht1k71$rds$1@dough.gmane.org' \
--to=u.s.reddy@cs.bham.ac.uk \
--cc=help-gnu-emacs@gnu.org \
/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).