#1278 manpages/docbook.xsl: broken xinclude breaks following conte

output: manpages
closed-invalid
nobody
XSL (1066)
5
2013-01-09
2012-12-28
No

Given the following input:

[bad-xpointer.docbook (text/plain, inline)]
<?xml version="1.0"?> <!-- -*- sgml -*- -->
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">

<refentry>
<refnamediv>
<refname>bad-xpointer</refname>
<refpurpose>
demonstrate handling of unresolvable
<sgmltag class="attribute">xpointer</sgmltag> values
</refpurpose>
</refnamediv>

<xi:include
xpointer="bogus-id"
xmlns:xi="http://www.w3.org/2001/XInclude" />

<refsection>
<title>Example section</title>
<para>Example paragraph.</para>
</refsection>
</refentry>
[Message part 3 (text/plain, inline)]
the command "xsltproc --xinclude
/usr/share/xml/docbook/stylesheet/docbook-xsl/manpages/docbook.xsl
bad-xpointer.docbook" [1] produces the following output file:

[bad-xpointer.1 (application/x-troff, inline)]
[Message part 5 (text/plain, inline)]
which is rendered more-or-less like this:

,----
| NAME
| bad-xpointer - demonstrate handling of unresolvable xpointer
| values <xi:include></xi:include>.SH "EXAMPLE SECTION"
|
| Example paragraph.
`----

[1]: non-Debian installations might require the command to be written as
"xsltproc --xinclude
http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl
bad-xpointer.docbook"

Discussion

  • Robert Stayton
    Robert Stayton
    2013-01-07

    I'm not clear what you are asking for here. A bad XInclude is a failed file at the parsing stage, so why is it a surprise that the output is broken?

     
  • True. This is non-sense. Closing.

     
    • status: open --> closed-invalid