[Libreoffice-ux-advise] [Bug 138628] ClearDirectFormatting does not remove page break

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Wed Dec 9 10:31:42 UTC 2020


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

--- Comment #14 from Telesto <telesto at surfxs.nl> ---
(In reply to Mike Kaganski from comment #13)
> Just to answer those who like to throw in unrelated rant filled with
> self-inventer guessing positioned as truth.
> 
> There was no "people not able to choose". The ODF is built with "page break
> (and page style) are paragraph property" concept. It is decided, and allows
> things like having paragraph styles that have the page break property.
> 
> But as there are people that *want* to see it as a kind of "insertable
> object", a helper was implemented to allow insertion of the break using a
> dialog (which lists different kinds of breaks). Of course, adding such a
> helper makes people imagine that "people not able to choose"...

Sorry for what you call 'rant'. However not sure where to bring this up
elsewhere (and kind of relevant, IMHO). Also thanks for answering! For the
record: I was bit ambiguous with "people not able to choose" was not directed
to user (but more related to those involved in development/design) 

So there was an actual choice: page breaks are paragraph settings.. Which got
"polluted" by compatibility mode which kind of suggesting an object. Similar as
what they blue page break line does.

As 'paragraph setting' is the design choice, and 'object interpretation' only
compatibility mode this should be included in arguments made (in my
perception). The starting point for reasoning should be based 'paragraph
setting' 

As this does make request for comment 0 'stronger' and argument against it
'weaker'. [I do get the request and yes I do get objection; and no clue what's
proper outcome]. 
Without this knowledge it's hard to follow the line of reasoning, IMHO.

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


More information about the Libreoffice-ux-advise mailing list