Philippe Nobili wrote: > >> >> Yes, this is probably the case. I cannot help you much because I don't >> understand how works the DocBook profile XSL layer. That is, I can use >> it, but I don't understand how it is implemented. >> > > My apologies for coming back on this topic, we really need to get the > profiling working... From what I understand (I may be wrong), the > problem could come from the single-pass XSL transform that we use with > the profiling DocBook, leaving some unresolved references.
I've never heard about these two passes before today. I don't really see why two passes would be needed here: Excerpts of http://www.sagehill.net/docbookxsl/AlternateText.html --- Two-pass processing A separate stylesheet is available to perform just the profiling step, without also applying the DocBook style templates. The output is a filtered version of your original XML document, with the profiling conditions applied so that some elements are excluded. That profiling-only stylesheet is useful when your document contains xref or link which cannot be resolved with the single-pass processing, or if you are using an XSLT processor that does not support the EXSLT node-set() function. --- * Saxon supports the EXSLT node-set() function. * We use the profiling style sheets for our own needs without any problem and without the two-pass processing workaround. (Note that we use xi:include with parse="text" and not textobject/textdata.) * You've probably found a bug triggered by textobject/textdata processing. The best approach would be to fix it. * If you cannot or don't want to fix this bug, you may consider using xi:include with parse="text". In this case, Saxon and the XSL style sheets will just have to process a normal <literallayout> containing plain text. > > An alternative method would be to use a two-passes XSL transform: first > pass simply applies the profiling stylesheet to the original DocBook > document (xsl/profile.xsl stylesheet), the second pass run our XSL > customization on the resulting XML file, using the regular DocBook XSL. > > So, we will try to modify the stock xlsMenu.incl file to apply this two > pass XSL transform for all HTML/HTML-1 and PDF (.i.e. calling <transform > stylesheet="/> twice). Would you have an advice on how to achieve this > in cleany ? You need to replace the stock process commands by your own custom process commands (having the same name as the stock ones). How to do this cleanly is explained here: "Customizing an existing configuration" http://www.xmlmind.com/xmleditor/_distrib/doc/configure/customizing.html > > Again, thanks a lot, this will be the last message from us about this. No problem.
