[ossrp-control] Re: TTS engines that use the SAPI interface

Hi,

I'm new to this list and relatively new to the VI area. A student I work with pointed me in the direction of

http://www.speegle.co.uk/

What are the general opinions on this ?

NB. No axe to grind here - just want some objective views.

Regards

Robert


http://www.speegle.co.uk/

Darrell Shandrow wrote:

Hi Richard,
Yeah. If you want something from Google, then you'd better get it right now! Who knows? Maybe tomorrow we'll all wake up only to find they've implemented yet another inaccessible CAPTCHA (visual verification) just for doing simple searches! Google has shown its contempt for the blind by simply failing to provide any accessible alternatives, more coverage at http://www.blindaccessjournal.com on the issue.


    ----- Original Message -----
    *From:* Richard Thomas <mailto:rthomas@xxxxxxxxxxx>
    *To:* ossrp-control@xxxxxxxxxxxxx
    <mailto:ossrp-control@xxxxxxxxxxxxx>
    *Sent:* Thursday, April 28, 2005 5:09 PM
    *Subject:* [ossrp-control] TTS engines that use the SAPI interface

Sorry for the last post;
But, does anyone have a good book or article on the TTS engines
that use the SAPI interface?
I'm off to google to accumulate what I can find there and store
the results in a file here on my home pc. Anyone can have
whatever I find by just posting a request.
Rick of Farmington Mich. USA
Rick of Farmington Mich. USA
----- Original Message -----

        *From:* Will Pearson <mailto:will-pearson@xxxxxxxxxxxxx>
        *To:* ossrp-control@xxxxxxxxxxxxx
        <mailto:ossrp-control@xxxxxxxxxxxxx>
        *Sent:* Wednesday, April 27, 2005 3:02 PM
        *Subject:* [ossrp-control] Features So Far

Hi,
Here's my understanding of the important features that should
be investigated for version 1. It doesn't feature everything,
but then there'll be versions after 1 in which more things can
be brought in.
Functional requirements:
* ability to read *windows* login screen
* ability to work with widely used types of applications, e.g.
word processors, spreadsheets
* support for TTS engines that use the SAPI interface, as some
of these provide clearer speech than current formant synthesisers
* ability to use mouse or equivalent functionality
* must work with User Interface Automation
* ability to update components over the web
* support for Braille devices
Architectural requirements:
* based on .Net Framework/WinFX
* component based architecture
* Research requirements
* investigate mechanisms to provide more efficient interaction
mechanics
* investigate techniques to convey all the semantic
information contained within a GUI through auditory and
tactual/haptech transmission media.
* investigate means for clearer speech
* investigate perceptual psychology techniques for semantic
conversion of web based graphical turing tests to text
Project management requirements:
* risk analysis
* avoid scope creep
* requirements management
* beta 1 to be made publically available April 2006
These are fairly high level requirements, and if anyone feels
anything is being missed or would like to include anything,
then say now.
Will

To post to the list, send a message to:
ossrp-control@xxxxxxxxxxxxx
To unsubscribe, send a message to:
ossrp-control-request@xxxxxxxxxxxxx
and set the subject field of the message to "unsubscribe" (without the quotes

Other related posts: