Paul Johnson wrote:
[...]
There are no show-stopping problems for me, but a few little problems.
Even though each chapter setup indicates that it has a master
document, and I *thought* Lyx would get a pre-amble from that master
document, it appears to have no effect when I look at chapters. I want
LyX uses the preamble of the document for which you issue the
print/export command. Print the master, and the master preamble is used.
Print a chapter alone, and the chapter preamble is used.
This is sometimes necessary, for example if you make a book that is a
collection of parts that you also print freestanding.
ragged-right output, and it appears necessary to put the \RaggedRight
stuff in every chapter preamble. When I view chapters by themselves,
they do not inherit the preamble of the master document. So I end up
copying the whole preamble from the master document into each chapter.
Boring.
LyX could be improved with some master/subdoc commands, such as
"copy master preamble to all subdocuments" and "import preamble from
master".
Also, it is a problem that Chapter numbering is not correct when you
work on chapters by themselves. There is an easy fix to set the
chapter counter in ERT at the top of the document, but it is a bit of
a pain.
I wrote a book with chapter subdocuments. This was never an issue
because I didn't use those numbers much while writing. All references to
page numbers are automatic, so they are automatically correct when the
final print is done.
When communicating with the publisher, they might say things like "fix
the typo on page 4". But then I knew what document they were referring
to. Getting the numbers "right" in the beginning wasn't interesting
because later additions to chapter 1 would shift the rest of the numbers
anyway.
Another problem I notice is that it is tedious to experiment with
different document settings when working on separate chapters. If the
main document, the one that has all the includes, is KOMA script, but
then a chapter is just regular book, then when you use LyX to try view
the whole document, you will get a lot of warnings about child
documents of different types every time you view.
Yes, but the warning doesn't matter unless the child document uses
features that aren't in the master class. In that case you have trouble
anyway.
Perhaps it'd be more user-friendly to have a document setting checkbox
with "inherit settings from master document". Check that, and the child
document settings are all greyed out and the master document consulted
when printing (and when LyX decides what class-specific paragraph types
to show in the user interface.) the child document could even be stored
without other settings than this checkbox and the master reference.
Helge Hafting
