Hi again

Found the workaround ...

1. Split the document into two - name the top part common_core.ott and the bottom part tail_xyz.ott

2. Ensure one blank line at the beginning of tail_???.ott before a manual page-break which begins the tail section. The blank line has to fit on the end of common_core.ott without throwing a page or you will get a blank page between the two sections.

3. At the beginning of the blank line at the top of the tail_???.ott Insert | Section | [x] Link and browse for common_core.ott

4. Save as original_filename.ott because it has exactly the same content except that the common core is now linked from a separate file common_core.ott in which changes get reflected in all documents which link to it.

5. That should leave tail_xyz.ott lying around to edit and provide the differences then get saved as tail_abc.ott before repeating step 3 and then saving as the new "abc" version with the common core.

Thanks OOo team for a fabulous product :)

Mike



On 27/04/2010 5:20pm, Mike Dewhirst wrote:
Hi

I have built a nice document template with varying page styles and I'm
happy with it.

Now I need to make it serve different purposes by way of chopping off
the original end then replace it from a choice of different ends.

This is what I'd like to do ...

1. Double-click the template to produce an untitled document

2. Adjust File | Properties | Custom Properties to name the particular
file to include as a different end

3. Refresh the Table of Contents

... and if it isn't expecting too much, I'd like the included bookmarks,
cross-references and special fields to be coherently populated across
the inclusion boundary.

I can understand this is a big ask - probably impossble. I just don't
want multiple copies of the main document lying around to maintain for
future changes.

Any hints or workaround advice would be greatly appreciated.

Thanks

Mike


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to