Hi Daniel,
I'm afraid that both the line numbering feature and the inserted callouts feature are both implemented as Java extensions in Xalan and Saxon, and won't work with xsltproc.

I understand your quandary about needing xsltproc's XInclude feature as well. One solution is to process the XIncludes with xmllint to create a temp file, and process the temp file with Saxon with extensions to get the callouts or line numbers.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
[EMAIL PROTECTED]


----- Original Message ----- From: "Daniel Leidert" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, February 26, 2007 5:54 PM
Subject: [docbook-apps] callout-lists and HTML/PDF creation with xsltproc/libxslt


Hello,

When I try to process a <screenco> or <programlistingco> element with
xsltproc to output HTML, it works, except that the numbers in the
<screen> or <programlisting> area are missing [1]. If I now try to
create FO output using the docbook-xsl stylesheets and xsltproc, it
fails. Are the FO-stylesheets only behind the HTML stylesheets or are
there problems with callouts for FO-output, that cannot be solved
without a special extension?

My problem is, that I would like to comment some screen-output, but the
linenumbering attribute needs an extension, libxslt does not provide,
and the PDF output seems to fail for callouts and shows the explained
problem for HTML. But I cannot use Saxon or Xalan, because Xerces seems
to miss support for xpointer(), which I need for some includes (system
is a Debian Sid).

[1] If I process the docbook-defguide with xsltproc, it produces the
correct output for the screenco-example - if I process the
screenco/example1.xml alone, it shows the same problem - the numbers are
missing in the <screen>-area.

Regards, Daniel


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to