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 784281 - Problem RTF output: The class list "classes" within the namespace report is wrong indicated.
Problem RTF output: The class list "classes" within the namespace report is w...
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.5
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2017-06-28 10:44 UTC by hope
Modified: 2018-05-28 13:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Error Example (146.34 KB, application/x-zip-compressed)
2017-06-29 09:59 UTC, hope
Details

Description hope 2017-06-28 10:44:03 UTC
There is some confusion in indication of classes and their brief description.
The HTML indication is correct. 
The error can be easy recognized if following screenshots are compared. 

See the screenshots in folder error_report: 
2017-06-28 11_28_51-Error sample_ Error Namespace Reference_HTML.jpg 
2017-06-28 11_26_06-refman_RTF.jpg.  (shows the error behaviour)

Used versions:
Doxygen version: 1.8.5 also tested with 1.8.13
OS:  Windows 7
Microsoft  Word 2010
The folder contains the error sample.

The attachment contains the last doxgen version 1.8.13 , the doxyfile and
an example. Also the created HTML and RTF output.
The folder error_report explains the error.
Comment 1 albert 2017-06-28 17:04:15 UTC
Probably forgot the attachment?
Comment 2 hope 2017-06-29 09:59:19 UTC
Created attachment 354679 [details]
Error Example
Comment 3 albert 2017-08-26 16:52:58 UTC
I just pushed a proposed patch to github (pull request 596)
Comment 4 albert 2017-09-02 16:20:08 UTC
update has been integrated into the main version on github
Comment 5 Dimitri van Heesch 2017-12-25 18:43:41 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.14. 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).