@barniedo
I think you have no clear understanding about the various categories of documents that can be created from an author point of view.
There are at least two:
- text-oriented: main concern is contents (text) and author relies on the document processor to spread this text onto pages as needed
In this category, pages “do not exist”. They are allocated on demand. They can’t be duplicated. Only contents can and when pasted will cause new pages to be allocated.
An example of such a document is a novel.
- page-oriented: author requests on a specific layout where text has to be forced into this layout
Pages layout is so important that pages won’t be allocated automatically to handle overflow. Pages are allocated explicitly by author.
The second category is frequently named desktop publishing and is the realm of dedicated applications.
If your document is page-oriented (catalogue, RP document, advertisement, …), then Writer is not the best tool.
No. Writer has another approach to document management. Its founding principles are different. It can of course be used to do simple things (and even in a quick’n’dirty way) but I appreciate the tremendous power of these principles for my sophisticated documents.
I have no idea about the technology under the hood. I let this to the developers.
I fully agree. However, you must accept to spend some time to study the program. It took me a few years to develop a mental model of Writer (principles) to ease my daily use. In the end, the model is quite simple (a layered one) but it is explained nowhere.
Remember that the adoption of any tool require a readjustment. You can’t use it like you did with the previous one. When you switch from nails to screw, you don’t hit screws with the screwdriver, do you?