Hi Janice,
Since some FO customizations do work and not others, the current issue has two probable causes:
- The most likely cause is that there is a docbkx parameter setting, or worse, an undeclared _default_ parameter setting, that is overriding your custom TOC template. The docbcx documentation is atrocious in general, but is worse than atrocious in declaring what parameters they set for you. You can get a list of those by running Maven in debug mode, which emits far too much information. Among that info is a long list of every single DocBook XSL parameter that docbkx sets as it prepares to build the Webhelp, with the value assigned to each. I saved a copy of that list somewhere and will e-mail it to you privately.
- An unlikely cause is the order in which your customized templates are read in your FO customization file. In the XSL, one XSL file calls another, which calls another, and so on, and all this happens in a certain well-defined order. Your custom templates _should_ always overlay and replace the default templates of the same name, but sometimes one customized template inadvertently overrides or cancels another in the same layer. Thus, sometimes rearranging the order of templates in your customization layer makes a difference.
Best of luck, Barton Wright
Unfortunately not anytime soon, since it was chosen for easy integration with the product build.
I've been able to make several customizations in the FO XSL file that do work, so it seems to be a bit hit or miss.
|