| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 617.1 | Looking for <UPDATE_RANGE> ? | IJSAPL::KLERK | Theo de Klerk | Thu Jul 09 1987 03:33 | 18 |
| There must be an automated way to do this, as the VMS kit maintainers
do it all the time...
The <UPDATE_RANGE>(start\endpage_no) will produce a file containing
only those pages (when the new text is longer, it will continue from
"endpage.1, .2, .3" etc).
But my question is: how can I know /make sure what's the first word
on the first odd page to be "reprinted"? (apart from looking at the
documentation). And how do I know that when a second update arrives
(and the first ones are merged as "ordinary" text).
If you could specify <START_UPDATE> and <END_UPDATE> and leave it to
Document the entire page which contains <START_UPDATE> upto and
including the one which contains <END_UPDATE>, that would be nice.
A wish for the next release?
Theo
|
| 617.2 | It isn't always reasonable to remake 6 copies of a 1000 page book | CAADC::PEREZ | The sensitivity of a dung beetle. | Mon Jul 13 1987 00:16 | 8 |
| I've also had people asking for this. We put out a document to
a customer and then need to make modifications. Rather than redoing
the entire document we would like to be able to provide that same
kind of "kit" that we receive internally for updated documentation.
How do we get Document to just do an updated TOC and those pages
with changes? It must exist since we get manuals this way.
Dave P
|
| 617.3 | <update_range> it is. | CLOSET::ANKLAM | | Sun Jul 19 1987 14:51 | 15 |
|
<UPDATE_RANGE> and <ENDUPDATE_RANGE> will, in V1.0, give you
a complete table of contents and index, not just contents and index
for the changed regions of the file.
However, you must still enter these tags manually (and you must
sometimes back up a few odd pages to start an update range in
a safe context; this is documented). The whole point is that
you are starting with a previously published book, so you have
hardcopy in front of you that guides you in setting the <update_range>
and <endupdate_range> tags.
patti
|
| 617.4 | Pointers to solution | KELLS::DONOHUE | | Fri Jul 24 1987 10:41 | 14 |
|
Under current baselevels (.06, .07, and .08) doing an update is
very time consuming as a number of operations are manual. These
include hard editing of TeX files. Jean Szymczak and I recently
completed two updates under BL07.
If you can wait to do the updates wait until you have V1. If not,
see Note 461 and the replies (Jean's reply with the process is .2.)
If you need any help or further information contact me or Jean
(SCOOTA::)SZYMCZAK. Good luck!
Jack Donohue
|