<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - FORMATTING: make line end (shift enter) work the same as paragraph end with last line setting 'left' for alignment justified" href="https://bugs.documentfoundation.org/show_bug.cgi?id=68486#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - FORMATTING: make line end (shift enter) work the same as paragraph end with last line setting 'left' for alignment justified" href="https://bugs.documentfoundation.org/show_bug.cgi?id=68486">bug 68486</a> from <a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> Mike Kaganski</a> <pre>What is the *intended* use case for the line break? It's often used as a means for moving a word to next line (e. g. to keep with next word) without actually breaking paragraph. One could argue that non-breaking space should be used for that - but NBS has a property being fixed width, while normal space widens in justified alignment, so the line break in some cases is inevitable here to achieve good formatting. IMO, the feature specifically exists for augmenting the automatic line break (when its results don't satisfy user), maybe especially in case of hyphenated paragraphs. In this case, the justification of the broken line should not change. OTOH,it's often used in lists, to add a non-numbered intermediate "paragraph". And it's a bad usage, as there exists a dedicated unnumbered entry. Which is fully suitable for the task (unlike the previous case). There exist many documents, that would break if this is implemented.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>