https://bugs.documentfoundation.org/show_bug.cgi?id=149230
Heiko Tietze <heiko.tie...@documentfoundation.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.documentfounda
| |tion.org/show_bug.cgi?id=11
| |7022
--- Comment #9 from Heiko Tietze <heiko.tie...@documentfoundation.org> ---
Since the discussion is going towards Writer only: we have the meta ticket for
a "Style-focused formatting toolbar" with bug 117022. In fact, the inbuilt
"Formatting (Styles)" toolbar is meant as replacement for the ordinary
Formatting toolbar.
However, I would challenge the idea of educating users (just for sake of the
argument). We can force users into learning a paradigm or - the actual
challenge for UX/IT - make the software smart. Simple solution is to change DF
= bold into CS = Emphasis (with the only attribute bold). Or change two empty
paragraphs into a heading plus spacing.
But I believe this "convenience solution" would be the wrong way even when
requested by the users. Competitors do so - on cost at flexibility and
clearness. Everyone who tried to work with styles in MS Word knows that
LibreOffice is way superior in this regards.
My solution would be to not force users into a certain workflow but rather give
better feedback. Like done/planned with the accessibility checker or suggested
in bug 38194. We could show a "traffic light indicator" in the statusbar with
green in case of no DF and a low number of PS/CS, yellow for a few DF or large
number of PS/CS, and red.
--
You are receiving this mail because:
You are the assignee for the bug.
