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 793644 - Long functionnames with links are not split in latex output when the line is to short.
Long functionnames with links are not split in latex output when the line is ...
Status: RESOLVED OBSOLETE
Product: doxygen
Classification: Other
Component: general
1.8.14
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
[moved_to_github]
Depends on:
Blocks:
 
 
Reported: 2018-02-20 12:26 UTC by Frank HJ Cuypers
Modified: 2018-07-30 10:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Complete example, see description field. (2.06 KB, application/zip)
2018-02-20 12:26 UTC, Frank HJ Cuypers
Details
Example demonstrating point 4 (3.39 KB, application/zip)
2018-02-20 17:59 UTC, Frank HJ Cuypers
Details

Description Frank HJ Cuypers 2018-02-20 12:26:53 UTC
Created attachment 368632 [details]
Complete example, see description field.

Long functionnames with links are not split in latex output when the line is to short.
I don't think this was a problem in doxygen 1.8.9.1.

In the provided example, run doxygen and then tmp/latex/make.bat. 
The detailed description of the "theclass" class shows the issue. All text is correctly right aligned, except the links to the member functions which run past the right border.
Long words without links are however correctly split.
A similar problem occurs in the "References" section of the longfunctionname() function.
Comment 1 Frank HJ Cuypers 2018-02-20 12:28:16 UTC
MikTex 2.9
Comment 2 albert 2018-02-20 14:47:07 UTC
I just pushed a proposed patch to github (pull request 661).

• Regression on Bug 778730 - doxygen build fails  
• Stackexchange article: When I prevent hyphenation using an \mbox, the box gets pushed into the right margin (https://tex.stackexchange.com/questions/53364/when-i-prevent-hyphenation-using-an-mbox-the-box-gets-pushed-into-the-right-ma)
Comment 3 Frank HJ Cuypers 2018-02-20 15:44:13 UTC
I manually added the \sloppy after \begin{document} and verified the result.
In the detailed description of the "theclass" class the issue is indeed solved.
But in the "References" section of the longfunctionname() function, the problem is still present.
Comment 4 Frank HJ Cuypers 2018-02-20 16:23:37 UTC
The \sloppy will not help for long links that do not fit 1 textline.
A link to a java function in a few nested packages and with a few arguments, can quickly become longer then 1 line of text. Here the only solution is splitting the link, like it was before Bug 778730.
Comment 5 albert 2018-02-20 16:42:37 UTC
Concluding we actually have a number of problems:
1) links overflowing right side margin in running text
2) links in references  overflowing right side margin in running text
3) index values overrunning column boundary (Bug_793649)
4) long links

1) has been solved by means of adding \sloppy to the document
2) overlooked, as was not that obvious in pdf file. Still to be solved.
3) problem was already present in 1.8.13 (i.e. before Bug_778730), with patch 1 better but still to be solved
4) problem to be investigated @Frank HJ Cuypers can you provide a problem that signals this problem due to nested packages. I think we should not, directly, take into account those cases where names are really that long that they don't fit in the column or on a line.
Comment 6 Frank HJ Cuypers 2018-02-20 17:59:40 UTC
Created attachment 368674 [details]
Example demonstrating point 4

I added a modified example to demonstrate point 4. See last paragraph of detailed description of class om.thecompany.theproject.theclass in the LaTeX output.
Not sure if this is realistic; anyhow easy to circumvent by providing shorter label in the @link.
Comment 7 André Klapper 2018-07-30 10:16:49 UTC
As discussed in https://github.com/doxygen/doxygen/pull/734 , Doxygen has moved its issue tracking to 

   https://github.com/doxygen/doxygen/issues

All Doxygen tickets in GNOME Bugzilla have been migrated to Github. You can subscribe and participate in the new ticket in Github. You can find the corresponding Github ticket by searching for its Bugzilla ID (number) in Github.

Hence I am closing this GNOME Bugzilla ticket.
Please use the corresponding ticket in Github instead. Thanks a lot!