public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: "Speakup is a screen review system for Linux."
	<speakup@linux-speakup.org>
Subject: Re: eSpeakup Source Tarball
Date: Wed, 31 Aug 2016 15:48:41 -0700	[thread overview]
Message-ID: <87lgzctv06.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20160831.204105.450.24@[192.168.1.117]> (Rob's message of "Wed\, 31 Aug 2016 15\:41\:05 -0500")

"Rob" <captinlogic@gmail.com> writes:

> I found a download link for the old eSpeak on sourceforge. I am not
> using espeak-ng, because it is only available on github and you need
> their client to clone repositories.

Not quite.  You can use HTTP to get tarballs.  For instance, this link
will get the current master branch for espeak-ng:
https://github.com/espeak-ng/espeak-ng/archive/master.tar.bz2
And you can also get released versions.  Just replace master with the tag.
That being said, you cannot use espeak-ng with espeakup right now,
because of a bug that causes espeak-ng to crash if espeak_Cancel() is called
before any text has been synthesized.
Here's a link to my pull request to fix that:
https://github.com/espeak-ng/espeak-ng/pull/143
All that being said, espeak-ng looks to have a very bright future.

> So is there a tarball somewhere for eSpeakup that I can just use a wget command for?

Sure.  espeakup is on GitHub, and here's the link for downloading the
most recently released version, 0.80:
https://github.com/williamh/espeakup/archive/v0.80.tar.gz

PS.  One of you Arch Linux people should flag espeakup as out of date and
give them this new download URL for 0.80.

-- Chris

      reply	other threads:[~ UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Rob
 ` Chris Brannon [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=87lgzctv06.fsf@mushroom.localdomain \
    --to=chris@the-brannons.com \
    --cc=speakup@linux-speakup.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).