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 652695 - missing space rtf generation
missing space rtf generation
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.7.4
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
: 656147 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-06-16 07:57 UTC by Adrien
Modified: 2011-08-14 14:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
generated RTF screenshot (89.15 KB, image/png)
2011-06-16 07:57 UTC, Adrien
Details

Description Adrien 2011-06-16 07:57:15 UTC
Created attachment 190016 [details]
generated RTF screenshot

Hello,
I have found a minor issue for the RTF generation.

Considering the following code:

==================

/** main function called by the Upgrade tool to perform the upgrade.
 *
 * @param upgrade_package_info a dictionary contuining informations 
 * @param message the message 
 * @param toto negociation flag
 * @param plop the plop status. 
 *
 *
 *
 * @return the status of the return code.
 * @retval 0 OK, 
 * @retval 1 Not OK
 * @retval 2 Error .
 *
 *
 * */

int buggy_space(upgrade_package_t upgrade_package_info, char* message, dummy_type toto, dummy_type* plop); 

}     

==============

I have attached the a screenshot of the generated rtf file, showing in yellow where the space is missing.



Thank you for supporting the tool ! I really like it.
Comment 1 Dimitri van Heesch 2011-06-17 20:09:58 UTC
Confirmed. Should be fixed in the next subversion update.
Comment 2 Dimitri van Heesch 2011-08-08 09:12:53 UTC
*** Bug 656147 has been marked as a duplicate of this bug. ***
Comment 3 Dimitri van Heesch 2011-08-14 14:04:52 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.5. 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.