Description: Using LO 25.2.4.3 now, I find a bad bug: I use c for character(s) and n for no-break-space(s) here: In older versions I cold write something like: cccccccccccccc ccccccccccccc cccccccc nnnnnnnn, If the line ended, so I got: cccccccccccccc ccccccccccccc cccccccc nnnnnnnn, Now I get: cccccccccccccc ccccccccccccc cccccccc nnnnnnnn , while nnnnnnn is invisible out of the "paper" and which is absolutely not, what should a no-break-space do. Older documents of mine do trouble now!!! In new documents I also get that (using t for tab): ccccccncccccccccctttttttttttttttttttttttttttttttttcccnnnn nnnnnccc I think, the linebreak should be between the tabs, not between NO-BREAK-spaces!!! Btw. - also the no-break-spaces are shown otherwise than before - now quite ugly with blue ringlet instead of a gray space before. Also it seems, the width of the no-break-space increased. (?) Steps to Reproduce: write words (characters, c) a short before the end of the line some no-break-spaces (n) followed by , or . Actual Results: cccccccccccccc ccccccccccccc cccccccc nnnnnnnn , (while nnnnnnn is invisible out of the "paper") Expected Results: cccccccccccccc ccccccccccccc cccccccc nnnnnnnn, Reproducible: Always User Profile Reset: No Additional Info: Older documents of mine do trouble now!!! In new documents I also get that (using t for tab): ccccccncccccccccctttttttttttttttttttttttttttttttttcccnnnn nnnnnccc I think, the linebreak should be between the tabs, not between NO-BREAK-spaces!!! Btw. - also the no-break-spaces are shown otherwise than before - now quite ugly with blue ringlet instead of a gray space before. Also it seems, the width of the no-break-space increased. (?)
Please attach a sample file, reduce the size as much as possible without private information, and paste the information in Menu/Help/About LibreOffice, there is a copy icon.
Created attachment 202340 [details] odt-file containing examples screenshots will follow
Created attachment 202341 [details] screenshot no 1
Created attachment 202342 [details] screenshot no 2
Created attachment 202343 [details] screenshot no 3
[Automated Action] NeedInfo-To-Unconfirmed
(In reply to Werner from comment #3) > Created attachment 202341 [details] > screenshot no 1 Note for others wondering: the blank before the period and "ignored" is due to the Aufgabe style having first line indent of -0,60 cm. I bibisected with linux-64-6.2. The no-break spaces started disappearing when wrapping to the second line in commit 4bb28ad217ea9d6511b6921dcd3d28328edcb4d6 tdf#120677: restore treatment of blanks in SwTextGuess::Guess Let's ask Mike what he thinks.
If this will be restricted only to > I use c for character(s) and n for no-break-space(s) here: > In older versions I cold write something like: > > cccccccccccccc ccccccccccccc cccccccc nnnnnnnn, > > If the line ended, so I got: > > cccccccccccccc ccccccccccccc cccccccc > nnnnnnnn, > > Now I get: > > cccccccccccccc ccccccccccccc cccccccc nnnnnnnn > , > > while nnnnnnn is invisible out of the "paper" and which is absolutely not, > what should a no-break-space do. then I'm inclined to consider this as a real regression. The problem with tabs is pre-existing, and must be considered separately. And "quite ugly" look of NBSP is (1) separate, (2) opinionated, and (3) IIRC, configurable. Decide on resolution.
(In reply to Mike Kaganski from comment #8) > If this will be restricted only to > > > I use c for character(s) and n for no-break-space(s) here: > > In older versions I cold write something like: > > > > cccccccccccccc ccccccccccccc cccccccc nnnnnnnn, > > > > If the line ended, so I got: > > > > cccccccccccccc ccccccccccccc cccccccc > > nnnnnnnn, > > > > Now I get: > > > > cccccccccccccc ccccccccccccc cccccccc nnnnnnnn > > , > > > > while nnnnnnn is invisible out of the "paper" and which is absolutely not, > > what should a no-break-space do. > > then I'm inclined to consider this as a real regression. Sure let's focus on this.
https://gerrit.libreoffice.org/c/core/+/198882
Mike Kaganski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/e3c068cb190e6cf04a49f9984f984d5ef72f9d9a tdf#167946: reimplement the fix for tdf#120677 It will be available in 26.8.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.