Description: Suggestion -- add a Comments field to LibreOffice Styles (i.e., paragraph styles, character styles, frame styles, page styles, list styles, table styles). A Comments field enables one to document intended purposes for the styles (e.g. for a fiction novel template). Steps to Reproduce: N/A Actual Results: N/A Expected Results: N/A Reproducible: Always User Profile Reset: No Additional Info: N/A
Created attachment 176084 [details] More detailed description of enhancement & example custom style names The attachment provides additional detail concerning the proposed enhancement, as well as some example custom style names.
Created attachment 176085 [details] More detailed description of enhancement & example custom style names Adds more details describing the proposed enhancement to LibreOffice Writer and some example custom style names.
KMM, thank you for your idea. But I'm not sure, if I understand it correctly. Do you want to add a comment field to the paragraph styles dialog (for example in organizer tab)? Use case might be that you have a template that should be used by different persons ad every person should know, when to use a certain style. Is this the idea? => NEEDINFO
This is rather clear request and there's no need for Needinfo. I set Unconfirmed again. I added UX.
I understand the request exactly as Dieter asks back. But what puzzles me is the huge list of styles in the attachment (don't see a description). Styles should be used sparingly and combined with templates. So template A would be "Hard Bound Cover" with ~10 paragraph styles (PS), actually 4 or 5 categories with less than 5 PS. "Perfect Bound Cover" would be another template, etc. What's listed under Character Styles (CS) is counterproductive as it combines all attributes into styles. You could also use direct formatting in this case. Change this to something meaningful like "Emphasis" and use only a small number of CS. Putting all together I see where the request comes from but doubt it's needed.
I totally agree that a specific case might mis-use styles, and would be best re-designed. But generally, as someone who used to design a standard for styles in an organization, where I created templates as part of the process, wrote guidelines for users explaining where and how to use the templates and styles in them, I totally support the idea, which might be perfectly reasonable in a correctly designed template, and each style describing itself (where and how) to users.
I agree with mike and I don't understand the meaning and the use case of comment 2. That was the reason why I asked bug reporter.
(In reply to Mike Kaganski from comment #6) > ...which might be perfectly reasonable in a correctly designed template So you agree with WF, adding a comment field to styles, in favor of writing the comments into the template?
(In reply to Heiko Tietze from comment #8) > So you agree with WF, adding a comment field to styles, in favor of writing > the comments into the template? No, I agree with this proposal making perfect sense, having comments in *styles*, stored in templates.
Not much concerns from my side, the organizer tab should have enough space for these information. I wonder, however, where to show it to the end user. Are they supposed to "edit" the style in order to learn how to use? An idea might be to show the description as tooltip in the Stylist. That requires to keep it short.
No further input, so do it.
(Not really about "Writer comments", changing to "Writer styles" meta bug 107326.)