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

Javadoc compatibility (Origin: bugzilla #601694) #3584

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2009-11-12 13:49:11 +0000, wrote:

Created attachment 147577
Bug report compatibility with javadoc

What a pity to leave this awesom tool doxygen not fully compatible with javadoc. The joined document explains the different cases I have encountered.
I hope this will be soon resolved !

Thanks !

On 2009-11-17 13:50:17 +0000, wrote:

Should I understand by your non responsing behave that doxygen is not going to be compatible with javadoc ?

On 2009-11-18 08:45:45 +0000, wrote:

Ok thanks a lot for your answer I'll ask my company for help but not sure as I'm such a trainee. Have a nice day Mister.

Respectfully yours,


On 2009-12-28 12:56:24 +0000, Dimitri van Heesch wrote:

Problem is found and should be fixed in the next release.

On 2009-12-30 13:38:31 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.2. Please verify if this is indeed the case and reopen the
bug if you think it is not fixed (include any additional information that you
think can be relevant).

On 2010-01-04 14:51:15 +0000, wrote:

Sorry but all bugs are still there.

On 2010-01-04 14:55:29 +0000, wrote:

I tried with the doxygen-1.6.2.exe on windows XP pro.

On 2010-01-15 13:15:42 +0000, Dimitri van Heesch wrote:

The {@code ... } construct should work. The rest is a matter of setting the correct value for INPUT_ENCODING. Your sources are apparently not UTF-8 encoded!

If you still see problems please attach a self-contained example (source + config file in a zip) that allows me to reproduce the problem.

On 2010-06-03 14:46:03 +0000, Tobias Mueller wrote:

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.

@doxygen doxygen closed this Jul 2, 2018

@doxygen doxygen added the doxywizard label Jul 19, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment