Re: Splitting out the speech-dispatcher flite module into separate package.

2016-12-04 Thread Samuel Thibault
Luke Yelavich, on Mon 21 Nov 2016 08:14:30 +1100, wrote: > On Mon, Nov 21, 2016 at 04:20:38AM AEDT, Samuel Thibault wrote: > > Why not, indeed. We could then put them in speech-dispatcher's > > recommends or suggests as we see fit. I guess we want espeak-ng as > > recommends, and possibly others as

Re: Splitting out the speech-dispatcher flite module into separate package.

2016-11-20 Thread Luke Yelavich
On Mon, Nov 21, 2016 at 04:20:38AM AEDT, Samuel Thibault wrote: > Why not, indeed. We could then put them in speech-dispatcher's > recommends or suggests as we see fit. I guess we want espeak-ng as > recommends, and possibly others as suggests? That sounds perfectly reasonable. I'll take care of i

Re: Splitting out the speech-dispatcher flite module into separate package.

2016-11-20 Thread Samuel Thibault
Hello, Luke Yelavich, on Thu 17 Nov 2016 12:20:31 +1100, wrote: > I am wondering whether we should do the same in Debian. In fact I > wonder whether it makes sense for all modules other than dummy and > generic to be in their own packages, Why not, indeed. We could then put them in speech-dispatc

Splitting out the speech-dispatcher flite module into separate package.

2016-11-16 Thread Luke Yelavich
Hey folks. In Ubuntu we have the flite Speech Dispatcher module split out into a separate package, since at the time it was done, we were trying to shoot for fitting into a CD footprint. This is no longer something we try to do, but so far as I know, espeak supports more languages out of the box