The rules for the properties file format match the ones specified in the JavaDoc documentation of the java.util.Properties
class (please see the documentation of the load
method: http://docs.oracle.com/javase/7/docs/ap ... tStream%29
I do not see any problem in the way you specified the value for the webhelp.skin.css
parameter (assuming that the file with that path exists on your local disk).
I have tried to specify a different skin for the WebHelp output using a similar setup and the skin set in the properties file did reflect in the output HTML pages.
Can you test using one of our predefined skins? For example use the Forest skin:
Code: Select all
urbanrobots wrote:Here's an example of what I'm trying but that's unsuccessful...
What is the exact problem that you are facing? Does the transformation end with an error? Or, it finishes successfully but the the custom skin isn't applied?
As a side note, I have noticed that you are using the fix.external.refs.com.oxygenxml
parameter. Do you have references in your DITA map that are outside the map's directory?
urbanrobots wrote:Dfix.external.refs.com.oxygenxml = true
The name of the parameter is prefixed with the "D"
character which may come from the fact that, in the command line, you can set a property using the following syntax:
However, please note that this parameter, takes effect only when the DITA OT transformation process is started from Oxygen XML Editor. If the DITA OT process is started from the command line the parameter is not supported (please see the parameter description in our User Guide: https://www.oxygenxml.com/doc/versions/ ... sic_output