<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Highlighting no fill is not the same as no fill; there is still direct formatting present according to paragraph style" href="https://bugs.documentfoundation.org/show_bug.cgi?id=135871#c21">Comment # 21</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Highlighting no fill is not the same as no fill; there is still direct formatting present according to paragraph style" href="https://bugs.documentfoundation.org/show_bug.cgi?id=135871">bug 135871</a> from <a class="email" href="mailto:telesto@surfxs.nl" title="Telesto <telesto@surfxs.nl>"> Telesto</a> <pre>(In reply to Luke Kendall from <a href="show_bug.cgi?id=135871#c20">comment #20</a>) > > But of course, the whole style stuff is rather 'hard'. Basic formatting at > > PS level (say font), some overlay at CS level (bold).. accompanied with DF > > (say highlighting). What should auto-style produce here. > > I'm not sure I understand. > Do you mean, should the CS style (e.g. bold) be just a Bold style, or should > it be a style that copies all the properties of the PS and then adds Bold to > that and creates a PS, or is it just a CS style (e.g. StrongEmphasis, or > SimplifiedCharStyle2 or whatever) applied on top of the PS? A CS style is simply a style applied on top of the PS (so overruling the PS, as far as the CS differs from PS). And DF formatting is overrules PS and CS (so DF is always on top of everything). It isn't possible to stack different CS layers on top of each other (not saying this should be possible; only noting) Of course the implementation is again unfinished/confusing. A line of text. Set the paragraph style default font to lets say: Linux Biolinum G. Select a part of the text go to sidebar -> Character style & apply Strong Emphasis. Now right click Strong Emphasis and click modify. Font tab -> Notice font shown being "Liberation Serif". However it simply inherits the PS font (as expected from design point of view) However the dialog is showing something else.. so in that way unexpected. As styles already being complex by itself, those flaws are pretty annoying. I would expect it showing 'inherited' instead of any font (as there can be a multitude of different fonts where they style can be applied). Same holds true for all other areas.. As Inherited probably to long, * symbol?) Also it's possible to reset/remove CS style by Applying Default Character style (which can't be modified) --- As with the issue with all styles and formatting you can't see what is formatted using what. So if BOLD highlights in the formatting toolbar. It can caused by PS, CS or DF. (Same for font, font size, font color, highlight color) And you can't manage PS/CS styles at with the sidebar If style Inspector being active. If people don't want to meddle with the formatting toolbar, I would like the Inspector to be in the properties deck? So while editing you can see at minimum how the formatting is build up? The Style Inspector does improve things.. However it doesn't highlight all area's with certain (and no way of doing that, I think). So double clicking DF BOLD highlighting all area's with BOLD applied by DF. [Not sure if it would be workable (if edit a certain place, all other stuff is hidden again. You could consider pressing highlighting bucket.. to make it 'temporally permanent' for clean up purposes.. but if some BOLD DF shouldn't be replaced, you can't remove the highlighting.. as you introduced highlighting DF; which can't be removed (except by CTRL+M). If the mock-up will become reality this might not be an issue. But not so sure this will happen as initially advertised: <a href="https://design.blog.documentfoundation.org/wp-content/uploads/sites/2/2019/11/20191105_SI2.png">https://design.blog.documentfoundation.org/wp-content/uploads/sites/2/2019/11/20191105_SI2.png</a> And showing DF simply won't work with the current Writer comment perf issues. It simple can't handle massive amount of comments</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>