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 675757 - Markdown lists are improperly nested
Markdown lists are improperly nested
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.0
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2012-05-09 15:29 UTC by danielpopowich
Modified: 2012-05-19 12:27 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Sample files plus Doxyfile that demonstrate the bug. (2.29 KB, application/zip)
2012-05-09 15:29 UTC, danielpopowich
Details

Description danielpopowich 2012-05-09 15:29:57 UTC
Created attachment 213738 [details]
Sample files plus Doxyfile that demonstrate the bug.

Using markdown to generate lists improperly nests the 2nd - nth element in the list.  For example, the following:

 - item 1
 - item 2
 - item 3
 - item 4

Gets rendered as:

 * item 1
      o item 2
      o item 3
      o item 4

Same for numbered lists.  Also, a paragraph after a numbered list becomes the continuation of the last item in the list.

I have included three files as an attachment.  One is plain text, one is a python file and the last is C.  The plain text version doesn't have the improper nesting issue, but does have the improperly indented paragraph issue.  The python and C files demonstrate both problems.

I've included a minimal Doxyfile as well.
Comment 1 Dimitri van Heesch 2012-05-09 19:02:43 UTC
This is mostly a duplicate of bug #671023, except for the paragraph 5 indenting issue, which should be fixed in the next subversion update.
Comment 2 Dimitri van Heesch 2012-05-19 12:27:01 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.1. 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.