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

--- Comment #29 from Adalbert Hanßen <[email protected]> ---
(In reply to Heiko Tietze from comment #23)
> To cut a long story short: paragraph breaks continue with the new PS but
> keep the previous CS. Which makes sense within the paragraph but not
> necessarily across.
> 
> Mike, any concerns to switch off the CS after a paragraph break?

Of course DF should also be dropped after a new paragraph is started. I have
seen comments 24 and 25: I doubt that many people really expect CS and DF to
continue after beginning a new paragraph. It looks more natural to me to start
from the default settings for a new paragraph.

Unfortunately the documentation neither tells about the formatting behavior
when a new paragraph or line is begun nor tells it anything about the
precedence of formatting options. Changing this merely fixes an undocumented
feature. I also proposed to close this gap in the documentation.

Because humans are creatures of habit and people with little knowledge some
times even more considering a program reaction, which they have experienced
once, as the only reasonable one and don't think about alternatives, I had
already suggested to let behavior depend on a basic setting in LibreOffice. In
this context, one could still think about whether to set the default value for
that as I suggested, i.e. forget CS and DF, or whether to give preference to
the continuity of operation, i.e. keep them both (=present behavior). The
latter can certainly be argued for, although I don't: Advanced users who use
style sheets should not be hindered and for them it is probably more natural to
end the previous DS and DF with a new PS, which Heiko also agreed with. 

That this question came up at all and did so many rounds shows, after all, how
confusing LO's current behavior is at this point. 

How can you actually tell for sure and at a glance what the effective
formatting has done: PS, CS or DF?

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

Reply via email to