I agree, Brian, that one generally need need to worry about style
precision in subdocuments, since the master document controls the final
output. That's the beauty of the master document process. It's almost
LyX-like in its execution (what you see is what you /mean/).
But, I sense that the way Dale is creating his "faux headers" in his
subdocuments, he needs an accurate wysiwyg display on each page of each
subdocument, which would, of course, require that each subdocument have
styles that exactly match those of the master document so that, while
he's editing, he can have total comfort that the final output will be as
he's created it.
So, instead of looking at this as a possible bug (which it isn't),
perhaps pursue a feature request to have a Field that would pick up the
first and last words of each page. Then he could put just the field in a
true header and have the perfect solution.
Virgil
On 3/25/2014 2:31 AM, Brian Barker wrote:
At 23:26 24/03/2014 -0500, Dale Erwin wrote:
... the instructions for creating a master document. First you
create a template which has all the styles defined in it. Then the
master document and all subdocuments are created from this template.
The only problem is that if changes to any style becomes necessary,
I've not found any way to make the changes in one place and have them
take effect in all files which were already created before the
changes were made.
I don't think you generally need to do this. It's surely not
important to be able to see any such changes in the subdocuments: what
matters is only how the final (master) document appears. If your
structure is right and you change the styles in the master document,
you should have all that you need.
Up to now, I've had to make such changes in the template as well as
in each file which has already been created from the template.
Unless you are going to create further subdocuments (and possibly not
even then), there is no point in changing the template, I think. But
if you do, you get a chance to update documents created from the
template to use any modified styles when you next open those
documents, so you should not need to make changes "as well as in each
file" - only perhaps to open those files, accept the offer, and
re-save them.
I trust this helps.
Brian Barker
--
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] Master Documents, Office Suites, and the Underwood (continued)
- Re: [libreoffice-users] Master Documents, Office Suites, and the Underwood · Kracked_P_P---webmaster
- Re: [libreoffice-users] Master Documents, Office Suites, and the Underwood · Brian Barker
- Re: [libreoffice-users] Master Documents, Office Suites, and the Underwood · Steve Edmonds
- Re: [libreoffice-users] Master Documents, Office Suites, and the Underwood · Kracked_P_P---webmaster
- Re: [libreoffice-users] Master Documents, Office Suites, and the Underwood · Virgil Arrington
- Re: [libreoffice-users] Master Documents, Office Suites, and the Underwood · Wolfgang Keller
- Re: [libreoffice-users] Master Documents, Office Suites, and the Underwood · Tom Davies
Re: [libreoffice-users] Master Document · Brian Barker
Re: [libreoffice-users] Master Document · Dale Erwin
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.