Help > Authoring > Dialog Boxes > Edit Window > Tools Dialog Boxes > Compile Document Type Dialog Box
  
Compile Document Type Dialog Box
The Compile Document Type dialog box displays if you attempt to load an SGML document type that has not been compiled. (XML applications using non-XML-compliant markup can also be compiled using MarkIt. The dialog box contains the following options:
Document Type Path — Specifies the path of the document type that you want to compile. If you selected a document type from the Select DTD dialog box, this field will include the path and file name of the selected document type. Click the Browse button to select a document type.
Top Level DTD Tag — Specifies the top level element for a document type. If this document type is unwrapped (no <!DOCTYPE wrapper), you must type the element name in this field. If the document type is wrapped, you do not have to specify this element; Arbortext Editor will automatically detect it.
SGML Declaration Path — Specifies the path to the SGML Declaration for SGML document types. If Arbortext Editor locates an SGML Declaration in the directory in which the document type is located, it will fill in the appropriate path. If Arbortext Editor does not find an SGML Declaration in this directory and you do not specify a path, Arbortext Editor will use the appropriate default. You can leave this field empty if you are compiling an XML document type. In Arbortext Editor, XML documents are compiled using predefined SGML Declaration values for XML. Click the Browse button to select an SGML declaration.
Catalog Path — Specifies the catalog path Arbortext Editor will use for compilation. You may specify additional catalog paths if you like. Use semicolons to separate multiple paths.
Application — Indicates whether the document type is an SGML or XML application.
Warnings — Indicates whether Arbortext Editor will Report or Ignore warnings. Warnings indicate problems that in many cases will not cause the compile to fail, but could cause problems when you use the document type. For example, a missing entity in the DTD would generate a warning, but, in many cases, the compile would succeed.
Arbortext Editor will always report errors, as errors indicate serious problems that cause the compile to fail.