Creating a Custom Document Type
Important Notes
-
All custom doctypes are located in the
/doctypes/customfolder. -
Each document type dependencies should be placed in a single folder within the custom folder.
-
A catalog file within each doctype folder should be created that references each DTD/schema. This catalog file can be created with the ACL script noted in the Referencing Arbortext Document Types section.
-
A master catalog file should be created in the custom folder that references each doctype catalog file.
Troubleshooting Document Types
Document Type configurations are highly complex and sometimes it can be a challenge to get them correct. If you run the sync job, and see errors indicating Titania Sync was unable to find a dtd, ent, or xsd file, then the first thing to check is the document type. Make sure the ACL script noted above was executed, and the result was saved to the custom catalog. It is usually a good idea to not have too many levels of file referencing. For example, one catalog can have an entry <nextCatalog catalog=“custom/catalog.xml”/>, and each catalog could reference another. We recommend flattening all the custom catalog entries as much as possible.
In the case of schema’s, the ACL script may not generate all the necessary references. It is usually a good idea to review the catalogs in your Arbortext custom folder, if you see errors indicating Titania Sync is unable to find an xsd file, and pull in any entries that look like the following example.
<public publicId="urn:ptc:names:arbortext:dita:xsd:techinfoMod.xsd" uri="file:///F:/TitaniaSync/bin/doctypes/custom/Arbortext%20TechInfo/techinfoMod.xsd"/> <public publicId="techinfoDomain.xsd" uri="file:///F:/TitaniaSync/bin/doctypes/custom/Arbortext%20TechInfo%/techinfoDomain.xsd"/>