Problem description: No Text To Speech or Speech To Text
Steps to reproduce: NA
Current behavior: NA
Expected behavior: Should allow dictations & should read out selected stuff on giving that command.
Please can you have Text To Speech & Speech To Text as well. Google's Text To Speech & Speech To Text Engine may be used I guess (with their permission of course) with an extension or something.
This will help dictate notes & letters. Similarly it can read out what the document says.
Maybe, even voice commands like: "LO, select all"
Operating System: All
Version: 188.8.131.52.alpha0+ Master
Some Android Apps have Text to Speech & Some have Speech to Text.
This would be a KILLER feature making all those bogus complaints of an "ugly" user interface *obsolete*.
enhancement request. this feature has never been present in OOo and LibO.
status NEW. version: inherited from OOo
An enhancement clearly beyond project scope. Believe this should be set resolved wontfix--or possibly converted to a Meta.
Each OS requires its own framework for speech recognition. That framework would then have to interact with the UNO Accessibility API via a native accessibility bridge (ATK, IAccessible2, or NS Accessibility).
Marginal support already under OSX with VoiceOver and Dictation (aka SIRI).
ATK support of the Orca project does not implement speech recognition--so minimal GNOME-Voice-control or Simon listens
And as Microsoft went its own way with UIA (dropping Text Services Framework) there is nothing integrating IAccessible2 to UIA based Windows Speech Recognition.
Unfortunately, as there is no "standard" for speech recognition, there is nothing for the project to implement.
Development would of necessity be external to the project. Where, open source projects such as Dragonfly (Python), or Sphinx (now Java implemented) offer some promise of providing speech recognition framework--but at most integration would be by external API interface, and not into the core. Just as Nuance's Dragon NS had done in the past.
Improvements to UNO Accessibility API and the native bridges are of course in scope to accommodate implementation.
Migrating Whiteboard tags to Keywords: (a11y -> accessibility)
*** Bug 108271 has been marked as a duplicate of this bug. ***