Re: [Doxygen-users] fenced code block bug

2015-08-19 Thread Paul Anton Letnes
Hi again. Well, this is embarrassing, but as expected in a way - when creating a minimal working example, the problem showed itself. It turns out someone had subtly modified the DoxyCode environment in the document preamble, by using verbatim instead of typewriter font. This caused the LaTeX co

Re: [Doxygen-users] fenced code block bug

2015-08-17 Thread Albert
Which LaTeX version are you using on your system. There are problems with some a bit older LaTeX versions. Might be good to have a look at the recent texlive version (solved a lot of problems for me on Linux). I used your code, incorporated as follows in a file aa.h: /** \file ~~~ 'THIS IS A COMME

Re: [Doxygen-users] fenced code block bug

2015-08-17 Thread Paul Anton Letnes
Hi! Okay, so I've dug further into the matter. doxygen 1.8.5 (centos 7) and 1.8.6 (ubuntu 14.04) creates this LaTeX code: 0 \begin{DoxyCode} 1 \textcolor{stringliteral}{'THIS IS A COMMENT} 2 \textcolor{stringliteral}{'}NOTE! COMMENTS ARE IGNORED BY THE PROGRAM 3 \end{DoxyCode} whereas 1.8.9.1 (c

Re: [Doxygen-users] fenced code block bug

2015-08-14 Thread woody
Given that curly braces enclose items, it is Pretty clear that the {'} is a stand alone quote, and the remainder of the line NOTE! is just a line of text, and passed through directly to the output. However, if the code was {'NOTE!...} then I assume it will behave correctly. perhaps re

Re: [Doxygen-users] fenced code block bug

2015-08-14 Thread Albert
What kind of investigations did you test regarding the newer versions? What errors are there in the Latex code, code looks fine to me (and compiles correctly). The part the second {'} is the closing quote of the first one, in the HTML you see that the first line has a different color than the seco