https://bugs.documentfoundation.org/show_bug.cgi?id=152605

            Bug ID: 152605
           Summary: Change "outline level" to "heading level" in UI and
                    help pages for Writer
           Product: LibreOffice
           Version: 7.6.0.0 alpha0+ Master
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: medium
         Component: Writer
          Assignee: libreoffice-bugs@lists.freedesktop.org
          Reporter: sdc.bla...@youmail.dk

Summary:  Change "outline level" to "heading level" in UI and help pages.

Some reasons:

1. More meaningful in relation to numbering in Tools > Chapter Numbering
    For example, see [1] where "heading level" should replace "outline level"
2. Better consistency in help pages, which often refer to chapter heading,
   where "heading level" for a chapter heading, fits better than the (current) 
   "outline level".
    See for example [2] (which is already using "heading level" somewhat)
3. Makes more sense that (default) "Heading n" is assigned to
   "heading level" n, rather than the (current) "outline level".
4. Avoids confusion with lists, which also use "outline"
    See [3] and [4] for relevant comments.

In sum: Main idea (hypothesis) is that using the label "heading level" to refer
to Tools > Chapter Number > Numbering tab > Level will (a) make the
meaning/significance of "level" more transparent, including its relation to
numbering of headers, and (b) allow improvements in the help pages to better
communicate the connection between heading and heading level, while (c)
reducing confusion with the use of "outline" in connection with lists.

----
[1] https://help.libreoffice.org/7.6/en-US/text/swriter/01/06060100.html
[2]
https://help.libreoffice.org/7.6/en-US/text/swriter/guide/chapter_numbering.html
[3] https://bugs.documentfoundation.org/show_bug.cgi?id=107573#c15
[4] https://bugs.documentfoundation.org/show_bug.cgi?id=83071#c21

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to