public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Hans Zoebelein <zocki@goldfish.cube.net>
To: blinux-list@goldfish.cube.net
Subject: EARS: ears-0.25 released (fwd)
Date: Fri, 13 Sep 1996 00:00:21 +0200 (MET DST)	[thread overview]
Message-ID: <Pine.LNX.3.94.960912235115.2727B-100000@goldfish.cube.net> (raw)

there is a new version of ears released.
Ears means Easy Automatic Recognition of Speech.

The EARS package is intended as a limited ready-to-use single word
recognizer for Linux systems.  However, its design already aims at
being a host for all kinds of methods used in speech recognition (SR).

You can get it at 
svr-ftp.eng.cam.ac.uk/pub/comp.speech/recognition/
sunsite.unc.edu/pub/Linux/app/sound/speech/      
Look first at the incoming dirs for the new version.

Hans

---------- Forwarded message ----------
Date: Wed, 11 Sep 1996 17:01:32 +0200 (MET DST)
From: "Ralf W. Stephan" <ralf@ark.franken.de>
Reply-To: ears-list@phil.uni-sb.de
To: ears-list@phil.uni-sb.de
Subject: EARS: ears-0.25 released

"Ralf W. Stephan" <ralf@ark.franken.de> in ears-list:

  Hi,

ears-0.25 is out.  From CHANGES:

- bug: "There are new words..." or "Do you want to save..." -> ESC -> left
  train_ears with fatal.  Changed messages::yesno() and words::try_to_load()
- bug: on first startup "Do you want to use the digits..." didn't accept RET
- bug: crash if InfoCfg::helpmap_ < number of config options
- bug: command line options were not handled right (overloaded config::set())

[lots of bug fixes deleted]

- updated README and doc/implementation.txt

Have fun,
ralf
------
End of mail from "Ralf W. Stephan" <ralf@ark.franken.de>


                 reply	other threads:[~ UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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.94.960912235115.2727B-100000@goldfish.cube.net \
    --to=zocki@goldfish.cube.net \
    --cc=blinux-list@goldfish.cube.net \
    /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).