Revision file

The process option UPDREV produces an update file containing a copy of the new source text with revision tags delimiting the changed text lines.

The UPDREV process option is available for LINE and WORD compare types.

UPDREV supports two different types of revision tags, one for SCRIPT/VS files and one for BookMaster® files. (Use the REVREF process statement (Revision code reference) to specify which type of revision tag you want.)

Figure 1 shows a SuperC UPDREV file with SCRIPT/VS revision tags (.rc on/off).

Figure 1. Example of a UPDREV update file for SCRIPT/VS documents

.rc 1 &vbar.
.rc 1 on
This line is reformatted; the spacing in the "new" file differs.
.rc 1 off
This line is the same in both files.
.rc 1 on
This line differs from the text in the "old" file.
.rc 1 off
This line is the same in both files.
.rc 1 on
This line is in the "new" file, but not in the "old".
.rc 1 off

When the UPDREV update file in Figure 1 is processed by SCRIPT/VS, the final scripted output has "|" revision characters in the left margin of the output document identifying the changed lines (those between the SCRIPT/VS revision tags .rc 1 on and .rc 1 off).

Note: The revision character ("|" in the example in Figure 1) can be specified either by using a REVREF process statement (see Revision code reference) or by having a SCRIPT/VS .rc. revision tag as the first record in the new file. Subsequent changes to the source can therefore be separately identified by using different revision characters.

Figure 2 shows a SuperC UPDREV file with BookMaster revision tags (:rev/:erev).

Figure 2. Example of a UPDREV update file for bookmaster documents

This line is reformatted; the spacing in the "new" file differs.
This line is the same in both files.
This line differs from the text in the "old" file.
This line is the same in both files.
This line is in the "new" file, but not in the "old".

When the UPDREV update file in Figure 2 is processed by BookMaster, the final formatted output has the revision character associated with the revision ID abc (as specified by a :revision. BookMaster tag in the new input file) in the left margin of the output document identifying the changed lines (those between the BookMaster revision tags :rev and :erev).

Note: The revision ID (abc in the example in Figure 2) is controlled by the REVREF process statement (see Revision code reference). Subsequent changes to the source can therefore be separately identified by using different revision IDs (which are associated with unique revision characters).