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 688739 - PATCH: Special markers (url/local) incorrect in eclipse toc.xml
PATCH: Special markers (url/local) incorrect in eclipse toc.xml
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.2-SVN
Other All
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2012-11-20 17:18 UTC by René Papenhoven
Modified: 2012-12-26 16:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Fix for special markers in eclipse toc.xml (1.23 KB, application/octet-stream)
2012-11-20 17:18 UTC, René Papenhoven
  Details
Fix for special markers in eclipse toc.xml (2nd version) (2.45 KB, patch)
2012-11-24 10:36 UTC, René Papenhoven
none Details | Review

Description René Papenhoven 2012-11-20 17:18:29 UTC
Created attachment 229488 [details]
Fix for special markers in eclipse toc.xml

Special markers do not end up correctly in the eclipse toc.xml.

The markers for URLs ('^') and local ('!') are not handled by the eclipsehelp.cpp and as a result they end up prefixed with a path and an additional suffix .html.

I've fixed this in the attached patch.

Local markers (file) are correct now in the toc.xml.
As far as I know the eclipse toc.xml does not support entries to URLs.
Hence the patch will not generate toc.xml entries for URLs (iso incorrect ones).
Comment 1 René Papenhoven 2012-11-24 10:36:52 UTC
Created attachment 229757 [details] [review]
Fix for special markers in eclipse toc.xml (2nd version)

I've added a new patch (2nd version) to fix the issue.

The first one should be ignored as it has an issue with topics without href.
Comment 2 Dimitri van Heesch 2012-11-25 12:09:55 UTC
Thanks, I'll include the patch in the next subversion update.
Comment 3 Dimitri van Heesch 2012-12-26 16:09:12 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.3. 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.