https://bugs.documentfoundation.org/show_bug.cgi?id=115311
--- Comment #26 from Eyal Rozenberg <[email protected]> --- (In reply to Heiko Tietze from comment #19) > CS are typically a rare breed in text Absolutely false. I use them in almost all Writer documents I author. (And I would use them in Impress too, except LO still wont let me; see bug 128810, which has multiple dupes from other people requesting it.) To the extent that people use DF over CSes for repeatedly-appearing formatting, that is due to mis-education: We are encouraged to use DF; it's the "junk food" of styling: Shiny, immediate satisfaction, no thinking about wider consideration and consequences, and when you have it a lot, it's bad for you :-) Also agree with what Mike said. > using Emphasis and Strong Emphasis together has no real-world use case. I just gave you six use cases, two of which I personally encounter frequently. > What might be a use case, however, is a > language, eg. a inline term in Latin should not trigger the English > spellchecker, together with attributes to make parts outstanding. Marking the term as Latin is the subject of bug 148257; and remember: language is not (or I should say: should not be) a formatting attribute, but an aspect of the content itself. > In any case it is possible to create a CS and inherit it from a parent. As Mike suggested, that's not a relevant solution. It's a bit like saying we shouldn't be able to mark text as underlined and as italic independently, with buttons, and that instead we would need to choose "underlined italic" from some combo-box with a zillion options. Moreover - style inheritance expressiveness is severely lacking in LO. We have (unfortunately) rejected being able to expressively inherit styles: bug 152712. One can't say any of the following: * "Font weight at 125% of the parent style" * "1 pt less inter-character spacing than in the parent style" * "font is bold if-and-only-if parent style font wasn't" > The procedure is well known from PS and easy to handle. That's a homunculus argument, Heiko, since it should also be possible to apply multiple Paragraph Styles at once: bug 149271. > If, however, the stacked CS (to name it differently from nested aka > inherited) is crucial in terms of applying more than one CS to the > selection, it obviously could be done by multi-selection. Yes. But - since users often like the selection to switch rather than to add, perhaps we would have an "enable multi-selection" toggle somewhere. > And the interaction of PS and CS would diverge. It should not, because what we do for CS we should do for PS as well (again, bug 149271). -- You are receiving this mail because: You are the assignee for the bug.
