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 735759 - Broken man pages due to bad use of autoBreak
Broken man pages due to bad use of autoBreak
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.8-GIT
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2014-08-31 18:49 UTC by Mattias Ellert
Modified: 2014-12-25 16:02 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Example file that triggers the bug. (259 bytes, text/plain)
2014-08-31 18:49 UTC, Mattias Ellert 		Details

Description Mattias Ellert 2014-08-31 18:49:04 UTC 
Created attachment 284947 [details]
Example file that triggers the bug.

When generating manpages any call that generates manpage output between the calls to startMemberItem() and endMemberItem() must not write newline characters to the manpage since this will make the manpage not display correctly. The reason is thet the call to startMemberItem() outputs a quotation mark that starts a string and the call to endMemberItem() outputs a matching quotation mark that ends the string. This string must be on a single line to comply to manpage syntax.

In most cases this works as expected, but there are calls to linkifyText with autoBreak set to true between the calls that makes things fail under some conditions.

The attached fails shows te problem.

Setting autoBreak to false in the relevant linkifyText calls fixes the problem.
Comment 1 Mattias Ellert 2014-08-31 18:53:41 UTC 
https://github.com/doxygen/doxygen/pull/218
Comment 2 Dimitri van Heesch 2014-09-04 17:56:24 UTC 
Thanks, I've merged the pull request.
Comment 3 Dimitri van Heesch 2014-12-25 16:02:47 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.9. 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 (preferrably in the form of a self-contained example).