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 646002 - htmlonly content appears in generated XML output
htmlonly content appears in generated XML output
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.7.4
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2011-03-28 19:17 UTC by Ray Lefuel
Modified: 2015-12-30 10:19 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ray Lefuel 2011-03-28 19:17:36 UTC
The Doxygen docs state that the \htmlonly tag starts a block of text that will be verbatim included in the generated HTML documentation only.  However, the content appears in the generated XML documentation, too.  It is encased in <htmlonly> and </htmlonly> tags.

Shouldn't the content be ignored altogether as it's being generated?

Also, in the Doxygen docs, the link to the \endhtmlonly topic under the \htmlonly topic doesn't work.
Comment 1 Thomas Martitz 2015-08-12 09:10:09 UTC
I can confirm this. Any resolution on the horizon?
Comment 2 albert 2015-08-12 10:56:06 UTC
According to the documentation the @htmlonly (and other *only marked documentation) should not appear. For the other output formats this works.

I've just pushed a proposed patch (pull request 381) to github.

In case the old behavior should be maintained, i.e. in the xml file also the other *only documentation should appear, the documentation of the different commands has to be adjusted and I think it would be better that the code inside e.g. <htmlonly> .. </htmlonly> (etc.) should be placed in CDATA constructs to overcome possible incorrect XML code resulting from the other *only constructs.
Comment 3 albert 2015-08-31 16:37:07 UTC
Code has been integrated in github
Comment 4 Dimitri van Heesch 2015-12-30 10:19:01 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.11. 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 (preferably in the form of a self-contained example).