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

JAVADOC_AUTOBRIEF=YES causes paragraphs to be concatenated. (Origin: bugzilla #631380) #3963

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 1.7.1-SVN on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2010-10-05 05:39:14 +0000, Timothy Landers wrote:

Created attachment 171738
Example C++ source and doxygen config.

There seems to be an inconsistency between detail sections produced with and without JAVADOC_AUTOBRIEF enabled.

When using the triple slash doc comment to supply a brief, enabling JAVADOC_AUTOBRIEF causes the first and second detail paragraphs to be concatenated.


/// Demonstrates inconsistent paragraph rendering.

/**
Paragraph One

Paragraph Two
*/
class ParagraphBug
{
};


Details will contain the erroneous text: "Paragraph OneParagraph Two"

No whitespace is preserved between the joined paragraphs irregardless of the amount of vertical whitespace provided.

Tested versions:
1.6.1
1.7.1-20100920 (SVN REV 742)

I've attached example files that can be used to reproduce this bug.

On 2010-10-06 19:13:43 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next release.

On 2010-10-09 08:19:36 +0000, Dimitri van Heesch wrote:

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