Bug 158879 - Direct-formatting of INDIVIDUAL list symbols
Summary: Direct-formatting of INDIVIDUAL list symbols
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.6.0.3 release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected
: 160792 (view as bug list)
Depends on:
Blocks: Writer-Styles-List
  Show dependency treegraph
 
Reported: 2023-12-27 03:41 UTC by libretist
Modified: 2024-05-08 09:04 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description libretist 2023-12-27 03:41:12 UTC
Description:
Please allow for direct-formatting of *individual* list symbols.

Currently this seems only possible by way of an obscure trick found by a fellow user here:
https://ask.libreoffice.org/t/direct-formatting-of-list-symbols/99731/7
This obscure trick is very counter-intuitive since it works by selecting the *subsequent*(!!) list item, see image:
https://ask.libreoffice.org/uploads/asklibo/original/3X/0/d/0d82bc4893701ba3c0fa837285563222f9654f38.png

Unfortunately this trick does not always work. We haven't yet figured out why. Maybe it depends on whether the item text includes forced line breaks or not. But it could be something else entirely. Not sure.

I don't know if a bug prevents this obscure trick from working consistently *OR* if the fact that this obscure trick sometimes works actually is a bug itself.

Either way, this request asks for another, more intuitive (and consistently working) method to direct-format individual list symbols.

Steps to Reproduce:
n/a

Actual Results:
n/a

Expected Results:
n/a


Reproducible: Always


User Profile Reset: No

Additional Info:
n/a
Comment 1 libretist 2023-12-27 03:44:12 UTC
related: bug#158835
Comment 2 Telesto 2023-12-29 14:21:53 UTC
A) The obscure trick is likely a bug. The trick doesn't work in older version of LibreOffice. And the formatting applied with current version of LibreOffice visible with older versions.

B) The request of being able applying direct-formatting of *individual* list symbols is valid request, IMHO  

C) Side note: Applying direct formatting to a list is in more ways broken.
1. Insert a list
2. Place cursor in the list field
3. Apply red font color (to the full list)
4. Place cursor outside the field
5. Press undo (formatting change isn't included)
Comment 3 Telesto 2023-12-29 14:25:39 UTC
To bibisecters:
Attachment 191568 [details] has formatting applied to single entry's of the numbered list. 

However this isn't visible in (or older) 
Version: 7.4.8.0.0+ (x64) / LibreOffice Community
Build ID: f8ba7c6f77497e2dc7bfef8378511e2074ce01f9
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL
Comment 4 Telesto 2023-12-29 21:11:28 UTC
Bisected to:
tdf#155238: Reimplement how ListAutoFormat is stored to ODF

This reimplements commits 6249858a8972aef077e0249bd93cfe8f01bce4d6
(sw: ODT import/export of DOCX's paragraph marker formatting,
2022-12-19) and 209dce614c43f63f63f5b42a746665c0ec1cbfe3 (sw: fix
ODT import of paragraph marker formatting, 2022-12-20).

Instead of using an empty trailing span for the ListAutoFormat data,
introduce a new loext:marker-style-name attribute for text:p element,
referencing a text autostyle.

The problems with the previous implementation were that (1) it was
impossible (or very difficult) to disambiguate several empty trailing
spans, in case it was needed; and (2) this was incompatible change,
with other ODF implementations treating the trailing span normally.

I couldn't manage to incorporate the attribute to paragraph autostyle,
because of problems referencing different autostyles one from another,
so put it directly to the paragraph attributes.

Change-Id: I33473147f1f774c24cbbc57bf0c4f3a1d83ce5bc
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151645
Comment 5 Telesto 2023-12-29 21:20:03 UTC
@Mike
I guess you unintendedly introduced a new feature (workaround) as a side-effect of a change you made. 

I bibisected this based on attachment 191568 [details] (bug 158835). Both are more or less about the some topic. Opening the file in older versions of LO doesn't show formatting of the numbered list.
Comment 6 Mike Kaganski 2023-12-30 06:46:40 UTC
This is not about my commit. It is about the whole "paragraph marker formatting" feature (introduced in commit 5ba30f588d6e41a13d68b1461345fca7a7ca61ac) still has no UI. It was originally created with interoperability in mind, to enable good import and round-trip of MSO documents. But the UI is needed anyway.
Comment 7 Telesto 2023-12-30 08:33:06 UTC
(In reply to Mike Kaganski from comment #6)
Thanks for the quick reply. UX is aware about the required UI part?
Comment 8 Heiko Tietze 2024-01-02 11:48:52 UTC
The UI would probably require to allow changes to foreground/background color, symbol type (ie. character, image, number style ), symbol size. Excluding position, separator, value/level. 

But before this can be done I think we need to select the list symbol, without adding the previous paragraph. If this adds too much fuss I could also imagine a special command "List Item" on the context and main menu.
Comment 9 Heiko Tietze 2024-01-05 12:56:42 UTC
Dup of bug 92170?
Comment 10 libretist 2024-01-11 22:56:47 UTC
(In reply to Heiko Tietze from comment #9)
> Dup of bug 92170?

I don't think these are duplicates.

bug92170 seems to concern the "Shape style dialog" in Draw and Impress
bug158879 concerns direct-formatting in Writer
Comment 11 Heiko Tietze 2024-01-12 10:58:29 UTC
(In reply to libretist from comment #10)
> I don't think these are duplicates.
The "style" tab could be the same on DF and LS.
Comment 12 libretist 2024-01-12 15:23:43 UTC
(In reply to Heiko Tietze from comment #11)

It still is about styling.
This over here is the exact opposite (direct-formatting).
Comment 13 Stéphane Guillou (stragu) 2024-05-08 09:04:15 UTC
*** Bug 160792 has been marked as a duplicate of this bug. ***