Hi Chris:
There's no good solution to the "share a dock area" problem. We
recommend that you don't use both top and bottom panels when running an
onscreen keyboard, for this reason.
The straightforward solution is to remove either the top or bottom
panel, and then use that edge to dock your keyb
SOK is simple onscreen keyboard I am writing to compliment GOK. It is
a summer of code project.
I've been trying to implement a dock window mode for SOK like that
which GOK has.
Unfortunately my effort was met with a plethora of problems.
Support for such docked windows is unpredictable under
Greetings,
After a bit of a delay, audio recordings of the two Orca sessions and
the ODF Accessibility Panel are now available, for your listening
pleasure. We have them up in Ogg Vorbis format (of course). Please see
http://blogs.sun.com/roller/page/korn/20060628 for details, links, etc
Hi Hynek, All:
I'm not sure I agree that speech engines should not do their own audio
output. While I think you have identified some real problems with that
approach, it's not clear that the ".wav file" approach has a low enough
latency. If tests show that latency is not a problem, then passing
> Festival is free software, so this is of course fixable. Having looked
> at the code, it's simple code and it wouldn't break if it'd be stretched
> a bit. But that's not improving a driver: that's improving festival (if
> the authors allow) and then having to depend on a very new version of
> i
Hello,
might be around here:
$ echo "Evviva il Perú" | festival --tts --language english
$ echo "Evviva il Perú" | festival --tts --language finnish
SIOD ERROR: damaged env : #
$ echo "Evviva il Perú" | festival --tts --language spanish
$ echo "Evviva il Perú" | festival --tts --language italian
On Tue, Jun 27, 2006 at 05:04:37PM +0200, Hynek Hanke wrote:
> * Enrico suggested we should use Festival C API instead of talking
> to it via TCP. Also Olivier mentioned the whole chain to be too long and
> source of troubles. However, I suspect the problem is not in the chain
> being too long as
On Tue, 2006-06-27 at 21:34 +0200, Hynek Hanke wrote:
> The modules inside the TTS
> API implementation we are working on are supposed to run as separate
> processes for licensing reason and for the reason of stability.
You answered my malformed question. :-) Thanks.
George (gk4)
George Kraft píše v Út 27. 06. 2006 v 13:26 -0500:
> On Tue, 2006-06-27 at 17:04 +0200, Hynek Hanke wrote:
> > talking to it via TCP.
> Are commercial TTS engines sufficiently isolated in this new TTS API
> proposal? With respect to licensing, can DECtalk and TTSynth be
> successfully linked to an
