| Title: | Online Bookbuilding |
| Notice: | This conference is write-locked: see note 1.3. |
| Moderator: | VAXUUM::UTT |
| Created: | Fri Aug 12 1988 |
| Last Modified: | Mon Jul 15 1991 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 440 |
| Total number of notes: | 2134 |
Maybe you folks can help me find what is the best way to manage "book
versions" in a production type environment. I am with sales support,
and working with a customer who is looking to go into full production
using DECwrite to create their own internal "BOOKREADER" documentation.
They will have many contributing writers and are looking for some input
on how to best manage the situation. What products or tools do we use
internally for the creation/revision control of our books?
Any input is greatly appreciated.
Thanks, Mark
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 436.1 | try QUEEN::DECWRITE | VAXUUM::UTT | Mary Utt | Tue Jun 25 1991 14:31 | 8 |
This notes conference is devoted to online bookbuilding problems and
issues using VAX DOCUMENT. Most writers in CUIP use VAX DOCUMENT and
also use CMS to control source files (i.e., versions). I'm not exactly
sure what your question is, but possibly this inquiry is better
suited to QUEEN::DECWRITE where writers using DECwrite can describe
how they manage book versions.
Mary
| |||||
| 436.2 | Thanks | SANFAN::BATESON_MA | Tue Jun 25 1991 17:30 | 2 | |
Okay, Thank you...
Mark
| |||||