This whole thing has the feel on none linear functions gone out-of-order
wrong.
That is to say, there are two or more functions that can apply to
organize placement of images within a document.
Initially, they start at the same time, within the tolerance of the
processor/motherboard. The more they function, the more they get out of
sync until it can't complete in the way we wish, but do complete as a
process.
Some get less failure and others get more.
What is the order of priority and how does it restart on failure? Does
one wait before doing another?
Any thoughts?
On 9/8/2016 12:59 PM, Bo Siltberg wrote:
I too have that book on the reading list, it's been there for too long now..
As I show in the other thread, the image problem does not seem to be
(solely) related to "large" documents as I could reproduce one kind of
error in a one-page document.
Otherwise I guess a document can be as large as it need to be and still be
manageable. There is for example a difference in need between a book
written from top to bottom and a large technical specification which is
updated here and there and that contains internal references back and
forth. It was quite some time since I evaluated the master document
function, maybe it has evolved now to handle navigation and references
better than in the past?
2016-09-08 16:51 GMT+02:00 Tim---Kracked_P_P---webmaster <
webmaster@krackedpress.com>:
On 09/07/2016 11:02 PM, Bruce Byfield wrote:
On September 8, 2016 01:40:46 AM Wiebe van der Worp wrote:
<snip>
You might also want to take the time to download my book (which is free)
and ready the chapter on frames. It represents my best thinking on this
problem, offering two different approaches, neither of which is
completely satisfactory:
http://designingwithlibreoffice.com/download-buy/
On the whole, the table solution is the most flexible, but having lots
of tables does increase the file size.
Thanks fro the reminder of the book link.
I downloaded it and forgot about it. I have not had a chance to do more
than a fast look through.
Thanks for your work on this book, as well.
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-uns
ubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be
deleted
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- Re: [libreoffice-users] Page formatting in writer goes nuts (continued)
Re: [libreoffice-users] Writing large or complex documents · Philip Jackson
RE: [libreoffice-users] Writing large or complex documents · toki
Re: [libreoffice-users] Page formatting in writer goes nuts · Bo Siltberg
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.