DeltaXML Support Forums

• Home
• Products
  • Products Overview
  • Core
    • About Core
    • FAQs
    • Demos
  • Sync
    • About Sync
    • FAQs
    • Demos
  • Competitors
• Services
• Applications
  • Applications of DeltaXML
  • Publishing
  • I.T.
  • Aerospace
  • Financial
  • Government
  • Telecoms
  • Education
  • OEM
  • Content Management
• Customers
  • Customer List
  • Endorsements
• Partners
• About Us
• Contact Us
• Support and Resource Library
  • Support Overview
  • Support Forums
  • Technical Document Index

DeltaXML Support Forums

new topic  post reply	DeltaXML Products and Applications -> DeltaXML Core -> DITA pipelines
moderators: chrisc nigelw tristanm

DITA pipelines
jrhooker Joined: 15-April-2008 Posts: 23 Location: , Canada	Posted: 18-July-2008 23:05 Are there any plans for creating a DITA pipeline similar to the ones available for Docbook? If not, I need to start scoping the difficulty of creating one myself. Thanks, Jeff.
No immediate plans for DITA support
nigelw Joined: 27-March-2007 Posts: 54 Location: Malvern, United Kingdom	Posted: 22-July-2008 15:59 Hello Jeff, I have very little knowledge of DITA myself, so I needed to consult some colleagues on this. Are there any plans for creating a DITA pipeline similar to the ones available for Docbook? We have had surprisingly little demand for this so we have no immediate plans.  This may be because of the concept of small topics, with perhaps less need to track changes. As you say, the pipeline would be similar to that for DocBook. DITA has similar support for marking changes though we have not verified that the publishing pipelines that generate XSL-FO (or HTML) from DITA are able to handle these correctly - this is important because alot of our DocBook work involved adding revision-flag support to docbook-xsl fo output).  Using DeltaXML to add the revision flag support to the comparison pipeline was the easier part! For DITA, there will be some additional complexity due to specialization. This means that to produce a solution for a defined specialization would be easier than writing a general solution for any specialization (for example specialization could be used to remove the ability to highlight change: the equivalent of removing d:phrase from a d:para in docbook). If not, I need to start scoping the difficulty of creating one myself. I would suggest looking at the far end of the pipeline/toolkit first and then looking at any comparison filters. Hope this helps, Nigel
jrhooker Joined: 15-April-2008 Posts: 23 Location: , Canada	Posted: 23-July-2008 18:49 Indeed. I'm a DITA neophyte myself, but our CMS vendor is a native DITA shop and has offered to foot the bill of converting our Docbook content to DITA to avoid having to customize their product's configuration to handle Docbook. It's intriguing to us since we'd targetted DITA as our eventual destination anyway. Our Docbook rollout was driven by time contraints and preexisting knowledge of Docbook. I'm going to have to look into change marking in DITA. Can't believe that the mechanism would be that much different from Docbook's.

new topic  post reply

To find out about new replies to this post as they occur please subscribe to one of these feeds:

moderate