The Document Type Association preferences panel is opened from menu .
Document Type Association preferences panel
The following actions are available in this preferences panel:
- Change framework directory location - Specifies a custom frameworks folder from where Oxygen loads the document types.
- User roles - Selects between two user roles: Content
author and Developer. When the selected role is
Content author, you can modify only the properties of the
Document Type Associations stored in the user preferences. The
externally stored associations (that means all the built-in document types) cannot be
modified and you must duplicate them to further customize these associations. The
Developer user can change any document type association.
- Document types table - Presents the currently defined document type
associations. The columns are:
When expanding a Document Type Association its defined rules are
presented. A rule is described by:
- Namespace - Specifies the namespace of the root element from
the association rules set (any by default). If you want to apply the rule only
when the root element is in no namespace, leave this field empty (remove the
ANY_VALUE string).
- Root local name - Specifies the local name of the root element
(any by default).
- File name - Specifies the name of the file (any by
default).
- Public ID - Represents the Public ID of the matched
document.
- Java class - Presents the name of the class which is used to
determine if a document matches the rule.
- New - Opens a dialog that allows you to add a new association. New
association is added to top of document type list.
- Edit - Opens a new dialog allowing you to edit an existing
association.
- Delete - Deletes one of the existing association.
- Up - Moves the selected association one level up (the order is
important because the first document type association in the list that matches the document
will be used).
- Down - Moves the selected association one level down.
- Enable DTD/XML Schema processing in document type detection - When
this option is enabled, the matching process also examines the DTD/XML Schema associated
with the document. For example, the fixed attributes declared in the DTD for the root
element are analyzed also, if this is specified in the association rules.
If you are
writing DITA customizations, it is recommended to keep this checkbox enabled. DITA topics
and maps are also matched by looking for the DITAArchVersion attribute in
the root element. If the DTD is not processed on detection, then this attribute specified
as default in the DTD will not be detected on the root element and the
DITA customization will not be correctly matched.
This option is enabled by
default.
- Only for local DTD's / XML Schemas - When the previous feature is
enabled, you can choose with this option to process only the local DTD's / XML
Schemas.
This option is enabled by default.