DITA support Limitations
For the current release, the Arbortext Editor DITA support has the following limitations:
• The following limitations apply to content references (conref and conkeyref):
◦ You cannot change the text of a content reference, either through editing or operations such as spell checking and find/replace. You must edit the source of the content reference to change the text.
Note that a content reference suppresses the existing content of the element the reference is replacing. You can use Arbortext Editor to edit the existing content. You can see the existing content if you deselect > . The underlying element will be displayed as fallback in publishing if the content reference can’t be resolved.
• The spell checking and find/replace operations do not search the content of attributes. Misspellings and other content problems might be missed in DITA text attributes, such as title, and navtitle.
|
|
DITA has deprecated the title, and alt attributes and recommended against using the navtitle attribute for this reason. The use of title, navtitle, and alt elements is recommended.
|
• You can use the props and base attributes directly and as a basis for specialization, but fallback processing of attributes and specialization from generalized attributes is not supported.
• The DITA index-sort-as element is not supported for published HTML Help and RTF outputs.
• When you have multiple index-see and index-see-also elements for a single indexterm element, extra index entries may occur in published Web output.
• The chunk attribute on the topicref element is not supported. Chunking for Web and HTML Help outputs is currently based on the division information included in Arbortext Styler stylesheets.
• The PTC Server connection is supported for accessing DITA documents stored in a content management system (CMS). Using the default burst configuration files distributed with Arbortext Editor, the PTC Server connection is not aware of metadata stored in a DITA document. You can customize those configuration files to support storing metadata from DITA documents directly in the CMS.
