https://bugs.documentfoundation.org/show_bug.cgi?id=121369
Heiko Tietze <tietze.heiko@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |libreoffice-ux-advise@lists
| |.freedesktop.org
Summary|group styles in sidebar |Group Header and Footer
| |styles together at the
| |hierarchical view
Status|UNCONFIRMED |NEW
Blocks| |102946
Ever confirmed|0 |1
Severity|normal |enhancement
--- Comment #1 from Heiko Tietze <tietze.heiko@gmail.com> ---
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.
Addressee, Complimentary Close, Sender, Signature (this needs discussion!)
could be moved into "Letter".
Horizontal Line, Frame Content are also very special, related to "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.
Referenced Bugs:
https://bugs.documentfoundation.org/show_bug.cgi?id=102946
[Bug 102946] [META] Styles bugs and enhancements
--
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.