This has been addressed multiple times by the development community. https://issues.apache.org/ooo/show_bug.cgi?id=6104 https://issues.apache.org/ooo/show_bug.cgi?id=70567 https://issues.apache.org/ooo/show_bug.cgi?id=71542 https://issues.apache.org/ooo/show_bug.cgi?id=84997 https://issues.apache.org/ooo/show_bug.cgi?id=116253
https://bugs.freedesktop.org/show_bug.cgi?id=69039 As a cross platform program supporting Linux, OS X and Windows environments--the UNO Accessibility API will remain the basis of support for AT. In short this is not an Apache Open Office (or a LibreOffice) responsibility, it falls to 3rd party extension developers. And it remains for external projects to implement AT for mobility impaired users who would benefit from speech recognition. Microsoft TSF is in "legacy" status. And currently no agreed "standard" exists for Speach recognition. Microsoft has gone its own way with UI and MSSR. And Nuance, with its current Dragon NS 12--Full Text Control function--looks to again have omitted Apache OpenOffice and TDF LibreOffice support for UNO API, and only supporting Microsoft productivity products. The full implementation of a native IAccessible2 (v1.3) standard based bridge for Windows OS now provides the AT hooks needed to implement Windows speech recognition to both Apache OpenOffice and LibreOffice. That might be a Nuance DNS commercial module, or I'd lean more to an Extension for AOO/LibreOffice using the Python based Dragonfly speech recognition framework and a AOO/LibreOffice specific command-module for Microsoft WSR. Perhaps a cross over from the NVDA community. -- View this message in context: http://openoffice.2283327.n4.nabble.com/Speech-recognition-with-openoffice-tp4659010p4659028.html Sent from the Development mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
