You are not logged in.
Hope I'm not out of place posting this here
.
I just want to take note of KDE Bug 236457, in which Jovie does not recognise talkers provided by MBROLA (and thus you can't use them), for the benefit of anyone else experiencing the same issue (or does so into the future).
I'm not the one who reported the upstream, but can confirm the same symptoms locally under the current versions of the packages available from Arch repositories (kdeaccessibility-jovie 4.9.5-1, speech-dispatcher 0.7.1-7 and espeak 1.46.02-2 in Official, and mbrola 3.0.1h-4 in AUR) on x86_64 (which may be important as the MBROLA package depends upon lib32-glibc). There is no corresponding bug in the Arch tracker (the Bug Reporting Guidelines are conflicted on the point of whether or not to duplicate matters already reported upstream).
There isn't any stated workaround thusfar; when I get a moment I'll have a further look and see if a workaround is possible (noting that I'm not all that experienced at this!). Should someone beat me to it though, please feel free to jump in to this thread
.
p.s. This may or may not be related -- it depends how Jovie determines what voices are available -- but there is a similar upstream bug reported recently as affecting eSpeak GUI (available from AUR: espeak-gui 0.4-2). I haven't investigated this yet (pending the aforementioned "when I get a moment").
Last edited by aexoxea (2013-02-02 04:59:45)
Offline
Don't duplicate upstream bugs on the Arch tracker. Well maybe if you knew a suitable workaround it would be appropriate. You could find one and then write something like:
"I think we should modify the kdeaccessibility-jovie package in <this> way in order to get around an upstream bug. I have let the upstream developers know and they do not want to do <this> to their upstream package, but it would still benefit Arch."
6EA3 F3F3 B908 2632 A9CB E931 D53A 0445 B47A 0DAB
Great things come in tar.xz packages.
Offline
Don't duplicate upstream bugs on the Arch tracker. Well maybe if you knew a suitable workaround it would be appropriate. ...
Thank you for clarifying that; I will refrain from adding anything to tracker unless such a situation arises (though hopefully it won't come to that!)
Offline