[orca-list] [Fwd: Re: [g-a-devel] Speech-dispatcher/orca integration specification, first draft.]
- From: Willie Walker <William Walker Sun COM>
- To: orca-list <orca-list gnome org>
- Subject: [orca-list] [Fwd: Re: [g-a-devel] Speech-dispatcher/orca integration specification, first draft.]
- Date: Sat, 18 Apr 2009 16:01:09 -0400
Hey All:
With the planned removal of CORBA from GNOME 3.0, we need to resolve the
situation with GNOME speech (GNOME speech currently uses CORBA).
Luke Yelavich from Canonical has developed a proposal at
http://www.themuso.id.au/speech/speech-dispatcher-orca-integration.txt
This proposal uses speech dispatcher as a starting point and has
provisions to address a number of considerations for different operating
systems and different operating environments.
I'd appreciate it if you could review this proposal and provide your
constructive feedback. Note that constructive feedback does not include
any of the following:
1) This is dumb.
2) How do I configure speech-dispatcher on Ubuntu?
3) Will Cepstral be coming out with new voices?
4) Which netbook should I buy?
5) I cannot navigate my.favorite.page with Orca. Why?
6) Did OOo come out with a new release yet?
7) etc.
Note that replying to this message with anything like the above may
cause the moderation filtering mechanism I have in place to fire and put
you on moderation. So, do the simple thing and be constructive.
An example of constructive feedback would be "I'm concerned about
feature X. It seems to prevent me from doing Y. As an alternative, I
propose Z."
Thanks!
Will
--- Begin Message ---
- From: Luke Yelavich <themuso ubuntu com>
- To: gnome-accessibility-devel gnome org, Gnome Accessibility List <gnome-accessibility-list gnome org>
- Cc: buchal brailcom org, cerha brailcom org
- Subject: Re: [g-a-devel] Speech-dispatcher/orca integration specification, first draft.
- Date: Thu, 09 Apr 2009 06:06:59 +1000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Re-sending to ensure I sent it to the same addresses as the original.
On Tue, Mar 10, 2009 at 10:55:12PM EST, Luke Yelavich wrote:
I am happy to announce the first draft of a specification document I am writing, which discusses what is
required for speech-dispatcher to be more tightly integrated with orca, and the various kinds of
environments where orca has to be able to function. Just about all the suggested changes in this document
can also be applied to other speech-dispatcher clients in the *NIX accessibility relm, including BrlTTY,
yasr, and speakup, however this document focuses on the requirements for orca.
You can find the first draft of this document here:
http://www.themuso.id.au/speech/speech-dispatcher-orca-integration.txt. Note you will always be able to
find the most current version of the document at this URL, however I will be keeping older versions of the
document at a similar location, as this document is improved. Keeping old versions will allow for looking
back and working out the changes that were made along the way.
Hi all
Sorry I haven't got to this sooner, I've been rather busy helping get Ubuntu Jaunty 9.04 ready. I have made
some slight adjustments to the document referred to at the above URL. Please have a look, and let me know if
things are still not clear enough.
I'd like to point out that this needs to be finalized by the end of April. Exactly when at the end of April
I am not sure, Will can probably fill us in on that.
There are a few things I'd like to make clear, relating to previous discussion in this thread:
* You will still be able to run speech-dispatcher as a system service should you wish to, although its
likely distributions will only configure speech-dispatcher to work as a system service for things like
BrlTTY, speakup, and gdm login.
* You will be able to configure speech-dispatcher to use whatever audio system you want, so if you don't
want pulse, you don't have to have it enabled for speech-dispatcher. One addition that the specification does
address however, is allowing for the falling back to other audio systems in the event the chosen system
fails. So for example, if pulseaudio is requested, but is not available, use alsa, and if not available, use
oss, etc.
* This specification only deals with Orca. The unresolved issues section of the document deals with things
that do need to be resolved for speech-dispatcher to be a good gnome-speech replacement, but these issues are
NOT specific to orca.
* Such issues in the unresolved issues section will be addressed in a separate specification which will go
into detail about the extra work needed to make speech-dispatcher the standard text to speech API for Linux,
and hopefully *NIX.
* sd_generic will not be going away.
Please have a read, and give feedback. I am starting to work on a specification that is Ubuntu specific, to
be discussed at the next Ubuntu Developers summit in May, as this work will have to benefit Ubuntu if my
superiors are to give me the green light to do this work in Canonical's time. This specification needs to be
complete soon, so I need to be able to refer to this specification where necessary. Also note that the work
in question will probably be done in 2 6-month lots, depending on how long the work takes to complete, given
that I also have other Ubuntu related duties.
Thanks, and I look forward to hearing from you.
Luke
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkndA+MACgkQjVefwtBjIM73swCeMU1wZLfJKE06HvFWy6EHmVnA
cR4AniWGWGgFLJTyfmbo2m4osRKFFmoE
=teOv
-----END PGP SIGNATURE-----
_______________________________________________
Gnome-accessibility-devel mailing list
Gnome-accessibility-devel gnome org
http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
--- End Message ---
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]