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

htmlonly content appears in generated XML output (Origin: bugzilla #646002) #4214

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

On 2011-03-28 19:17:36 +0000, Ray Lefuel wrote:

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 and 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.

On 2015-08-12 09:10:09 +0000, Thomas Martitz wrote:

I can confirm this. Any resolution on the horizon?

On 2015-08-12 10:56:06 +0000, albert wrote:

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. .. (etc.) should be placed in CDATA constructs to overcome possible incorrect XML code resulting from the other *only constructs.

On 2015-08-31 16:37:07 +0000, albert wrote:

Code has been integrated in github

On 2015-12-30 10:19:01 +0000, Dimitri van Heesch wrote:

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).

@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