| Patti,
I think we have ancountered a similar problem concerning HIDE_TAG errors.
A new DOCUMENT user on our system coded a COMMAND section as follows:
<COMMAND>(ADD Command (UDU))
<OVERVIEW>
Authorizes and assigns login displays to ACMS users by adding UDU
definitions to the ACMSUDF.DAT file. You can use qualifiers to assign
login displays or let new definitions receive information from the
DEFAULT definition.
<ENDOVERVIEW>
<FORMAT>
<SYNTAX>
ADD user-name
<EMPHASIS>( Command Qualifiers Defaults)
/[NO]AGENT From DEFAULT definition
/MDB=menu-database-file From DEFAULT definition
/MENU[=menu-path-name] From DEFAULT definition
/[NO]DISPLAY_MENU From DEFAULT definition
<ENDSYNTAX>
<ENDFORMAT>
<ENDCOMMAND_SECTION>
Ignoring for the moment that they should be using the QUAL_LIST tags,
this code results in the errors:
%TAG-W-DUPHIDNAM, at tag <HIDE_TAGS> ...
A <HIDE_TAGS> tag is reusing the hide-name, _MATH_TAG_
%TAG-W-DUPHIDNAM, at tag <HIDE_TAGS> on line 11 ...
A <HIDE_TAGS> tag is reusing the hide-name, _HEADER_LEVEL_TAGS_
%TAG-W-NOTHIDNAM, at tag <REVEAL_TAGS> on line 24 ...
A <REVEAL_TAGS> tag is referencing an unknown hide-name, _MATH_TAG_
%TAG-W-NOTHIDNAM, at tag <REVEAL_TAGS> on line 24 ...
A <REVEAL_TAGS> tag is referencing an unknown hide-name, _HEADER_LEVEL_TAGS_
It seems that the errors come from the <SYNTAX> nested inside the <FORMAT>.
However, I only deduced that after a lot of trial and error.
Is this nesting illegal? If so, I suggest an error message be generated
that says so. (It would make debugging much easier.) Actually, we would
prefer if it *wasn't* illegal, because we will need <SYNTAX> for
complex diagrams in reference sections.
Thanks,
--Andrew Gent
|