After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 681135 - incorrect HTML formatting between @code and @endcode
incorrect HTML formatting between @code and @endcode
Status: RESOLVED NOTABUG
Product: doxygen
Classification: Other
Component: build
1.8.1.2
Other All
: Normal critical
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2012-08-03 13:28 UTC by Nicolai Otto
Modified: 2012-08-03 14:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Nicolai Otto 2012-08-03 13:28:08 UTC 
In V 1.8.1.1 and 1.8.1.2 the code between @code and @endcode tags is not formatted correctly for HTML output. There is no indentation, font is arial. Only color coding is correct.

When analyzing the HTML we found an additional CSS class (called "line") which is not part of the default CSS file. The section between @code and @endcode is correctly embedded into a div of class "fragment". But then again each line is embedded in a div of class "line" which isn't defined and will kill formatting.

A similar issue has been reported in another forum here: http://stackoverflow.com/questions/11091545/extraneous-html-in-doxygen
Comment 1 Dimitri van Heesch 2012-08-03 14:05:26 UTC 
Hi Nicolai,

The 'line' class is part of the default doxygen.css since revision 814, as you can see here:
http://doxygen.svn.sourceforge.net/viewvc/doxygen/trunk/src/doxygen.css?view=log
A fix was made in revision 817 for empty lines, but this fix is included in releases 1.8.1.1 and 1.8.1.2 already.

Please check if you are not using a custom stylesheet that needs updating.
Please attach a self-contained example (source+config file in a tar or zip) that allows me to reproduce the problem in case it still does not work.
Comment 2 Nicolai Otto 2012-08-03 14:21:41 UTC 
Understood - turns out the problem was an outdated custom CSS file. Sorry for the false alert.