https://bugs.documentfoundation.org/show_bug.cgi?id=149271
--- Comment #6 from Eyal Rozenberg <[email protected]> --- (In reply to ajlittoz from comment #5) > Writer is base on a layered model: paragraph, character, Internet Link, > direct (from bottom to top). 1. Writer is based on ODS. So whatever happens there, should generally be able to happen in Writer. And - ODS sometimes changes to accommodate new functionality, so even that is not set in stone. 2. Direct formatting can be applied to paragraphs and to characters, so I don't see how you placing it in a hierarchy makes sense. Also see below about Internet Link. > You may be surprised to note I grant special status to "Internet Link" > character style. It has a unique property that any link created by > Insert>Hyperlink receives an extra character style above the standard style. I gave Internet Link as a typical example, but given that it gets special treatment - I'll amend the example to side-step that particular situation (although it's still a valid example I encounter occasionally). Suppose I have character styles for: * Quoted text (as opposed to a paragraph-level block-quoting) * Published article title * Source code (again, not a full source-listing paragraph) * Emphasis. Now, if I want to: * Refer to a published article whose title contains an emphasized word (or in whose title I want to emphasize a word) * Quote some text which itself emphasizes a phrase or mentions a piece of source code. then I need to combine more than one of the relevant character styles. > Since paragraphs are the basic unit of writing, I don't see what a > "combining" style application could do on paragraphs. What about my example (of a blockquote in a footnote) was not clear? Or - do you believe it's invalid? > If your goal is to override a few parameters, you can do this > with style inheritance. No, I can't. Or rather, I can only do it by an enormous blowup of duplication: For supporting a combination of k styles out of N, I would need to define a style inheritance tree of depth k with node out-degree N, having N^k leaves. That's a tremendous amount of work already, not to mention how every change to one of the styles which is not arbitrarily chosen to be at the top of the hierarchy would necessitate changes to a large number of other styles at the same level of the hierarchy. And it's not just me who would need this: LO _already_ needs this. Even with the styles available by default, we're missing these duplicates: "Footnote Blockquote", "Endnote Blockquote" etc on the paragraph level, and some combinations of Page Styles etc. And let's not talk about triplets of styles, which occur less frequently but do actually occur. I would like to address the rest of your comment, but - I thought maybe we should focus on the motivating examples first. If you'd rather I answered the rest of your comment, please say so and I'll do that. -- You are receiving this mail because: You are the assignee for the bug.
