G
Guest
I have a large number (500+) of small files that I want to use to generate a
set of manuals (80). There is redundancy between the manuals so working with
source files allows me to edit a sourcefile ONCE and have the changes
reflected in ALL the manuals where that source file is linked.
I have tested with nesting of both text and images and all works fine.
(There's a quirk in the TOC generation but I'll address that later).
The problem I have is that I need to have SMEs (subject matter experts)
review the final manuals and they can't be burdened with all the linking
"overhead". They need a file that they can redline using Word's "track
changes" feature, period.
The linking system I briefly describe here is based on a solid structure to
organize the source files that the SMEs don't have access to.
Here's the question: In the final manuals, how do I convert all links and
fields to embedded text or images?
set of manuals (80). There is redundancy between the manuals so working with
source files allows me to edit a sourcefile ONCE and have the changes
reflected in ALL the manuals where that source file is linked.
I have tested with nesting of both text and images and all works fine.
(There's a quirk in the TOC generation but I'll address that later).
The problem I have is that I need to have SMEs (subject matter experts)
review the final manuals and they can't be burdened with all the linking
"overhead". They need a file that they can redline using Word's "track
changes" feature, period.
The linking system I briefly describe here is based on a solid structure to
organize the source files that the SMEs don't have access to.
Here's the question: In the final manuals, how do I convert all links and
fields to embedded text or images?