DITA Preferences

The DITA category in the Preferences dialog box sets the following preferences for DITA documents:

• DITA Resource Manager — Provides the following preferences for the Resource Manager dialog box:

◦ Hide element IDs — Determines whether the ID option is displayed on the New Topic tab and whether IDs are displayed in the Resource Manager browser.

◦ Insert preview link text — Determines whether preview text from the link target is inserted and displayed in the Arbortext Editor window for DITA xref and link tags.

◦ Warn when inserting more than: xx objects — Determines whether Arbortext Editor displays a warning dialog box when more than a designated number of topic references are being inserted into a DITA map in a single operation.

◦ Automatically place new relationship table entries into correct column — Determines whether a topic reference entered into a DITA relationship table through drag-and-drop is automatically put into the table column that matches the DITA topic type.

The default is on. If you uncheck this option, the topic reference is put into the column where the reference is dropped.

◦ Check referenced documents for errors during completeness check — Determines whether the enhanced completeness checking for DITA documents opens referenced documents and performs the enhanced check on them as well as the current document.

◦ Show key reference user interface — Determines whether the user interface options for keys and key reference support are displayed in the Arbortext Editor interface.

◦ Include maps in Resolved Document for Editing view — Determines whether the markup for DITA maps is included in a resolved document for editing.

By default, only DITA topics are included the resolved document. This option has no effect when you are using a custom document type for the resolved document for editing. The default is off.

◦ DITA References — Specifies the list of directories to search to locate content referenced from DITA documents.

The DITA references path is used when a reference is not specified as either an absolute path name or a path name relative to the current document directory. The DITA references resolved by this variable include topic references, content references, links, cross references, and any other DITA element that references content. The only exception to this are graphic references, that are resolved using the graphics path.

The initial setting is the value of the APTDITAPATH environment variable if set. Otherwise, it defaults to the Arbortext-path\doctypes\ditamap\ditamapsample directory. Separate each directory in the DITA references path by a semicolon. You can use symbolic parameters in the DITA references path.

The document directory and the base URI for the current element, if different, are included by default before any directories on the DITA references path to resolve relative references. When any set ditapath directory parameter is set to a value of %^, the document directory and the base URI for the current element will not be included when searching for graphics. Only the paths specified will be searched.

◦ Default language for new documents — Determines the default language to which Arbortext Editor sets the value of the xml:lang attribute on the root tag of DITA maps and topics created from templates.

Note that this only affects templates that do not already have xml:lang set when a new document is created. If this preference is not set to a value, then the default language of the stylesheet associated with the document is used. If the default language of the stylesheet is en, then the system locale is used. The default is (System Locale) meaning this preference is empty or not set.

The drop-down list for this preference contains the following special values:

▪ (Default Stylesheet Language) — Indicates to use the default language of the stylesheet associated with the document.

Following these values is a list of language codes. If the language code you want to add is not in the list, you can enter the desired code in the option. However, note that Arbortext Editor does not check to see whether an entered code is valid.