GNOME Bugzilla – Bug 681350
Code formatting completely broken
Last modified: 2012-08-11 13:18:19 UTC
Created attachment 220509 [details] The author.cpp file In V1.8.1.2 code formatting is completely broken (which used to work before). I've attached an example (pasted into the author.cpp file). The following things don't work: - Doxygen generates a warning during its run - The @code/@endcode block for class Test1 is not recognized properly - Comments for class Test2 are turned into code Also the removal of indentation introduced in V1.8.1.2 is not working properly (I assume the idea was to remove the relative indentation of a block - not to remove all leading spaces for each line?). Right now all lines are stripped of all leading spaces, so any existing formatting is lost. Please let me know if you need any more details or examples, thanks!
Created attachment 220511 [details] The same file, but without tabs. [Edit] I just found out that part of the problem seems to be related to tabs (we use a tab with of 2). I've attached author2.cpp without tabs and while the result is slightly better it still is broken.
Please check two things: 1) If setting MARKDOWN_SUPPORT to NO helps 2) If you use a custom CSS stylesheet it probably needs updating (not doing so causes the indentation of code lines to be lost). So try with the default stylesheet first. For completeness also include the config file you used to test the example.
Created attachment 220540 [details] Configuration file Thanks for the quick reply! Since removing the custom CSS stylesheet the indentation works again. The main problems reported in this thread are fixed by setting MARKDOWN_SUPPORT to NO. As we don't use markdown formatting (yet) everything works again. It might be interesting to examine though if there is a bug in the markdown interpreter. I've included the (original) author.cfg file.
There was indeed still a bug in Markdown processing. I'll correct this in the next release.
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.8.2. 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.