https://bugs.documentfoundation.org/show_bug.cgi?id=93970
--- Comment #27 from Luke Deller <luke@deller.id.au> ---
(In reply to V Stuart Foote from comment #12)
Yes, unclear why/how we have formatted multi-line Heading with a negative
indent for first line.
I did some digging to understand this. The old behaviour actually makes sense
when outline numbering is enabled: it means that the indent of the second line
will align with the heading text on the first line, taking into account that
the first line starts with a number followed by a tab stop before the heading
text begins.
I can also see that the default back in early 1996 was to have outline
numbering enabled, from some old German comments in revision 84a3db80 of
sw/source/core/doc/number.cxx
Also, there is some weird juxtaposition in editengine
in that the successive HEADING levels increase the base line of the indent.
That doesn't seem correct either.
This increase in the indent amount makes sense when fully-qualified (dotted)
section numbering is used. For example a level 3 heading may have a dotted
number like "5.1.7", and deeper levels have even more dots, so they need more
room for the numbering. I guess that such numbering used to be the default.
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 93970] Writer: default Heading styles 1 - 10 defined with negative indent for first line, results in odd multi-line Heading formats · bugzilla-daemon
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.