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

combine.xslt indent attribute should probably be set to "no" (Origin: bugzilla #640742) #4116

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

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

On 2011-01-27 17:26:16 +0000, Ray Lefuel wrote:

The Doxygen XML output is formatted so that indent="no" but, in combine.xslt, indent="yes".

If you were to use a tool that can interpret indent="yes" such as Saxon9 (Note: xsltproc automatically assumes indent="no"), the combined XML output is altered from the original Doxygen-generated XML output.

For example, I have the following sample code preformatted in the original Doxygen-generated XML output:

// Descriptive text. NewConfig nc; nc = conn.prepareConfig(); nc.run(); nc = conn.prepareConfig(sample.txt); nc.run();

If indent="no", the Doxygen-formatted text is preserved as-is. If indent="yes" (and you don't use xsltproc), the text is altered to the following format in the combined XML file:

    <preformatted>

// Descriptive text.



NewConfig nc;


nc = conn.prepareConfig();
nc.run();


nc = conn.prepareConfig(sample.txt);
nc.run();

I recently switched from xsltproc to Saxon9. After running xsl transformations on the combined output, extra white-space and hard breaks were found in the final doc output. I'm currently overwriting the Doxygen-created combine.xslt prior to running Saxon9 on it; I now get the same results as I did with xsltproc.

On 2011-01-29 13:10:08 +0000, Dimitri van Heesch wrote:

I'll set the indent to no.

On 2011-03-28 14:19:28 +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.

@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