https://bugs.documentfoundation.org/show_bug.cgi?id=153485
--- Comment #11 from [email protected] --- (In reply to Rizal Muttaqin from comment #9) > I just want to know if we would want maximum consistency with > labeling/terminology why we change Tools > Outline Numbering.. to Tools > > Chapter Numbering.. previously? If I understand your question correctly -- then the main reason for the change is that many places in the UI currently use the word "Chapter", but the actual behavior of the software is applied to "headings", so "Heading" is a more accurate description. (see bug 153549 and bug 152605, comment 14) Meanwhile, the change from "Outline Numbering" to "Chapter Numbering" was motivated primarily because of a perception that users were confused by "Outline numbering" and that "Chapter Numbering" might be better. The change to "Heading" is assumed to be even easier for users to understand. So a "double" advantage: possibly easier for users and more accurate in relation to actual behavior. The "consistency" part comes "on top" of the labelling change. There is sometimes incorrect (and misleading) terminology in the extended tips and help pages. Because some updating is needed with the command name change, then it is convenient to try, at the same time, to introduce clear, consistent terminology. About the icon for the Navigator panel.... a suggestion ... Instead of using a letter (which has the problem of not being the same in all languages) -- try a graphic image like: _____ ... ... ... _____ You understand that the point of the command is to make a kind of "filter" of how many levels of headings are shown in Navigator. I have tried to show with the dots that the command has something to do with headings, where there should be some blank space between the last heading and the bottom of the icon (to suggest that not all headings are shown). (I am not proposing to use "dots" necessarily -- just used here to communicate the "concept" of the icon, not its graphic expression.) -- You are receiving this mail because: You are the assignee for the bug.
