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

A lost refference in the documentation of htmlonly tag (with PATCH) (Origin: bugzilla #699464) #5160

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

status RESOLVED severity trivial in component documentation for ---
Reported in version on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2013-05-02 12:45:34 +0000, Manuel L. Pereira García wrote:

Created attachment 243044
PATCH for the xmlonly reference on the htmlonly description

I use the version, running on Ubuntu 10.4 LTS. In the html help, when docummenting htmlonly tag and in the section "See also", there is no a reference to xmlonly tag, despite there are references to manonly, latexonly and rtfonly tags. Perhaps an out of date bug?

On 2013-05-05 11:31:41 +0000, Dimitri van Heesch wrote:

Thanks for the patch.

Next time please modify the source doc/commands.doc, not the file html/commands.html, which is generated by doxygen ;-)

On 2013-05-06 09:57:08 +0000, Manuel L. Pereira García wrote:

Created attachment 243374
PATCH for the xmlonly reference on the htmlonly description

On 2013-05-06 09:58:06 +0000, Manuel L. Pereira García wrote:

Next time is now!

On 2013-05-19 12:36:09 +0000, Dimitri van Heesch wrote:

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

On 2013-05-21 10:07:38 +0000, Manuel L. Pereira García wrote:

It's verified, and it's OK. Thank you very much.

@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