https://bugs.documentfoundation.org/show_bug.cgi?id=153623
Heiko Tietze changed:
What|Removed |Added
CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda
https://bugs.documentfoundation.org/show_bug.cgi?id=153623
--- Comment #15 from Eyal Rozenberg ---
(In reply to Mike Kaganski from comment #5)
> Basically, this is a part of bug 88559. The said bug 88559 is about display
> of *any* case when any property is not defined in this style; and the
> sp
https://bugs.documentfoundation.org/show_bug.cgi?id=153623
--- Comment #14 from Eyal Rozenberg ---
(In reply to RGB from comment #2)
> Sure, I know that. But that doesn't change the fact that the dialog in its
> current state is confusing.
It's both confusing and wrong.
> CS attributes are inde
https://bugs.documentfoundation.org/show_bug.cgi?id=153623
--- Comment #13 from ajlittoz ---
Understanding style inheritance (within a category PS or CS) and interaction
(when applying CS over PS) is already difficult enough so that you must not add
any complexity to the present dialog(s).
What
https://bugs.documentfoundation.org/show_bug.cgi?id=153623
--- Comment #12 from Mike Kaganski ---
(In reply to Heiko Tietze from comment #11)
> (In reply to Mike Kaganski from comment #10)
> > > Can't we use the PS attributes in CS - and solve bug 155113 en passant?
> > I don't quite understand t
https://bugs.documentfoundation.org/show_bug.cgi?id=153623
--- Comment #11 from Heiko Tietze ---
(In reply to Mike Kaganski from comment #10)
> > Can't we use the PS attributes in CS - and solve bug 155113 en passant?
> I don't quite understand this.
We use default values like Liberation Serif f
https://bugs.documentfoundation.org/show_bug.cgi?id=153623
--- Comment #10 from Mike Kaganski ---
(In reply to Heiko Tietze from comment #9)
> How do you think we can show all attributes from the PS in the CS organizer?
*I* don't think about it. I try to avoid UI questions ;) because I know that
https://bugs.documentfoundation.org/show_bug.cgi?id=153623
Heiko Tietze changed:
What|Removed |Added
See Also||https://bugs.documentfounda
https://bugs.documentfoundation.org/show_bug.cgi?id=153623
--- Comment #8 from Mike Kaganski ---
(In reply to Heiko Tietze from comment #7)
> I wonder if there is more than font name.
Every property of a character style can appear in a paragraph style.
--
You are receiving this mail because:
Y
https://bugs.documentfoundation.org/show_bug.cgi?id=153623
--- Comment #7 from Heiko Tietze ---
This particular case is about one attribute of CS that clashes with the same
attribute on PS. I wonder if there is more than font name. As a potential
solution we could add the font "[Default]" to the
https://bugs.documentfoundation.org/show_bug.cgi?id=153623
--- Comment #6 from Mike Kaganski ---
(In reply to Mike Kaganski from comment #5)
> Basically, this is a part of bug 88559.
And there, in bug 88559 comment 17, I argued that the character styles' "some
properties unspecified" are a separ
https://bugs.documentfoundation.org/show_bug.cgi?id=153623
--- Comment #5 from Mike Kaganski ---
Basically, this is a part of bug 88559. The said bug 88559 is about display of
*any* case when any property is not defined in this style; and the specific
case when *the whole hierarchy* of styles (of
https://bugs.documentfoundation.org/show_bug.cgi?id=153623
--- Comment #4 from RGB ---
(In reply to Heiko Tietze from comment #3)
> (In reply to RGB from comment #0)
> > Liberation Serif seems to be hard-coded...
> CS attributes are independent from PS; the only way to solve the problem is
> to n
https://bugs.documentfoundation.org/show_bug.cgi?id=153623
Heiko Tietze changed:
What|Removed |Added
CC||mikekagan...@hotmail.com
--- Comm
https://bugs.documentfoundation.org/show_bug.cgi?id=153623
Roman Kuznetsov <79045_79...@mail.ru> changed:
What|Removed |Added
Keywords||needsUXEva
15 matches
Mail list logo
