[Libreoffice-ux-advise] [Bug 148597] FORMATTING request enhancement: create formatted Table of Figures using tabs before and after index

2022-06-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148597

Heiko Tietze  changed:

   What|Removed |Added

 Status|NEEDINFO|NEW
 CC||rb.hensc...@t-online.de

--- Comment #3 from Heiko Tietze  ---
(In reply to ajlittoz from comment #2)
> In the case of a TOC, chapter numbering is captured separately from the
> heading. These bits of information end up in E# and E descriptors which can
> be arranged separately.

Good point!

> A paragraph style (PS) can define tab stops with various attributes
> (alignment, leading, …). The Structure line in TOC overrides the PS tab
> stops without the possibility of variants.

You mean changing the tab stop for the paragraph style has no effect?

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

[Libreoffice-ux-advise] [Bug 148597] FORMATTING request enhancement: create formatted Table of Figures using tabs before and after index

2022-06-29 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148597

--- Comment #2 from ajlittoz  ---
The difficulty comes from the way data needed for the Table of Figures is
collected.

The caption is captured as a whole, i.e. no distinction is made between
generated contents ("Text", "Figure", …, number range inserted with a field and
the final separator) and user provided text (the "caption" itself). The whole
caption ends up in a E descriptor.

In the case of a TOC, chapter numbering is captured separately from the
heading. These bits of information end up in E# and E descriptors which can be
arranged separately.

There are two Type's to generate a table of figures from the TOC dialog: Table
of Figures and Index of Tables.

BTW, why are there two items in the menu as they are strictly equivalent?
Legacy of history?

The kind of table is selected by the Category menu which designates the number
range.

>From my naive point of view, we already have all elements to be able to
discriminate components of the caption, all the more since Display menu offers
to get rid of number or text if so desired.

User would gain more versatility if both data were made available in E# and E
descriptors instead of the present composite E.

Or course, this has a huge compatibility impact on existing documents.

=

bug 94661: I think it is a separate issue. See my comment there.

bug 32360: a "comfort" request? it can be done manually by manipulating the
Structure line in the Entry tab. The only common factor is the mention of tab
stops.

==

The question of tab handling in TOC/Tables of … is a fundamental one. The
Structure line introduces a bias but I can't tell if it is a simplification or
additional difficult compared to paragraph style usage.

A paragraph style (PS) can define tab stops with various attributes (alignment,
leading, …). The Structure line in TOC overrides the PS tab stops without the
possibility of variants. The only user-friendly addition is the Align right
check box for a quick reference to the right margin or indent (I remember
however some "distortions" with non-zero indents and, most annoying,
multi-column pages or sections).

Could it be possible to remove tab definition from the Entries tab to rely
exclusively on PS tabs? I know this could upset many users as the full TOC
configuration would require to look at two dialogs: TOC and PS and this would
be a complication for most users who don't practice styling with ease.

I don't think it would be too difficult to implement. The generated entry
contents (a paragraph) is passed to the formatting routine which then applies
standard processing.

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

[Libreoffice-ux-advise] [Bug 148597] FORMATTING request enhancement: create formatted Table of Figures using tabs before and after index

2022-04-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148597

Heiko Tietze  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1

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

[Libreoffice-ux-advise] [Bug 148597] FORMATTING request enhancement: create formatted Table of Figures using tabs before and after index

2022-04-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148597

raal  changed:

   What|Removed |Added

   Severity|normal  |enhancement
 CC||r...@post.cz

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

[Libreoffice-ux-advise] [Bug 148597] FORMATTING request enhancement: create formatted Table of Figures using tabs before and after index

2022-04-22 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148597

Heiko Tietze  changed:

   What|Removed |Added

 CC||mikekagan...@hotmail.com

--- Comment #1 from Heiko Tietze  ---
You align the content label (Figure) at left and the number right, followed by
a left aligned caption. Such a layout can be done only per table or in a ToC,
by right-aligning a tab stop. But apparently we have a bug here, see bug 32360
and bug 94661.

The actual request is going beyond the ToC. You could also expect the text of
headings to align at the second line. This can be done per indentation
(positive value before text and negative for first line). If you give enough
space for large numbers this works well. And it should do the trick as well for
ToC if you modify the "Contents x" PS properly.

My take: NAB (or duplicate). What do you think, Mike?

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

[Libreoffice-ux-advise] [Bug 148597] FORMATTING request enhancement: create formatted Table of Figures using tabs before and after index

2022-04-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148597

Telesto  changed:

   What|Removed |Added

   Keywords||needsUXEval
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||tele...@surfxs.nl

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