New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docbook output produces invalid XML for <programlisting> elements (Origin: bugzilla #700710) #5188

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component general for ---
Reported in version 1.8.4 on platform Other
Assigned to: Dimitri van Heesch

On 2013-05-20 12:52:44 +0000, Dean Camera wrote:

The 1.8.4 release of Doxygen generates invalid elements in some cases, resulting in an orphaned element inside the node. Sample validation error output:

struct_h_i_d___unit__t.xml:5: parser error : Opening and ending tag mismatch: para line 4 and programlisting
#include <HIDParser.h>

The issue appears to be at line 1174 of src/docbookgen.cpp:

if (!nm.isEmpty())
  t << "<para>" << endl;
  t << " <programlisting>#include ";
  if (ii->fileDef && !ii->fileDef->isReference()) // TODO: support external references
    t << "<link linkend=\"" << ii->fileDef->getOutputFileBase() << "\">";
  t << "&lt;" << nm << "&gt;" << "</link>";
  t << "</programlisting>" << endl;
  t << "</para>" << endl;

The opening item is conditionally generated if a file definition is present, however the closing is generated under all circumstances.

On 2013-05-25 13:59:16 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2013-08-23 15:04:41 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.5. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment