Date: prev next · Thread: first prev next last


Contact me off list I think I can help. it's a shame that ia2 is not supported yet!

It's a very long time coming I have been very patient but until IBM or oo gets the code out there we will have to struggle and hack around just to get the software working.

Malt if you are around can you please let us vi users know what the state of play is at the moment with Ia2 in open office or this Libreoffice program with thanks.

On 16/02/2012 15:41, David Goldfield wrote:
I am a visually impaired user of Libreoffice.  I am able to use it with the free open source screen 
reader NVDA, available from<>.
It has always been necessary that the Java Access Bridge be installed in order to ensure that NVDA 
can speak things such as menus, dialog boxes and even the text of the documents.  However, i notice 
that I'm unable to get any output with the new 3.5 release using the latest NVDA beta 2012.1.  I'm 
running Windows 7, 32-bit edition.  Enabling assistive technology support makes no difference.
I've reported this as a bug in Libreoffice's bug tracker but I'm wondering if anyone else can 
duplicate this and if there is a workaround which is not obvious to me.

thanks so much for any help you can provide.
David Goldfield

All The Best
Kevin Cussick

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.