Skip to content
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

Strange behavior when placing cite within brief. (Origin: bugzilla #684324) #4890

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

Comments

Projects
None yet
1 participant
@doxygen
Copy link
Owner

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2012-09-18 20:00:05 +0000, Jesper Brynolf wrote:

Created attachment 224665
An archive containing test.h, Doxyfile and testref.bib. Using this file to generate html and latex output illustrates the problem well.

I have been using the cite command together with brief within a few different doxygen comment context such as module, class, struct, function and typedef. The comments resides within C++ code.

Examples:

/**

  • \defgroup grp1 Group 1
  • \brief Foo bar see \cite report:FooBar
  • Detailed foo bar.
    */

And the result I get is that the cite and everything written after it in the brief ends up in detailed description section of the different contexts and it is no difference between the Latex and the HTML output.

On 2013-02-03 16:35:49 +0000, Jesper Brynolf wrote:

I have tested this with 1.8.3.1 on Ubuntu 12.10 and the strange behavior still remains.

On 2013-05-24 16:42:09 +0000, Jesper Brynolf wrote:

I have tested this with 1.8.4 in RedHat 5.6 and the issue still remains.

/**@brief See \cite report:FooBar
*

  • Detalied foo bar.
    */
    class FooBar
    {
    FooBar();
    virtual ~FooBar()
    };

This results in the following PDF

...
X.X FooBar Class Reference
See
X.X.1 Detailed Description
[1].
Detailed foo bar.

On 2013-05-30 19:32:16 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2013-05-30 19:33:46 +0000, Dimitri van Heesch wrote:

*** Bug 700788 has been marked as a duplicate of this bug. ***

On 2013-08-23 15:04:31 +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.

On 2013-09-16 17:19:44 +0000, Jesper Brynolf wrote:

Tested it with doxygen 1.8.5 on Xubuntu 13.04 and it worked perfectly.

@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
You can’t perform that action at this time.