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

--- Comment #11 from [email protected] ---
(In reply to ajlittoz from comment #10)
> For consistency with all the other table Entries tab (except Bibliography),
Not sure why consistency should be important in this context. I would put
higher priority on meaningful mnemonic labels for the abbreviations.

Meanwhile, in actual fact, the labels and abbreviations appear to be
consistent. See attachment 185540 for an overview.

> E# = category + category number
But this fails your consistency test. (-:

At present E# only appears for ToC, where it only provides a Heading number
(not a category number) and no category (label). (in relation to E#, see bug
153561)

My proposal with the Cs, is to introduce additional widgets in the Entry tab,
as part of the structure dialog, so that the user can control the Category
number and category label and caption text independently (and to drop/move out
that control from the "Type" tab).  This is completely separate from E# (which
has to do with the Heading number that appears before a caption, not caption
labels).

Have I misunderstood your point?

> However, this immediately raises a problem. From my experiments, today the
> "components" of the caption paragraph are split at the number range field
> with a subtlety. 
I have also encountered "strange" things with number range field (also with
setting the number of levels, see bug 153710). Could not decide what was
intended behavior and what was bug, in part because I can not systematically
repeat particular strange effects. (I think there are also sometimes problems
with "refresh" / "updating" the index.) -- so I have stopped exploring such
issues.

> ==> But to do with the separator? Should it be included with E# or ignored,
In the "real" E# (in ToC), there is a dropdown box, which allows both choices.
In my proposal, clicking on C# would provide a dialog with a dropdown box like
E# (where you can choose separator or not).

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

Reply via email to