DITA and XMetaL Discussion
XMetaL Community Forum › DITA and XMetaL Discussion › Command-line webhelp build
-
cdybdahl February 26, 2010 at 6:36 pm
Command-line webhelp build
February 26, 2010 at 6:36 pmParticipants 1Replies 2Last Activity 13 years agoI have a need to automate the build of multiple versions of webhelp, but before this can happen, I need to be able to build a single version from the command line successfully.
I am using this call after running startcmd.bat from XMetaL's toolkit directory:
java -jar lib/dost.jar /i:”C:wsdlwsdl_map.ditamap” /transtype:webhelp /outdir:C:wsdlwebhelp_out /basedir:”C:Documents and Settings%USERNAME%Application DataSoftQuadXMetaL SharedDITA_OT” /ditadir:”C:Documents and Settings%USERNAME%Application DataSoftQuadXMetaL SharedDITA_OT”This generates the navigation but fails to copy the individual HTML files over, so that each page in the help system gives a “page cannot be displayed” error.
XML source files are getting copied over into temp, but they are either not being transformed at all or there's some problem writing them to the output directory. Are there some additional/changed parameters I need to be passing to make this work?
cdybdahl March 2, 2010 at 3:10 pm
Reply to: Command-line webhelp build
March 2, 2010 at 3:10 pmSo, is this just not possible?
Derek Read March 2, 2010 at 7:34 pm
Reply to: Command-line webhelp build
March 2, 2010 at 7:34 pmIt is possible but not something I am able to take the time to document unfortunately. It is not something we have tested and also not something that is officially supported at the moment.
XMetaL Author Enterprise does everything w.r.t. DITA OT at the command line. This is the file that drives that process if you wish to try to decipher it:
C:Program FilesXMetaL 6.0AuthorDITAXACssharedrenditionsprint_dita142.xml
XMetaL Author Enteprise includes a basic set of customization files (DTD, CSS, CTM and some simple macros) for editing these types of XML files, so you can open it in the product to view it. Currently this customization is used only by our developers, which is why it is not documented and making changes to it are not officially supported. Basically the stuff you need to look at is in the
sections. -
AuthorPosts
- You must be logged in to reply to this topic.