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 601694 - Javadoc compatibility
Javadoc compatibility
Status: RESOLVED INCOMPLETE
Product: doxygen
Classification: Other
Component: doxywizard
unspecified
Other Windows
: Normal trivial
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2009-11-12 13:49 UTC by pierre.lakreb
Modified: 2010-06-03 14:46 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Bug report compatibility with javadoc (461.55 KB, application/pdf)
2009-11-12 13:49 UTC, pierre.lakreb 		Details

Description pierre.lakreb 2009-11-12 13:49:11 UTC 
Created attachment 147577 [details]
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 !
Comment 1 pierre.lakreb 2009-11-17 13:50:17 UTC 
Should I understand by your non responsing behave that doxygen is not going to be compatible with javadoc ?
Comment 2 pierre.lakreb 2009-11-18 08:45:45 UTC 
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,

Pierre
Comment 3 Dimitri van Heesch 2009-12-28 12:56:24 UTC 
Problem is found and should be fixed in the next release.
Comment 4 Dimitri van Heesch 2009-12-30 13:38:31 UTC 
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).
Comment 5 pierre.lakreb 2010-01-04 14:51:15 UTC 
Sorry but all bugs are still there.
Comment 6 pierre.lakreb 2010-01-04 14:55:29 UTC 
I tried with the doxygen-1.6.2.exe on windows XP pro.
Regards
Comment 7 Dimitri van Heesch 2010-01-15 13:15:42 UTC 
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.
Comment 8 Tobias Mueller 2010-06-03 14:46:03 UTC 
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.
Thanks!