The Document Type Directory
A directory must be created for each document type when adding document types to your system.
Although not required, it is common to create a separate directory that has the same base name as the document type files. For example, if the specification files are mytype.style, mytype.dcf, and mytype.dtd, a subdirectory might be called mytype. As an example,you could place the files in Arbortext-path\custom\doctypes\mytype.
|
|
Applications may use other directories specifically designated for graphics, entities, command language routines, and the like. These directories hold optional components for documents. The organization is determined by the document designer or site administrator. If directories for application components reside on another machine, set the user's appropriate paths to access them using Arbortext Editor preferences or environment variables.
|
You can load a custom document type automatically at startup by using the Arbortext-path\custom\doctypes directory. The \custom\doctypes path is automatically prepended to the catalog path, after any subdirectories of the custom\doctypes directory that contain a catalog file. Putting custom document types in custom\doctypes or in subdirectories of it makes them automatically available, avoiding additional steps to add them to the catalog path.
At the highest level of the custom directory is a file named custom.xml. This file is only used when you have a custom document type in the custom\doctypes subdirectory, and you have not designated a category name for the document type in the associated document type configuration (.dcf) file’s NewDialog element. In this case, the name in the custom.xml file’s Name element is used as the Category name for the document type(s) in the custom\doctypes subdirectory in the New Document dialog box.
