https://bugs.documentfoundation.org/show_bug.cgi?id=164487
--- Comment #4 from tmacalp <[email protected]> --- (In reply to Mike Kaganski from comment #3) > (In reply to tmacalp from comment #2) > > 1. Comment 2 is unrelated to this bug. After testing the attached documents, you're correct that my described behavior should probably be its own report. > 2. Comment 2 is not a bug. The behavior implemented in Writer is defined in > Unicode Standard Annex #14 [1], which explicitly specifies, that "when the > last character measured for fit is before the space character, any number of > space characters are kept together invisibly on the previous line and the > first non-space character starts the next line". > > [1] https://www.unicode.org/reports/tr14/#SP Mike, thanks for the link to the unicode definition. That does indeed explain the unintuitive(at least to me) behavior of normal spaces never breaking. That definition doesn't say how the word processor should handle visible formatted space characters. Nor does it mention whether to show trailing formatted space characters that are before/after the margin. * MS Word shows the characters up to the margin (pre-LO7.5 behavior) * Google Docs hides all trailing formatted space characters(you can't even create trailing lines with underlined spaces) * LO is now inconsistent, showing trailing formatted space characters, but only until they cross the margin, then it hides all of them. I'll report this as another bug. -- You are receiving this mail because: You are the assignee for the bug.
