https://bugs.documentfoundation.org/show_bug.cgi?id=165879
--- Comment #6 from ajlittoz <[email protected]> --- (In reply to Heiko Tietze from comment #5) > > A PS does not formally contain a CS, but it does contains one implicitly - > > by containing all properties of a CS. Note the bug title... > > No. A new PS has character attributes. There is no style, and definitely no > "Default CS". My statement was a "short circuit" one. Of course, there is no explicit CS when you create a PS. The PS contains internally all attributes of a CS (except one), thus allowing a PS to be applied without needing a CS. This internal group of attributes behaves like a "default" PS, thus my wording. > |Unfortunately, this default CS is not as "complete" as can be a stand-alone > CS. > |The provided Borders tab refers only to paragraph borders. The "character > borders" > |are missing. > So you do want a CS being created first and then applied to the new PS. No, the present workflow is good. A PS is "self-sufficient": you create one, you apply it and you get what you expect. The vast majority of users don't even know what a CS is and apply direct formatting for "exceptions" within their paragraphs (a single word in italic or bold). > |The provided Borders tab refers only to paragraph borders. The "character > borders" > |are missing. > > These are just two different things. Assuming a "Character Border" was > available on the PS this means applying that PS puts a border around every > consecutive character effectively lines. I see no need for that. Look at the provided example file. The main difference between paragraph and character border is the range. With a PS, border extends from margin to margin no matter text width (this is what you expect from a paragraph because its bounding box is defined as fixed within the page). With a CS, borders are as wide as text (because the border are defined for individual glyphs). In the example file (which results from a request by a user), the specification wants borders only around heading text, limited to the effective heading. If the borders were defined inside the PS, they would extend from margin to margin. So an ad-hoc CS was applied over the heading. Without this "hack" (word used because the PS attributes don't allow for character border), if the borders were defined in the PS, this would require as many PS as heading width which is unacceptable and contrary to the principle of "semantic styling" (i.e. one significance => one PS) and practically reverts to a pernicious form of direct formatting. Note also that being forced to apply a CS over the heading PS makes it extremely difficult to apply another CS, e.g. to italicise or embolden a word, because applying several CS'es is very tricky and creates an editing nightmare. So, please, lift the restriction about character border in a PS. I reckon this creates a vocabulary problem because we can't have two "Borders" tab in configuration dialog. It is important not to confuse users with these two distinct notions: global paragraph border and individual character border. -- You are receiving this mail because: You are the assignee for the bug.
