https://bugs.documentfoundation.org/show_bug.cgi?id=153731
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=14 | |0846 --- Comment #4 from [email protected] --- (In reply to Heiko Tietze from comment #3) Thanks for useful comments. > If you figure out where to add what it's an easyhack. > For consistency I'd add a type label before the level. Like "List: <level>". Good idea. My guess for this case: NC_("STR_NUM_LEVEL", "Level ") https://opengrok.libreoffice.org/xref/core/sw/inc/strings.hrc?r=04495836#1394 How about: "Level " -> "List: Level " > > 7. Click on section where "Chapter Numbering..." appears. > Quite long label and I wonder if we can use "Heading: <level>" here. No objections. Another guess: NC_("STR_OUTLINE_NUMBERING", "Heading Numbering") https://opengrok.libreoffice.org/xref/core/sw/inc/strings.hrc?r=04495836#301 Drop the "Numbering" -- but NB -- will also affect the Outline & List tab in PS, which would also show only "Heading" for List Style. (i.e., consistency between PS tab and status bar). And see bug 140846, maybe "Outline" should become "Heading" in the Contains section of the Organizer tab for PS (which should regain the lost consistency, lamented in bug 140846, comment 8) The status bar display for lists is managed with: https://opengrok.libreoffice.org/xref/core/sw/source/uibase/uiview/view2.cxx?r=fc1c9d7c#2038 but could not find out how B&N dialog was opened. But wouldn't the idea be to follow the same procedure, but open the appropriate dialogs? If so, then that, along with the label changes, would resolve the issues raised in this ticket. Chapter (heading) numbering is already recognized, but goes to the wrong dialog. List Styles also appears to be identified, so would need to add possibility to open appropriate dialog (which is still the B&N dialog, but probably need to use STR_POOLNUMRULE_NUM_ARY to identify the List style). -- You are receiving this mail because: You are the assignee for the bug.
