https://bugs.documentfoundation.org/show_bug.cgi?id=121369
Cor Nouws <cno@nouenoff.nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cno@nouenoff.nl
--- Comment #4 from Cor Nouws <cno@nouenoff.nl> ---
(In reply to andreas_k from comment #0)
are Inherit from Default Style so there is no Subgroup Footer and Header. I
propose to define an Group
+ Footer and Header ##new
could be done.
(In reply to Heiko Tietze from comment #1)
Header and footer styles belong to the "Special Styles" category together
with some unrelated options. So calling the newly to be introduced category
Special makes no sense. But we could label it "Document Structure" and add
also Endnote and Footnote.
Endnote and Footnote are not document structure.
Addressee, Complimentary Close, Sender, Signature (this needs discussion!)
could be moved into "Letter".
Horizontal Line, Frame Content are also very special, related to "Drawing".
Frame content drawing ?
So ultimately we organize the tree by the different use cases. But I wonder
also if all styles are needed. In particular the mentioned header and footer
styles are identical.
They are used at different places in Page styles, so definitely functional.
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 121369] Group Header and Footer styles together at the hierarchical view · 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.