[Accessibility] qtspeech status

Frederik Gladhorn gladhorn at kde.org
Mon Oct 13 10:41:35 CEST 2014

On Friday, September 26, 2014 06:00:47 PM Jeremy Whiting wrote:
> Hello list,
> I should have sent this a long time ago, but have been putting it off
> in hopes that I would do more homework before sending this out. It
> turns out that homework just never got done either :/. I just found
> that kdepim master branch is depending on qtspeech so I thought I'd
> send this out now and do my homework as I am able, possibly with some
> answers on this thread to help me along.
> My main question is what is needed for qtspeech to get released?
> In looking at the code itself I see some commented out
> structures/classes for the voice parameters. I guess for this to get
> uncommented out a standard/common denominator between the 4 (or is it
> 5 now) platforms that qtspeech will support needs to be found?

Yes, language and voice settings are missing, that's the biggest issue.

> Is this the only thing holding qtspeech back from getting included in
> an official Qt release? What else needs to be done for this to happen?

I think the speech dispatcher code has problems, all other backends were 
written after and should be fine. The problem with spd is that the state 
(speaking etc) can get out of sync with what spd is actually doing and what 
qtspeech is reporting. This part should be re-done (possibly internally 
tracking a desired and real state).

It may need some way to set the platform defaults (if it's to replace Jovie), 
though that can be added later.

Finally it needs to be proposed for inclusion on the Qt 5 mailing list.
Everything else I can take care of (including it in qt5.git as new module 

> I do realize that qtspeech wont write itself. I hereby commit myself
> to help with at least the linux platform code. I don't have access to
> a mac for development, so can't help there, but I can probably learn
> to help with android and windows platforms if needed.

If we nail down the API then implementing it is not so much work I imagine.


> thanks,
> Jeremy Whiting
> _______________________________________________
> Accessibility mailing list
> Accessibility at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/accessibility

More information about the Accessibility mailing list