As the Darwin Information Typing Architecutre (DITA) gains wider acceptance as an XML standard for technical documentation, there has been increased activity towards interoperability with other standards, such as S1000D and SCORM, specialization for uses in specific industries, and adaptation for different use cases. Noteworthy is the current effort to adapt DITA for monolithic business documents other than technical documents. This adaptation opens the possibility for techdoc groups to implement DITA without requiring the paradigm shift to topic-based authoring.
I am trying to process javahelp output and was wondering if anyone had suggestions for good tutorials or general advice. I am using Arbortext Editor and Arbortext Publishing Engine to create the DITA bookmaps and create pdf and webhelp output. Unfortunately, Arbortext doesn't support javahelp builds, so I have downloaded the open toolkit and did the practice javahelp build. Any suggestions for hooking up Arbortext stylesheets and dtd files with the open toolkit would be much appreciated. Thanks!
By:
Don Bridges & Mikhail Vaysbukh
Data Conversion Laboratory
DITA is a hot topic in the 'Tech Docs' arena, and for good reason. DITA is an open standard that addresses many of the needs of technical documentation producers - most notably content reuse needs. The big question for many companies, once they've determined that authoring in this new standard would be beneficial for them, is what to do with the treasure trove of existing documents, known as legacy documents. Would they be useful converted into DITA, and is it worth the effort?
