Document Types > Porting Document Types > Importing a DTD and an Instance without Arbortext Architect
Importing a DTD and an Instance without Arbortext Architect
Follow this method if you have some XML documents in Arbortext Editor, but the document types have not been set up on any Arbortext Editor system, or if you have only a DTD (the .dtd file) and possibly a document instance (an .xml file).
Although you can create a document type from the DTD information, it is not recommended that you use Arbortext Editor without a FOSI specification. Arbortext Editor is designed to operate with a FOSI specification. Without a FOSI specification no formatting is implied or assumed and the resulting document will have no visual representation of the structure. The DTD structure, however, is still valid but the document will be awkward to read or edit. Consequently, the creation of a FOSI specification is highly recommended. A FOSI specification can be created by using Arbortext Architect.
To create a document type in this circumstance, import the DTD and instance files and compile the DTD.
To import a DTD and an instance without Arbortext Architect:
1. Make sure the catalog path points to the user's document types.
2. Create a user catalog file in the doctypes directory if one does not already exist. If there already is a catalog file in the user doctypes directory, create the entries needed for that document type and add them to the existing user catalog file (on Windows).
3. Recommended - Create a subdirectory for the added document type in the user doctype directory.
4. If the file format of the source files on the source machine is different than that of the target machine, and they are not automatically converted by the file transfer process, convert the source text files to the target file format. (On a PC, copy the document type specification (source) files to the new directory on the target PC for the added document type.)
5. Optional - Copy the document instance files (if any exist) to the PC.
6. Check the format of the DTD file to ensure proper import of the file.
7. Check the headers of document instances to make sure they are valid.
8. Compile the document type. See Compiling document types for details.