https://bugs.documentfoundation.org/show_bug.cgi?id=169659
--- Comment #23 from V Stuart Foote <[email protected]> --- @Rafael, thanks for the see also link to bug 138725 had forgotten some of that discussion, and Maxim's and Justin's tech notes toward the bottom. Simply put, here the *best approach for now* remains as in comment 4 and comment 5 to make the full tooltip--with its configured UNO, its Label, Tooltiplabel, Context label and Properties--made available in the assigned Shortcut area and not just the Function column after a search. Giving parity to the other Customize tabs to be able to identify what is already assigned. Then, some full redesign of the Customize -> Keyboard could implement something more to provide descriptions and UI appropriate button names (and their associated l10n). For example since we've now got an SQLite instance with our python support would think we could possibly get away from the convoluted entries (and l10n translation effort) held now in the GenericCommands.xcu While poking at these piecemeal is a recipe for incomplete/inconsistent change that is the worse "change for changes sake". And gets an emphatic -1 from me to do it like that. -- You are receiving this mail because: You are on the CC list for the bug.
