[Kde-accessibility] KDE Speech API Draft 2 and new KTTSD

[Roger Butenuth]

Hello!

On Thu, 20 May 2004, Gary Cramblitt wrote:

> Thank you very much for the feedback!
>
> On Thursday 20 May 2004 12:16 pm, Olaf Jan Schmidt wrote:
>
> > There are mainly three types of usage for speech synthesis:
> >
> > 1. Speaking and navigationg through whole texts (can be interrupted by
> > messages and screen reader speech)
> > 2. Speaking single messages (can be interrupted by screen reader speech)
>
> Why would you want to interrupt a single message with screen reader?

Even a single message may need a second. When you move your cursor to a
new line, you want the screenreader to read the new line immediately, not
after half a second.

> > 3. A screen-reader reading out whatever happens on the screen (can be cut
> > off by new screen reader speech)
>
> If "cut off", is the speaking text re-queued or is it canceled?

In all screenreaders I know "cut off" means canceled (and not requeued).

> >
> > The suggested API is very feature-rich for the first two uses, but the
> > third use is not covered.

In my opinion the API posted by Bil was sufficient. Things like paragraphs
etc. should be handled by higher levels, not the low level speech API.

	Roger