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 775245 - referencing Python files via tagfile broken
referencing Python files via tagfile broken
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.12
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2016-11-28 15:30 UTC by Stefan Vigerske
Modified: 2016-12-29 18:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
example files to reproduce problem (220.00 KB, application/x-tar)
2016-11-28 15:30 UTC, Stefan Vigerske
Details

Description Stefan Vigerske 2016-11-28 15:30:14 UTC
Created attachment 340917 [details]
example files to reproduce problem

When I have one doxygen project documenting some python code and generate a tagfile for it and another doxygen project that tries to reference a file of the python code via the tagfile, then a wrong link is created in the HTML output of the latter project.

In the attached small example, foo.py is documented in foo_html/foo_8py.html.
However, the link in main_html/index.html points to foo__8py.html, that is, there is an additional underscore.

The .tag file has
<tagfile>
  <compound kind="file">
    <name>foo.py</name>
    <path>/home/stefan/tmp/doxygenpythonbug/</path>
    <filename>foo_8py</filename>
...

On our side, the Python code is the only one that creates compounds with kind "file" in tag files. Somewhere, I would guess, an underscore gets "escaped" too often.

To reproduce, first run doxygen on Doxygen_foo and then on Doxygen_main and open main_html/index.html.
Comment 1 Stefan Vigerske 2016-11-28 15:33:06 UTC
With doxygen 1.8.10, this has still been working. I don't know about 1.8.11.
Comment 2 Dimitri van Heesch 2016-11-29 08:38:16 UTC
Confirmed. Should be fixed in the next GIT update.
Comment 3 Dimitri van Heesch 2016-12-29 18:45:38 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.13. 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).