https://bugs.documentfoundation.org/show_bug.cgi?id=170517
V Stuart Foote <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=10 | |8458 CC| |[email protected] --- Comment #2 from V Stuart Foote <[email protected]> --- (In reply to Heiko Tietze from comment #1) > Same idea has been rejected in bug 169659 Well, not really. That was about the Keyboard shortcuts, while this is the more generic need for toolbars affecting labeling in the UI, to improve (where it makes sense) the descriptions of UNO commands that have *nothing* currently. Labeling/description for UNO that gets worked into the UI globally and for each module as well as for each UI element--Menu, Toolbar, Notebookbar(s), Context Menus, and Keyboard available as 'Customization'. They affect how devs build the UI elements as presented (tb buttons, menu labels, dialog buttons), but also how users can adjust things to taste with customization. Point is that better naming/labeling/description for *under-described* UNO controls really is needed. Yes it would be a huge undertaking to tweak the controlling .xcu and then the corresponding l10n. That alone could lead to a => WF as we disposed bug 169659 Seems to me, it might be appropriate to look for a better way to hold details on all the UNO than the currently in XCU? Wouldn't SQLite or possibly Firebird be an appropriate route to migrate the XCU over to? -- You are receiving this mail because: You are the assignee for the bug.
