[libreoffice-accessibility] Java Accessibility restored to LOdev 3.6 development builds, on hold for LibO 3.6.4

The developers have resolved the LibO source code issue for Assistive
Technologies for  Windows builds  using Java Accessibility API and the Java
Access Bridge mappings.

Unfortunately, not quite in time for the LibO 3.6.3 release that is now
building from the rc2 code base for a publish target Oct 29 - Nov 4th.

The fix WILL be in place for the LibO 3.6.4 builds due for publishing the
week of Dec 3 - 9. 

In the interim, LibO 3.5.7  Accessibility for Windows users is intact.

Or,  for the intrepid willing to work with the -LOdev-3-6 developmental
code, daily builds of the  -3-6 Windows branch are available at this link:

http://dev-builds.libreoffice.org/daily/Win-x86_9-Voreppe/libreoffice-3-6/

It is limited to language support for English, French and Spanish and lacks
a few of the extensions but is otherwise pretty stable. 

But if you are really adventuresome , the Developers are always looking for
folks willing to test and report on the current builds of the master
developmental code.  The daily builds systems for Windows (each a TinderBox)
are a little erratic, for example waiting on a sucessful build of the
current master code to test accessibility in LOdev 3.7, but the Devs get
that sorted out pretty quickly.  And they do appreciate getting earlier
feedback.

Here is the link to the daily TinderBox builds of master 
http://dev-builds.libreoffice.org/daily/
<http://dev-builds.libreoffice.org/daily/>    where forWindows build of 
LOdev 3.7 you'll want  TinderBox 6 Win-x86@6 (MSVC)
<http://dev-builds.libreoffice.org/daily/Win-x86@6/>   or   TinderBox 7
Win-x86@7-MinGW (MinGW)
<http://dev-builds.libreoffice.org/daily/Win-x86@7-MinGW/>  .  

The build time is the folder name, you'll want to download the latest and if
a site is really old, it means there were build problems with that
server--for example the two TinderBoxes 6 & 7 are both very stale due to an
error in the build system that is being worked on.

All agree that catching the problem with lack  Java Accessibility support
should not have made it past the first release of the LibO 3.6 branch! 
Having more users comfortable with working with the developmental builds
will help a lot when the call comes for testing.

Please do help.

Stuart




--
View this message in context: 
http://nabble.documentfoundation.org/Java-Accessibility-restored-to-LOdev-3-6-development-builds-on-hold-for-LibO-3-6-4-tp4015515.html
Sent from the Accessibility mailing list archive at Nabble.com.

-- 
Unsubscribe instructions: E-mail to accessibility+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/accessibility/
All messages sent to this list will be publicly archived and cannot be deleted