Re: [Doxygen-users] fenced code block bug

[Paul A. L. <pa...@le...>]

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 commands to shine through into the generated PDF.

Thanks for all your help!

Paul

> On 17. aug. 2015, at 19.33, Albert <alb...@gm...> wrote:
> 
> 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 COMMENT
> 'NOTE! COMMENTS ARE IGNORED BY THE PROGRAM
> ~~~
> */
> 
> I used a default Doxyfile, but don't see the line numbers (I've seen remarks about this before, but I don't remember under which circumstances).
> Maybe you can attach a small complete example (source and Doxyfile, with the Doxyfile when generating it use the -s option and try to pack it in a zip file as attachments are limited in size).
> 
> 
> Regarding the \- \+ I think they will be there for a good reason (The change from \- to \+ was commented as follows: Use hook arrow for hyphens in symbol names in the LaTeX output.).
> 
> Albert
> 
> On Mon, Aug 17, 2015 at 9:22 AM, Paul Anton Letnes <pa...@le...> wrote:
> 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 (cygwin, not sure when it was updated last) creates this LaTeX code:
>   0  \begin{DoxyCode}
>   1 1 'THIS IS A COMMENT
>   2 2 'NOTE! COMMENTS ARE IGNORED BY THE PROGRAM
>   3 \end{DoxyCode}
> 
> Notably, line numbering is suddenly enabled. I've got my markdown sources in git, btw, so they should be identical. The 1.8.[56] LaTeX code compiles on the LaTeX versions on their respective OS-es, but gives the screenshot attached: The \textcolor{...} stuff is included in the output, which it should not be.
> 
> On cygwin LaTeX and doxygen 1.8.9.1, the LaTeX does not compile due to another change in the generated LaTeX - there's a lot of \+ commands in CAPITALIZED words (can this be disabled?). On 1.8.[56], there are \- commands. For example:
> 
> Markdown:
> CAPITALIZED
> LaTeX from 1.8.[56]:
> C\-A\-P\-I\-T\-A\-L\-I\-Z\-E\-D
> LaTeX from 1.8.9.1:
> C\+A\+P\+I\+T\+A\+L\+I\+Z\+E\+D
> 
> Is it possible to disable the backslash plusminus behavior? And why do we see the differences in generated DoxyCode blocks? The version change 1.8.5 to 1.8.9 is a fairly minor one, so I'm a bit surprised. Any advice greatly appreciated.
> 
> -----------
> Paul Anton
> 
> 
> Den 14. august 2015 skrev woody <kn...@re...>:
> 
> 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 reformatting it so the braces line up properly will reveal this.
> 
> ~~~
> 
> 'THIS IS A COMMENT
> 
> 'NOTE! COMMENTS ARE IGNORED BY THE PROGRAM 
> ~~~ 
> the resulting LaTeX code has errors in it (the HTML looks fine): 
> \begin
> 
>                 {
>                 DoxyCode
>                 }
> \textcolor 
>         { 
>           stringliteral 
>         }
> {'THIS IS A COMMENT}
> \textcolor 
>        { 
>        stringliteral 
>         }
>       {'} 
>         NOTE! COMMENTS ARE IGNORED BY THE PROGRAM 
> \end{DoxyCode}
> 
> This leads to the \textcolor command passing through to the PDF document. Also, the curly brace looks off in the second line.
> 
> Are there any fixes in more recent versions of doxygen? Or is there a workaround that's not too bad? Sometimes it helps to give the .m suffix, e.g. ~~~{.m}, to the code block - but weirdly, not always.
> 
> ----------- 
> Paul Anton
> 
> ------------------------------------------------------------------------------
> 
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users