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 557094 - Wrong spacing in function names with french language (latex output)
Wrong spacing in function names with french language (latex output)
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.5.5
Other All
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2008-10-20 14:54 UTC by Matthias
Modified: 2017-12-25 18:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Matthias 2008-10-20 14:54:39 UTC
Please describe the problem:
Setting the option OUTPUT_LANGUAGE to French, makes latex use the french package.
But this package change the meaning of colon in order to have the right thin space on both side of the punctuation character. 

Thus, typesetting text like Class::method() with the french option, results in ugly output...

Something like "Class :  :method()"...

Steps to reproduce:



Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Matthias 2009-06-10 09:20:27 UTC
One should insert \NoAutoSpaceBeforeFDP in refman.tex to fix wrong spacing in  LaTeX generated documentation with french extension
Comment 2 albert 2017-10-01 12:04:54 UTC
I didn't find such extreme spacing as mentioned as in the bug report, but in the "References" part I did find some spacing issues. This is fixed by the mentioned addition of \NoAutoSpaceBeforeFDP


Just pushed the proposed patch to github (pull request 608)
Comment 3 albert 2017-10-02 16:26:21 UTC
Patch has integrated in master version on github.
Comment 4 Dimitri van Heesch 2017-12-25 18:43:35 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).