Re: [orca-list] punctuation pronunciation and pauses



-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

I'm a recent commer to this whole situation with Orca and was lead to
believe by others that Speech Dispatcher was supposedly the way of the
future and gnome-speech was not going forward.  Maybe I mis-understood
or something.  But one thing I did hear was that gnome-speech was
OSS.  What if we want to use ALSA and want to take advantage of ALSA's
multi chanel support? I thought OSS was obsolete now since the 2.6
kernel uses ALSA by default now.  I'm considering getting gnome-speech
going to see if it works better with Cepstral but if it is restricted
to OSS and single chanel operation, then I'm not interested.

If gnome-speech is the official line and speech dispatcher is *NOT*
"supported", then why doesn't gnome-speech get up to the more current
ALSA implementation?  What synths does gnome-speech work with? I'm
using espeak currently.

On Fri, Apr 04, 2008 at 11:10:57PM +0200, Peter VÃgner wrote:
Hello,

Willie Walker  wrote:
I believe this took place in
http://bugzilla.gnome.org/show_bug.cgi?id=520494#c33. If there's
something wrong, please let me know.

yes thanks this is great at least It does things as suggested in that 
bug report.
Thanks again for the efforts.

By the way, I need to repeat that THE CURRENT SPEECH DISPATCHER
IMPLEMENTATION IN ORCA IS NOT SUPPORTED. If you have problems with
speech output, please first use the currently supported solution,
gnome-speech.

Does it mean we should understand speech-dispatcher backend as 3rd party 
solution which is not going to be supported by the core team in the near 
future?
I know this has already been discussed but I am getting confused now so 
I'd like to ensure.

In any case...

I've explained that the design choice made early on in Orca was to solve
the 'missing synth feature' problem at the Orca level. I've also
admitted this was not the optimal solution and that we should work to
better understand this problem from the end user point of view. If I
have not said it clearly, let me state it now: I'm open to discussing
viable working solutions that offer a clear improvement, which address
the user requirements, and which run on all the platforms that Orca runs
on.

Yes this is what everyone wishes. Unfortunatelly it looks as in this 
discussion It's happening quite frequently someone might missunderstand.
Attempts to explain speech-dispatcher model has been made several times 
I believe with a few tips and questions whether gnome-speech and orca 
are able to adapt some of the key ideas.
Currently when the bug mentioned abouve is near to fixed. The only known 
difference from the users perspective is is that with gnome-speech 
character and punctuation processing is happening in gnome-speech 
backend and with speech-dispatcher this is not happening.

In my prewious posting I was not tallking about the implementation 
it-self. Really the offered solutions are not complete as I feel it 
those are just some concepts or so. The thing I am interested in is how 
much you and others can agree with that and where does it fail according 
to your experience etc.
I believe it would be nice to go into more details if possible.

The thing is final decision must be done within the Orca team I think. 
So it's why I am so curious.

oh finally let me thank also for this discussion. I feel such a skilled 
accessibility developer than you are is not going to waste the time 
talking with someone like I am. This really shows you are ready for 
cooperation if you feel it may lead to an improvement.

It is very likelly possible that it's me who don't understand the 
situation good enough so if you feel I should not continue in this thing 
I'll respect that as well.

thanks

Peter
_______________________________________________
Orca-list mailing list
Orca-list gnome org
http://mail.gnome.org/mailman/listinfo/orca-list
Visit http://live.gnome.org/Orca for more information on Orca

- -- 
HolmesGrown Solutions
The best solutions for the best price!
http://holmesgrown.ld.net/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFH9qPAWSjv55S0LfERAyJ0AKDH/dza6rDcmmmefAVQ3osPEJK3IACfWXkR
BKKbqNKJRJ9/lVGKrNsov2w=
=l+2n
-----END PGP SIGNATURE-----



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]