Editor variables in WebHelp footer files for DITA
Posted: Tue Jun 02, 2015 9:10 pm
Environment:
Oxygen 17
DITA source
DITA-OT 1.8 (the one included in the Oxygen installation)
Windows 7 OS
We need to get a part number and build date into the footer of our WebHelp builds.
The ${date} editor variable would work for the build date. The Edit Parameter dialog for the webhelp.footer.file parameter says editor variables can be used in the footer file, but it's not clear to me how to include them so they resolve. I tried adding the variable to the HTML code in the footer XHTMLfile:
When I run the transformation, the editor variable is not resolved; it is output as a literal value. I also tried setting the editor variable directly as the value of the field, but that did not work either. Can anyone point me to a working example? None of my searches have located an example or clear instructions for this use case.
I'm not sure what to do for the part number. We don't want to have to update the footer file each time we run a transform, nor do we want to update a custom editor variable each time. The ideal solution would be to use the value of the <bookpartnumber> element in the bookmap, but I have not seen anywhere that it is passed through to the WebHelp output so it could be consumed. Can we get this value without custom processing?
Oxygen 17
DITA source
DITA-OT 1.8 (the one included in the Oxygen installation)
Windows 7 OS
We need to get a part number and build date into the footer of our WebHelp builds.
The ${date} editor variable would work for the build date. The Edit Parameter dialog for the webhelp.footer.file parameter says editor variables can be used in the footer file, but it's not clear to me how to include them so they resolve. I tried adding the variable to the HTML code in the footer XHTMLfile:
Code: Select all
<body>
<div>${date(yyyy-MM-dd)}</div>
</body>
I'm not sure what to do for the part number. We don't want to have to update the footer file each time we run a transform, nor do we want to update a custom editor variable each time. The ideal solution would be to use the value of the <bookpartnumber> element in the bookmap, but I have not seen anywhere that it is passed through to the WebHelp output so it could be consumed. Can we get this value without custom processing?