Malte Timmermann wrote:
When the problem is in AT, not in OOo, we can't fix it, so ZoomText is
good for proving that it's very likely not a OOo bug.
Agreed. If ZoomText can do something, and JAWS can't,
it's JAWS' fault. So anybody doing serious testing of
this should be trying both ZoomText and JAWS.
To your concerns regarding filing issues to JAWS:
You might be right that they don't care much about home users, but as I
said, we (Sun) also failed to convince them to do something.
To your points
i) Write a JAWS script for OOo.
Freedom Scientific has already spent many years only in writing and
maintaining scripts for MS Office and IE, and still spend a lot of time
and resources into that.
I am not sure someone who doesn't work for JAWS can do that in a
reasonable time. If possible at all, depends on what scripting can do,
like accessing Java Accessibility API.
I wrote Freedom Scientific this morning and asked how much
they would charge to start improving JAWS' support for
OpenOffice. Let's see if the scent of money gets their
attention.
- Dan
--
Trying to get a job as a c++ developer? See
http://kegel.com/academy/getting-hired.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
