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

Broken man pages due to bad use of autoBreak (Origin: bugzilla #735759) #5585

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component general for ---
Reported in version 1.8.8-GIT on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2014-08-31 18:49:04 +0000, Mattias Ellert wrote:

Created attachment 284947
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.

On 2014-08-31 18:53:41 +0000, Mattias Ellert wrote:

#218

On 2014-09-04 17:56:24 +0000, Dimitri van Heesch wrote:

Thanks, I've merged the pull request.

On 2014-12-25 16:02:47 +0000, Dimitri van Heesch wrote:

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).

@doxygen doxygen closed this Jul 2, 2018

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