GNOME Bugzilla – Bug 624256
single line comments contained in formatted output
Last modified: 2010-08-22 17:43:19 UTC
Created attachment 165802 [details] (see end of description for details) screenshots, source of different versions After upgrading vom v1.6.3 to v1.7.1 the content and layout of out doxygen-projects changed heavily. No changes on the interpreted source code (c#) has been made but the output is very ugly now. (1) Having a piece of documentation with a couple of lines starting with triple slashes (///) was handled correct in 1.6.3. The triple slashes were omitted in the formatted output. Now (v1.7.1) these triple slashes appear inside the formatted output (see attachements, each for 163 and 171 repectively ... together with some fragments of the source code). (2) Maybe connected to that problem is the interpretation of html-tags included. The lines /// <ul> /// <it>an item description /// </ul> are not working anymore and we get errors according 'lonely <li>-items'. Other multiline-html-formattings behave similar (badly). ? Maybe there is another new option which switches back to the fine results of 163 ?. ? Maybe I have to improve the html-formattings and everything will go right afterwards ? referring attachments ... (a) There are t_w_o examples - codeFlow_mark (a method) - codeFlow_nodeFormStandards (an informational piece with dot-graphs) (b) Both are presented - as extracts from the source code - als screenshots (*.png) for version 1.6.3 and 1.7.1 respectively (c) I have to commit that the screenshots derive from different OS (WinXPx86 and Win7x64 respectively) but before upgrading on doxygen 1.7.1 on Win7x64 everything was nice as on WinXPx86.
I am sorry for some misspelled words in the description. My (German) spellchecker seems to re-interpret some english words as german words automatically ... which I didn't recognize before sending the message.
after another inspection of the current bug-list this error seems to correspond to bug #336053 which has already been reported in 2006.
Also bug #487871 seems to be connected with the problem reported here.
I can only reproduce the problem if MULTILINE_CPP_IS_BRIEF = YES, which is a known bug. If you have a self-contained test case the has this problem when MULTILINE_CPP_IS_BRIEF set to NO, then please attach it. *** This bug has been marked as a duplicate of bug 625952 ***