<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Introduce a comment style" href="https://bugs.documentfoundation.org/show_bug.cgi?id=103064#c18">Comment # 18</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Introduce a comment style" href="https://bugs.documentfoundation.org/show_bug.cgi?id=103064">bug 103064</a> from <a class="email" href="mailto:philipz85@hotmail.com" title="Yousuf Philips (jay) <philipz85@hotmail.com>"> Yousuf Philips (jay)</a> <pre>(In reply to Thomas Lendo from <a href="show_bug.cgi?id=103064#c15">comment #15</a>) > I agree that only a small set of features should be available for comments. > As working much with comments, I really only need font, strong > emphasis/emphasis and simple list features in comments. (Font because the > default comment font changed somewhere in the past and I don't want comments > with different fonts in a document. -- I simulate lists with "* Blabla" now.) We should likely decide what the optimal font size is for comment and not allow users to change it. We default to 10pt, MS Word uses 8pt, and Google Docs uses Arial 10pt. > I think there should be a paragraph style for all comments in a document > with a small set of paragraph features available and very limited direct > formatting if any. Use cases like in <a href="show_bug.cgi?id=103064#c5">comment 5</a> need more than one paragraph > style for different notations with various paragraph features. The only thing i'd put into a comment paragraph style would be the font name and allow users to change it, so its not repeated in each character style. In <a href="show_bug.cgi?id=103064#c5">comment 5</a>'s use case, I would suggest that a user can apply an existing document-level character style to a comment, but it would be a limited set of formatting options, and it wouldnt overwrite whatever default font size that are assigned to comments. > Before implementing a style there should be a consent of what features we > want to be available in Writer comments and subsequently in other LibO > components too. Yep we should do this. If we have a look at the formatting all comments character dialog, i'd say we should keep, font name, font style, underlining, strikethrough, overlining. (In reply to Luke Kendall from <a href="show_bug.cgi?id=103064#c16">comment #16</a>) > Please note that it's extremely helpful to have font sizes supported, as > comments can get very long, and reducing the font size is a good way to make > more of them visible without having to click into them and scroll about, > only able to see a small window onto it. That would be the wrong way to fix the issue of long comments. See <a class="bz_bug_link bz_status_NEW " title="NEW - Improvements to comments look and function" href="show_bug.cgi?id=89232">bug 89232</a> for the discussion on how to improve that issue. > You might also consider whether you could reuse the existing code for > editing and display of text, from the full writer, rather than having to > implement a separate text editor and text display algorithm. The current implementation gives similar text editing features that are available in textboxes, as doing comments like text in full writer would be overkill.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>