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 776870 - XML Parsing Error for operator<< methods when outputing to XHTML
XML Parsing Error for operator<< methods when outputing to XHTML
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.13
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2017-01-04 16:06 UTC by David Zemon
Modified: 2017-12-25 18:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Sample configuration and source file to reproduce the bug (33.32 KB, application/gzip)
2017-07-04 18:15 UTC, David Zemon
Details

Description David Zemon 2017-01-04 16:06:26 UTC
Some characters are not being properly escaped when generating XHTML output. It seems to have a problem with my operator<<() method.
Comment 1 albert 2017-01-05 18:14:14 UTC
Can you please attach a self-contained example (source+config file in a tar or zip) that allows us to reproduce the problem?
Comment 2 David Zemon 2017-07-04 18:15:21 UTC
Created attachment 354896 [details]
Sample configuration and source file to reproduce the bug

I'm really sorry for leaving this open for so long. I just re-discovered this bug and found out it's been on my plate this whole time. I've attached the requested information for you.
Comment 3 albert 2017-08-25 10:17:19 UTC
I just pushed a proposed patch to github (pull request 595)

NOTE: this bugfix also requires pull request #594 in case #586 has been incorporated.
Comment 4 albert 2017-09-27 11:06:26 UTC
Has been integrated in the main branch of github (September 21. 2017)
Comment 5 Dimitri van Heesch 2017-12-25 18:43:36 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).