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: 0.27 uploaded (fwd)
Date: Sun, 13 Oct 1996 23:06:53 +0200 (MET DST)	[thread overview]
Message-ID: <Pine.LNX.3.94.961013225331.1907D-100000@goldfish.cube.net> (raw)

Ears package can be found at:

sunsite.unc.edu/pub/Linux/Incoming
(will go later to sunsite.unc.edu/pub/Linux/app/sound/speech/)
vr-ftp.eng.cam.ac.uk /pub/comp.speech/binaries
and at just uploading to leb.net/incoming/blinux
(will go later to leb.net/pub/blinux)

Enjoy!
Hans

---------- Forwarded message ----------
Return-Path: <owner-ears-list@phil.uni-sb.de>
Delivered-To: zocki@GOLDFISH.cube.net
Date:	Thu, 10 Oct 1996 15:56:14 +0100 (MET)
From:	"Ralf W. Stephan" <ralf@ark.franken.de>
X-Sender: ralf@localhost
To:	ears-list@phil.uni-sb.de
Subject: EARS: 0.27 uploaded
Sender: owner-ears-list@phil.uni-sb.de
Reply-To: ears-list@phil.uni-sb.de

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

Version 0.27 is out with minor bug fixes:

- bug: linking order of ncurses libs was wrong
- bug: String::capitalize() and its usage was Broken As Designed
- bug: when UINcurses::infow_fill()ing, we didn't pad with spaces
- util/makesysdefs: we check for existence of libg++-2.7.1.4 function.h
- enhanced ui/win_reg.h logic, new windows take now empty slots
- fixed most -Wall warnings

It now will take some time for 0.30 to appear.  Don't hold your breath.
It won't be this year.


Thanks for your time,
ralf
------
End of mail from "Ralf W. Stephan" <ralf@ark.franken.de>


             reply	other threads:[~ UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Hans Zoebelein [this message]
 ` EARS: 0.27 available from leb.net/pub/blinux BLINUX Documentation and Development Project

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.961013225331.1907D-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).