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

@par leads to eclipse help problems due to an </b> without <b> in html output (Origin: bugzilla #672472) #4626

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 build for ---
Reported in version 1.8.0 on platform Other
Assigned to: Dimitri van Heesch

On 2012-03-20 14:40:09 +0000, Jochen Sauer wrote:

The keyword par leads to an additional into the

and
block.
Example:
@Par author: JochenS
leads to:

author:
JochenS

This severity is set to normal, because if you use the html output in combination with the eclipse help toolchain, the help server will not accept the additional (not well formed) and is not displaying the help file at all..
It works perfect in the 1_5_6 version, but there is no eclipse support there.

Workaround a:

  • Use 1.8.0 Version to generate the eclipse support
  • Use 1.5.6 Version to build the Helpfiles.

Workaround b:

  • Use grep to remove the from the html-files

On 2012-03-20 22:18:10 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2012-04-02 22:56:54 +0000, Travis wrote:

I've run into what appears to be the same issue, but wanted to note that in my case @Par was breaking the HTML output when I attempted to load it in Chrome (tested broken in FF11.0 and IE9 as well) due to the unpaired tag and my use of the .xhtml extension option for IE svg compatibility.

Should you be running into the issue from this side, setting the extension back to .html will allow you to open the pages.

On 2012-05-19 12:26:35 +0000, Dimitri van Heesch wrote:

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