https://bugs.documentfoundation.org/show_bug.cgi?id=155494
V Stuart Foote <vsfo...@libreoffice.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |102345
--- Comment #28 from V Stuart Foote <vsfo...@libreoffice.org> ---
(In reply to Heiko Tietze from comment #26)
> (In reply to V Stuart Foote from comment #25)
> > ...for what *purpose* do we allow this text to extend "dangling" outside a
> > paragraph...
> We follow the example of Microsoft blocking the abuse of spaces to indent
> the line, I guess. Can you answer the question what purpose multiple spaces
> have?
>
> (I mean it in a positive sense, both views might be valid.)
Well, none really--and why they should be *easily truncated* (i.e. MS's
centering behavior) to facilitate other means of object alignment.
But *when present*, they should behave like any other "printing" character for
the font in use--wrap at margins.
And this of course is not just the U+0020 instance. Rather that all Unicode
whitespace within text spans be handled the same. E.g. a run of U+0020 and a
run of U+00A0 should get the same handling--wrap at margins. They don't
currently.
Not to be confused with handling on document canvas of NPC--e.g. the zerowidth
joiners, RTL/LTR marks, or the Pilcrow paragraph markers that can extend beyond
margins.
Referenced Bugs:
https://bugs.documentfoundation.org/show_bug.cgi?id=102345
[Bug 102345] [META] Formatting marks (aka Non-printing characters) bugs and
enhancements
--
You are receiving this mail because:
You are the assignee for the bug.
