Hi, I only have the single jre environment on this machine now. I did
download python for windows since two blind programmers used it to write
nvda starting back in 2006 so I figure it'll be an accessible
development platform for me. I'm new at python since I've never been
asked to use it at work and just recently got this windows7 machine.
I'll start looking through those configuration files and see if I can
find the offending lines and see if I can't correct a few things this
On Tue, 5 Jun 2012, V Stuart Foote wrote:
Andreas comments earlier about a "list box" apply if you have more than one
JRE installed and is the reason I asked you to uninstall ALL your Java
Runtime Environments and to then use the JWin installer with a new JRE
installation, it was to ensure that you only have one JRE.
To answer what alternative ways to activate Java and Assistive
Technologies--both of which are disabled by default in LibreOffice 3.5.x--at
this point with LibreOffice 3.5.x your only options are navigating within
the LibreOffice Graphical User Interface (admittedly not very "assistive"
since it does not respond to screen reader while configuring). Or, you have
to directly edit the XML configuration files (again not very "assistive").
If you want to try to directly edit them, there are two configuration files
you would have to work with.
The Java Runtime can be toggled enabled "true", or disabled "false" from
the per user configuration file located at:
file in the "<enabled xsi:nil="false">true</enabled>" stanza
And the Assistive Technology tools can be toggled enabled "true" or disabled
"false" from the per user configuration file located at:
file in the
I'm sure these edits could be scripted with a Windows shell or Python
But at this point with just the one JRE installed (please double check that
is the case), and with the Java Access Bridge installed using the JWin
installer utility, it is simplest and most reliable making the configuration
changes from the GUI. This is even more reliable if your user configuration
is allowed to rebuild set to defaults.
So, the next step you need to perform is to remove (or rename) your
LibreOffice per user configuration file.
When no longer detected, a new "default" user configuration file will be
created. Any misconfiguration, plug-ins, extensions that may have been
present from past installations will be gone from a new default profile.
With a default user profile in place, it should finally clear any issues
when you perform the two enabling sequences. That is, first Java with--
Then the Assistive Technology with--
<alt>a -- (or as I've been giving, <tab><space>)
So, please perform these final steps:
1. remove (or rename)-- C:\Users\<your user
2. launch LibreOffice to allow default profile to be built
3. enable Java support
4. enable Assistive Technology
p.s. for others reviewing this thread-- the AppData\Roaming path is for
Windows7, if you enter "echo %APPDATA%" at a windows command window you
will see the correct path to use for your user account.
View this message in context:
Sent from the Users mailing list archive at Nabble.com.
For unsubscribe instructions e-mail to: email@example.com
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-users] Re: libreoffice 3.5 inaccessible · Andreas Säger
- Re: [libreoffice-users] Re: libreoffice 3.5 inaccessible (continued)
- Re: [libreoffice-users] Re: libreoffice 3.5 inaccessible · Jude DaShiell
Impressum (Legal Info)
: 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