GNOME Bugzilla – Bug 477895
Orca thinks OOo Writer normal text is bold in certain circumstances.
Last modified: 2010-05-22 18:09:39 UTC
Steps to reproduce: 1/ Start Orca 2/ Start OOo Writer with "oowriter -norestore" (not sure if "-norestore" is important - that was just the way I was trying it). 3/ In the empty text document, type in the following (without the quotation marks): control-b "bold" control-b space control-i "italic" control-i space "normal" 4/ Type Insert-f The text caret is to the right of the "normal" text. It thinks it's bold. Note that if you instead do: control-home insert-f control-right insert-f control-right insert-f the text information for each of the words is correct.
I just looked at this with Accerciser. It seems that in OOo Writer, for any given paragraph the "\n" at the end of that paragraph will inherit the style of the first character in that paragraph. YAOOB?
> YAOOB? I'd think so, but before I submit it, could Will and Mike comment...
We discussed this at the Orca team meeting this week. I will file YAOOOB.
OpenOffice issue is: http://www.openoffice.org/issues/show_bug.cgi?id=81718
Removing the "[blocked]". od@openoffice.org gave a suggested workaround that we could incorporate in the Orca StarOffice.py script: "If you want a "fast" workaround, which will be correct in most cases, you can do the following: If the user request the attributes for the character, she/he wants to input at the end of the paragraph, you can provide the attributes, which are provided for the last existing character. For most cases, this will be appropriate except the cases, in which the user explicit change a certain character attribute at the end of the paragraph. But, in this case the user made an explicit action and she/he should be aware of this action."
Adding [blocked] for bug 489828. The work done on http://www.openoffice.org/issues/show_bug.cgi?id=82637 should hopefully address much of this particular bug, though.
Changing the status to "to verify" as the OOo blocking bug has been marked as fixed.
Still blocked in the latest 3.2 available to the public (Build 9412)
Changing the status from 'blocked' to 'to verify' because the blocking bugs are marked as fixed. Note: Verification doesn't necessarily mean that Orca is doing the right thing yet; merely that in theory we should be able to implement what we need to do because we're getting the expected events from OOo.
This is now fixed by the OOo guys. There's nothing for us to do in Orca. Closing as NOTGNOME.