Troubleshooting DITA
DITA problems you may encounter
Differences between Content Delivery 5.0 and Content Delivery 5.1
- A bookmap publication that worked in Content Delivery 5.0 may fail to upload in 5.1. Due to an error in the DITA DTDs, Content Delivery 5.0 allowed a
<bookmap>element to have a@titleattribute. That was a violation of the DITA 1.1 specification but erroneously allowed by the DITA DTDs. Content Delivery 5.1 uses the DTDs provided with DITA 1.2, and will disallow the@titleattribute. Therefore, uploading a bookmap with this attribute will fail. In order to resolve this issue, you should modify your data to use the<title>element or the appropriate specialization per your data.
Unexpected browser behavior
- With conref pushreplace, extra space shows up before the list item in the Chrome browser. Other browsers are okay.
Variations from DITA 1.2 Specification
- With conref pushreplace, it is illegal to replace a more specialized element with a more general one. For instance, you cannot replace a <step> element with a <li> element. Content Delivery 5.1 does not check for generalization errors. The target element may disappear without replacement.
- With conref pushreplace, it is an error for two source topics to replace the same element. Content Delivery 5.1 does not check for this error.
- With conref pushbefore or pushafter, content gets pushed when different element types are used for pushbefore and mark elements. DITA requires that these be elements of the same type.
- The behavior of conref pushreplace in maps is unspecified. The DITA Technical Committee, in their dita-users forum, states "the use of conref of any form within maps is frowned upon" because there are better alternatives for use in maps.