Fekete Róbert wrote:
Otherwise, you can do it with profiling, and assign a condition to
the abstract that does not get fulfilled, but for this you have to
modify your build environment somewhat. Bob's book describes both
methods in detail: http://www.sagehill.net/docbookxsl/index.html
I believe profiling is what I was looking for.
I can get things to do what I want via command line (--stringparam
profile.audience "none").
Is there a way to include that profile via a processing instruction (or
something else) in the XML DocBook its self?
The only time that the abstract (hidden element) will be used is when it
is directly XIncluded via XPointer.
Grant. . . .
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
