Download it now!
Bug 118148 - [NEWHELP] Handle <ahelp> tags in the UI
Summary: [NEWHELP] Handle <ahelp> tags in the UI
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Documentation (show other bugs)
(earliest affected)
Hardware: All All
: high normal
Assignee: Not Assigned
Keywords: accessibility
: 124130 131748 (view as bug list)
Depends on: 120538
Blocks: New-Help 112237 129720
  Show dependency treegraph
Reported: 2018-06-13 16:52 UTC by Olivier Hallot
Modified: 2020-06-29 20:18 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Olivier Hallot 2018-06-13 16:52:14 UTC
In old help system, the <ahelp> tag is extracted at build time to be used by the user interface as tool tip for each widget.

The new help does not handle that, yet.

The content of <ahelp> should be available as tool tips in the UI dialogs. UI dialogs have provision to hold tooltips for each widget.

the <ahelp> tag is documented here:,_Authoring_and_Editing_Openoffice.org_Help/3#ahelp

So the task/enhancement is to have a script that extracts <ahelp> of a given dialog and add it to the corresponding .ui file. 

This will have some impacts
- The UI will increase in volume of translation job, but
- ideally the translated <ahelp> should go too, to prevent re-translation.
Comment 1 Buovjaga 2018-06-22 16:59:15 UTC
Setting to NEW
Comment 2 V Stuart Foote 2018-10-16 12:32:49 UTC
The a11y impact is a more immediate issue.
Comment 3 Olivier Hallot 2019-03-18 11:19:00 UTC
*** Bug 124130 has been marked as a duplicate of this bug. ***
Comment 4 V Stuart Foote 2020-03-31 21:35:07 UTC
*** Bug 131748 has been marked as a duplicate of this bug. ***
Comment 5 Olivier Hallot 2020-06-21 15:58:00 UTC
Currently (master 7.0), filling the tool tip field in the widget will display it in the dialog

But the Tools > LibreOffice > General > Extended tooltip checkbox does not control it.
Comment 6 Olivier Hallot 2020-06-21 16:41:55 UTC
Important discussion on the topic
Comment 7 Olivier Hallot 2020-06-29 20:18:52 UTC
 (In reply to V Stuart Foote from comment #2)
> The a11y impact is a more immediate issue.

Looks like that if we copy the <ahelp> contents on the widget "Accessible Description" field, e.g,

<child internal-child="accessible">
    <object class="AtkObject" id="versionlb-atkobject">
        <property name="AtkObject::accessible-description" translatable="yes">bla bla bla bla bla</property>

It works (enable extended tips in the Options).

Any other settings? What about field "AtkObject::accessible-name" and other in the accessibility tab of Glade?