Apache OpenOffice (AOO) Bugzilla – Issue 22053
gnome screen reader(gnopernicus) not reading selected text
Last modified: 2006-02-09 09:30:17 UTC
using a gnome-2.4 build from 24/10/03 using StarOffice 7 build from 31/10/03 reproduce: -launch staroffice 7 -launch gnopernicus with speech enabled -open a new text file -type a sample text document -highlight a portion of text from the document -gnopernicus does not read out the selected text expected: -the selected text in StarOffice should be reported by gnopernicus
reassigned to es @es: I think this is something for you...
ES->RU: please evaluate.
RU -> OBR: I compared the current SO behaviour with the behaviour of gedit. In gedit every marked character is reported. When one removes the text marking again screen reader reports "No selection anymore" Neither of them is reported in SO. RU: This bug is a candidate for Cinnabar.
.
*** Issue 25401 has been marked as a duplicate of this issue. ***
OpenOffice.org does not yet implement TEXT_SELECTION_CHANGED events. I am not sure why gnopernicus seems to ignore caret events while shift key is pressed though. Changing all (four) text implementations in the Office is unlikely to happen in the 1.1.x time frame, so I re-target this to 2.0.
Because of a shortage of resources we have to retarget this issue to OOo later.
*** Issue 32928 has been marked as a duplicate of this issue. ***
Gnopernicus ignores the caret events while shift key is pressed because it checks if there is a selection for this text object. So, if AccessibleText_getNSelection!=0, from gnopernicus point of view there is a selection which should be reported and the 'caret:moved' event is ignored.
Due to the importance of this issue, re-targeted to OOo 2.0
retarget to later due to missing ressources
re-targeted to "OOo 2.0.2" and changed priority to "P2" because of severe missing functionality
re-targeted to OOo 3.0
re-targeted to OOo 2.0.2, re-targeting to OOo 3.0 was done by error
Meanwhile a workaround for the missing TEXT_SELECTION_CHANGED events has been implemented in the Java AccessBridge for GNOME. However, these events are now generated by all OOo text components, so that this will (hopefully) not break when switching to a UNO <-> ATK bridge.
obr -> es: please verify that recent changes for TEXT_SELECTION_CHANGED support did not break gnopernicus reading selections. However, even with FLOWS_FROM/FLOWS_TO relations now implemented, I can't see any improvements in multi-paragraph selections :(.
Restoring FIXED state.
Verified in CWS swqbf49
Ok in src680m156