Arbortext Command Language > Commands > check_completeness
  
check_completeness
check_completeness [ -full] [output=outspec]
This command checks whether all the components that are required by the DTD are present. If elements are missing, it provides a listing of problems and supplies missing elements where the fix is unambiguous.
* 
If you have applied an alias map to the document, the element names in the panel are aliases.
It also checks for ID references for undeclared or multiply-defined IDs. In addition, it checks for mismatches for text IDs, such as saving text to a counter ID. By default, this command checks those parts of a document that have changed since a previous completeness check including file entities. If the -full option is specified, the entire document is validated including any SUBDOC file entities (SUBDOC is a rarely used SGML feature). If a document is saved and exited with its status incomplete, the next completeness check done on the document defaults to -full.
outspec can be any of the following:
The name of a file (this can be a complete path name). A right angle bracket (>) preceding the file name causes the result of the check_completeness command to be appended to the end of the file.
A question mark (?) preceding the output file name. If the file name starts with a question mark, the file name is a variable name whose value is set to the output produced by the command. If the second character is a right angle bracket (>), the output is appended to the current value of the variable instead of replacing it.
An exclamation point (!) preceding an output specifier. This suppresses the normal prompt to confirm overwriting an existing file.
cc is a synonym for check_completeness.
Examples
cc
cc -full
Related Topics
doc_incomplete function