https://bugs.documentfoundation.org/show_bug.cgi?id=89082
pehache.7@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |UNCONFIRMED
Ever confirmed|1 |0
--- Comment #6 from pehache.7@gmail.com ---
@Heiko Tietze : anchoring at the page is definitely not an option : depending
on the flow, there can be some conflicts between two (or more) frames to occupy
the same place. e.g. a paragraph at the bottom of page N with a frame anchored
at the top of the page N, and on the next page N+1 a paragraph at the middle of
the page with a frame anchored at also the top of the page N+1. If the whole
text flow is shift down (by inserting some text in the previous pages, then the
first paragraph may move to page N+1, while the second may be still on page N+1
: the frames would overlap on page N+1.
I have really investigated all possible positioning/anchoring options, and
really none of them correspond to the behavior I described (which can be found
in FrameMaker or Latex)
The best solution so far has been proposed by Jean-Baptiste Faure, but still
it's more a workaround than a proper solution.
@V Stuart Foote : may be a solution for desktop publishing, but not for word
processing with long documents (100+ pages)
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 89082] FORMATTING: improving text+frames flow · 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.