Invalid XML generated when using <list type="table"> in source. (Origin: bugzilla #640754)

[doxygen]

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

Original attachment names and IDs:

• sample.zip (ID 179467)

On 2011-01-27 19:37:41 +0000, Ray Lefuel wrote:

Created attachment 179467
Zip contains source, Doxygen-generated XML docs, Doxygen configuration file.

I use the tag in my code comments to create tables in my C# code. When Doxygen generates XML docs, it erroneously inserts and tags for every field, which results in invalid XML. You also get an error when you try to use xsltproc or Saxon9 to combine the files.

These are my source docs (Found in Sample.cs):

/**

This is a class.

Here is a sample table: Name Description Row1 Description1 Row2 Description2 Row3 Description3 Row4 Description4 Here is more text. */

This is the Doxygen-generated XML result with the strange and tags (Found in class_sample.xml):

Here is a sample table:

Name Description

Row1 Description1

Row2 Description2

Row3 Description3

Row4 Description4

This is the error that Saxon9 reports when I try to combine files:

Error on line 84 column 32 of class_sample.xml:
SXXP0003: Error reported by XML parser: The element type "para" must be terminated by the
matching end-tag "".
Recoverable error on line 11 of combine.xslt:
FODC0002: org.xml.sax.SAXParseException: The element type "para" must be terminated by the
matching end-tag "".

Currently, I run a python script post-generation to strip all the and tags from table structures; this seems to be the only way I can combine the XML files successfully.

I've attached my Doxygen configuration settings and the other applicable files.

On 2011-01-29 19:15:16 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2011-03-28 14:19:31 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.4. 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.