We are trying to transform the current XML of our manuals to the DITA structure.
In our documentation we use a so called 'spare parts list', in which each part that can be used in a machine, has a number and a description.
Our manauls for several machines contain some of the parts which are declared in the above mentioned parts list.
In our current XML of the manual, we refer to the parts, declared in the 'spare parts list'.
How can we implement this in a DITA structure?
What are DITA Utilities?
Various tools, mostly free, that will enhance your productivity with DITA.
DITAVAL generation utility by Joe Gelb of Suite Solutions. (Free - requires username and email)
DITA Debugging tools written in PHP by Dick Johnson of VR Communications. (Free. Click to download zipped file.)
WinAnt is an interface to the Ant build utility, developed by Tony Self of HyperWrite Consultancy and Training. (Free. Click to download an exe file.)
What are plugins? Plugins are extensions to the Dita-OT code that add or modify functionality. Although plugins are often used to add specializations to the Dita-OT, they can also be used to simply override processing logic for standard elements. This allows users to customize the logic of the system without actually changing the code in the Dita-OT installation. In many cases, plugins can be carried over to an upgraded version of the OT and still run properly.
Contributed open-source plugins.
We are trying to transform the current XML of our manuals to the DITA structure. I'm not sure if this is the right place to ask some help for our transformation.
In our documentation we use a so called 'spare parts list', in which each part that can be used in a machine, has a number and a description.
Our manauls for several machines contain some of the parts which are declared in the above mentioned parts list.
In our current XML of the manual, we refer to the parts, declared in the 'spare parts list'.
Traditional transformation approaches -- such as XSLT scripts -- that ensure a specific look and feel to your published documentation are often difficult and costly to develop, and equally expensive to maintain.
New from SiberLogic, SiberSafe Styler offers a simple, fast, and cost-effective alternative that enables non-technical users to control the look and feel of their output and that can be used with any XML CMS or without one at all.
