[Libreoffice-ux-advise] [Bug 153499] Index Entry dialog needs UI/HIG review

[bugzilla-daemon at bugs.documentfoundation.org]

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

--- Comment #8 from sdc.blanco at youmail.dk ---
Comment 4 makes a case for acknowledging "index level" as a meaningful LO
concept for discussing indices. 

- “Index levels” in LO are actually more like categories.
- Each “index level” gets its own PS (assigned in the Styles tab) and “entry
structure” (defined in the Entries tab).
- The numbers of the index levels provide a way to “identify” or
“differentiate” which PS and entry structure should be applied to a particular
index level, but there is no "structure" between levels that is enforced in the
software.
- The appearance/formatting of a level are achieved by the entry structure and
PS assigned to an index level. 
- There is probably a mnemonic value for users to refer to "levels" (even if
they are not levels in the software) because indices are often used to
communicate a hierarchical structure. 

Comment 5 (and comment 6) illustrates confusions about the relation between
index levels and outline levels => would be worthwhile to discuss indices
without reference to outline levels (except for the already noted instance when
“Outline” is checked), and always referring explicity (in the UI and help) to
"index level" or "outline level" when appropriate.

One additional terminological issue needs/deserves consideration for cleaning
up the help pages (and tool/extended tips) for indices.

In the “Assign Styles” help page [1], there is mention of an “index hierarchy”. 

I would propose to use only “index structure” when referring to the overall
result/appearance of the index (because it is neutral about the form/function
of the structure), and avoid words like “hierarchy” and “outline” when
referring to the overall index (because not all indices are not necessarily a
hierarchy or outline, or at least these terms are not defined within LO).

-- 
You are receiving this mail because:
You are on the CC list for the bug.