Date: prev next · Thread: first prev next last
August 2020 Archives by date, by thread · List index


https://bugs.documentfoundation.org/show_bug.cgi?id=107181

--- Comment #17 from Telesto <telesto@surfxs.nl> ---
What the extension in comment 3 does should ideally be build into LibreOffice.
Would make more workable; you have to follow by far more steps currently to get
it done (and be bit creative). This is great for customization; but less
conformable for quick and easy workflow. 

The extension is actually flawed in the sense that page number right means all
text is aligned right. Page number should be in a frame (or table) or something
like that (similar to what word does), so text can be but left and the page
number right.

See also bug 135751 (which I interpret as a request for this)

Hopefully not 'abusing this bug' as initial poster maybe had something
different in mind? I personally interested in the - build in - comment 3
functionality. It's but of silly having to use a extension for such type of
basic functionality (and not even working as someone would love to see it)


The header bar does make it possible to insert a numbering.. again without
formatting.. Ideally maybe some kind of template styles of different
header/footer formattings? For the most common header/footer layouts

@Heiko.. this kind of a idea.. you're mostly liking styles/templates?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Context


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.