https://bugs.documentfoundation.org/show_bug.cgi?id=146493
--- Comment #28 from V Stuart Foote <[email protected]> --- (In reply to Mike Kaganski from comment #27) > Note how bug 139107 advocates for inclusion of the non-printing characters > *non-existing* in a given font into this dialog, *exactly because* the name > of the function does not imply the connection to all the *font's* > characters, but instead talks about some "special characters". > > IMO, this needs revisiting. Sure. Our legacy menu and button labeling has used 'Special Character...' for the dialog, but it clearly is an implementation of a "Character map" (though it does have implementation issues, and has dropped its edit buffer for text string composition). Do we really gain anything by relabel? While the use case of insertion of non-mapped/non-visual control characters, not associated to any font, has remained a menu of individual UNO actions (uno:FormattingMarkMenu, and the list of available UNO controls one for each control character). The menu of UNO actions could certainly be expanded to provide categorization to accommodate additional control characters (each needing its own UNO). Adopting a sub-menu similar to OPs posted attachment 177308 would probably be needed to accommodate the additional formatting marks. But the first level Special/White space/Break would not be needed. But no real advantage their either to relabeling its insert "Formatting Mark" and remains consistent with the view "Formatting Marks" visibility toggle for NPC. -- You are receiving this mail because: You are the assignee for the bug.
