Re: [arch-general] BrlTTY Hard Dependency on eSpeak
Hi,
Yes discovered this the other day. I think it is time to make espeak
deprecated imo and have espeak-ng the default particularly in the talking
arch which someone is taking over development of.
Thanks.
Matthew
-----Original Message-----
From: arch-general
hello. to switch TalkingArch to espeak-ng we need that espeakup works with espeak-ng.. maybe a espeak-ng maintainer knows how to do it.
As mentioned earlier in this thread, upstream (espeakup, etc.) has to be engaged: https://lists.archlinux.org/pipermail/arch-general/2019-February/046055.html -- Best, polyzen
On February 16, 2019 2:32:43 AM EST, "Daniel M. Capella"
As mentioned earlier in this thread, upstream (espeakup, etc.) has to be engaged: https://lists.archlinux.org/pipermail/arch-general/2019-February/046055.html
-- Best, polyzen
Note that we could patch around this, but upstream support would be best. -- Best, polyzen
Am 16.02.19 um 08:39 schrieb Daniel M. Capella via arch-general:
On February 16, 2019 2:32:43 AM EST, "Daniel M. Capella"
wrote: As mentioned earlier in this thread, upstream (espeakup, etc.) has to be engaged: https://lists.archlinux.org/pipermail/arch-general/2019-February/046055.html
-- Best, polyzen
Note that we could patch around this, but upstream support would be best.
-- Best, polyzen
Hello, What is it that upstream should do? As far as I can see, brltty already supports dynamic loading of speech plugins. (see e.g. the --speech-driver paramter) The only problem seems to be that espeak-ng includes some compatibility files that conflict with the espeak package and prevent parallel installation. Wouldn't it be sufficient to split those two files into an espeak-ng-compat package? usr/bin/espeak usr/include/espeak/speak_lib.h -- progandy
As already stated, may you just wait until it's rules out, problems with other packages fixed, rebuild and replaced? Thanks
participants (5)
-
Alexandr Epaneshnikov
-
Daniel M. Capella
-
ilovecountrymusic483@gmail.com
-
Levente Polyak
-
ProgAndy