Description: I noticed problems when copying text from Writer to Thunderbird, which is already described in this issue: https://bugs.documentfoundation.org/show_bug.cgi?id=114501 As I never changed the default style of Writer I never noticed that when hitting enter it creates paragraphs, not line breaks. I do not consider this good. By default there should be a clear way to differentiate between the two. I searched for similar issues. These were my search terms: * summary:paragraph summary:space|summary:spacing|summary:style * summary:paragraph "new line" By the way: Are these bugs index-able by Google? Steps to Reproduce: - Actual Results: - Expected Results: - Reproducible: Always User Profile Reset: No Additional Info: -
(In reply to Tobias from comment #0) > ... Invalid, LO (and OOo era) default behavior for the <Enter> to render a new Paragraph object is correct. If you need line breaks, that is correctly achieved by <Shift><Enter> > I do not consider this good. By default there should be a clear way to > differentiate between the two. > There is. This is visually exposed on document canvas with the "Toggle Formatting Marks" <Ctrl><F10> (customizable as UNO .uno:ControlCodes). Each discrete Paragraph will be end marked with a pilcrow (U+00B6), each Line break/continuation will be end marked by a newline (U+21B5). Those visual marks are not searchable, but the reqular expressions "$" or "\n" can be used to locate using the <Ctrl>+H Find dialog.
I am not complaining about the default behaviour of enter being paragraphs. That's fine. I think you mis-closed this issue. Yeah, you can manually enable some way that shows you differences between paragraphs and new lines, but in what world does it make sense to start a new paragraph directly below the previous by default, so it looks like a simple linebreak? Without any indication? I think this should not be silenced without further discussion by one person.
There is no issue here, and OP seems to be asking for a change in function that <Enter> generates a line break rather than long established default that a New Paragraph object is instanciated. IMHO, nothing that needs improvement/enhancement and a clear => WF
(In reply to Tobias from comment #2) > I am not complaining about the default behaviour of enter being paragraphs. > That's fine. > > I think you mis-closed this issue. Yeah, you can manually enable some way > that shows you differences between paragraphs and new lines, precisely, if you need the differentiation you can easily add a visual queue > ... but in what > world does it make sense to start a new paragraph directly below the > previous by default, so it looks like a simple linebreak? Without any > indication? > Because we deal in Open Document Format document model. Paragraphs are a base element of the model. Working in paragraphs is the norm. > I think this should not be silenced without further discussion by one person. Fine pushed it onto the UX-advise pile.
Text processors structure content in paragraphs and Thunderbird/HTML does the same. Depending on the paragraph style you get 0.1"/0.25cm below for "Text Body" (which comes after headings and should be the default for empty documents as well; there is a ticket). This spacing distinguishes it clearly from line breaks with zero spacing. Similarly to what TB does with HTML mails. The "Default paragraph style" has zero spacing making it look like no breaks are used (except from the white space at the line ending). So do we need to change the "Default paragraph style"? It has a lot of consequences starting with the need to update all documents for ui testing (we compare on each build whether the exported document look like what was created before as prototype - and we have a lot of these documents to ensure pixel-prefect results). It's just not worth the effort.