TheDrop
25th Jan 2001, 23:09
Implementing JAR OPS, we are using MS Word for this. This is a question about revisions on different pages. Our JAR OPS manual has the mandatory given chapters, and it has been divided into 22 Word sections (some of the 14 chapters are divided into more sections). In the footer of each page is the revision number and the page number, amongst other information, like the title of the chapter, company name etc.
BUT, as the footer (and also header, as well as watermarks) are the same in the entire section, changing the revision number on one single page, changes the revision number on all other pages in the same section. This means, that changing a single page could imply changing the entire chapter - maybe 20 or 30 pages, then chapter 0 (currently 22 pages!) will need to be revised, as it contains the current revision list, so all these 22 pages must also be updated. And this is not possible, as all revised pages must show what changes are made, so changing an entire chapter will make it impossible for the user to track what changes are actually made ...
I have not been able to find a fix for this. All I can think of is dividing the 200+ pages into equally 200+ sections, with "continue pagination from last section" on all pages except when the pages really must start from number 1 again, as they do now in the present 22 sections.
So tell me, what else is there to do ? Is it impossible to do this in MS Word ? Is it possible in other word processors, like Adobe Acrobat ? If yes, is it a hassle to convert from Word to Adobe, as we have our revision "ORG" all finished and approived ?
The optimal word processing for us would (in addition to what Word 97 already does) automatically take care of
* Indexing, both normal index and alphabetic sorted index (less important)
* Revisions, including automated revision list
* Revision functions like "Print all pages changed since last revision" or "Print all pages of revision 004". Also, it should be able to print a current OPS manual at any time, with all pages on latest revision and the revision index updated.
* Insertion of extra pages would allow for page ie 11A, 11B etc, so page 12 and forward need not be changed because of renumbering.
* Optional line unique for each page, where change comments can be made if necessary, ie "Updated according to JAR OPS change" or whatever comment might be appropriate.
Please someone help - I am sure we are not the only company experiencing this problem ...
BUT, as the footer (and also header, as well as watermarks) are the same in the entire section, changing the revision number on one single page, changes the revision number on all other pages in the same section. This means, that changing a single page could imply changing the entire chapter - maybe 20 or 30 pages, then chapter 0 (currently 22 pages!) will need to be revised, as it contains the current revision list, so all these 22 pages must also be updated. And this is not possible, as all revised pages must show what changes are made, so changing an entire chapter will make it impossible for the user to track what changes are actually made ...
I have not been able to find a fix for this. All I can think of is dividing the 200+ pages into equally 200+ sections, with "continue pagination from last section" on all pages except when the pages really must start from number 1 again, as they do now in the present 22 sections.
So tell me, what else is there to do ? Is it impossible to do this in MS Word ? Is it possible in other word processors, like Adobe Acrobat ? If yes, is it a hassle to convert from Word to Adobe, as we have our revision "ORG" all finished and approived ?
The optimal word processing for us would (in addition to what Word 97 already does) automatically take care of
* Indexing, both normal index and alphabetic sorted index (less important)
* Revisions, including automated revision list
* Revision functions like "Print all pages changed since last revision" or "Print all pages of revision 004". Also, it should be able to print a current OPS manual at any time, with all pages on latest revision and the revision index updated.
* Insertion of extra pages would allow for page ie 11A, 11B etc, so page 12 and forward need not be changed because of renumbering.
* Optional line unique for each page, where change comments can be made if necessary, ie "Updated according to JAR OPS change" or whatever comment might be appropriate.
Please someone help - I am sure we are not the only company experiencing this problem ...