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 702066 - VHDL: Bad HTML formatting when using inline sources
VHDL: Bad HTML formatting when using inline sources
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: build
1.8.4
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2013-06-12 09:52 UTC by lahmson
Modified: 2013-08-23 15:04 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
wrong format due to inline sources (86.51 KB, image/jpeg)
2013-06-12 09:53 UTC, lahmson 		  Details
VHDL test source file (1.34 KB, text/x-vhdlsrc)
2013-06-12 09:57 UTC, lahmson 		  Details
fixed the </div> and the source comment bug (3.27 KB, patch)
2013-06-16 07:40 UTC, mk 		none Details | Review

Description lahmson 2013-06-12 09:52:05 UTC 
When the .ini parameter INLINE_SOURCES is set to YES, the HTML format of the architecture reference gets corrupted.
I looked into the HTML file and noticed that after every source code block, an additional </div> is inserted in the HTML code that causes every following member (usually processes) to belong to a hierarchically higher div. Simply deleting these </div> results in a correct formatting.
In the screenshot you can see 3 process descriptions and the wrong placement of the second and third one. They are aligned correctly when I disable inline sources.
Comment 1 lahmson 2013-06-12 09:53:14 UTC 
Created attachment 246598 [details]
wrong format due to inline sources
Comment 2 lahmson 2013-06-12 09:57:50 UTC 
Created attachment 246599 [details]
VHDL test source file

I used this file to create the doxygen output.
Comment 3 mk 2013-06-16 07:40:57 UTC 
Created attachment 246925 [details] [review]
fixed the </div> and the source comment bug
Comment 4 Dimitri van Heesch 2013-06-16 08:08:27 UTC 
Thanks, I'll include the patch in the next GIT update.
Comment 5 Dimitri van Heesch 2013-08-23 15:04:30 UTC 
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.