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 700456 - MarkDown ordered lists are not fully supported
MarkDown ordered lists are not fully supported
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
unspecified
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2013-05-16 13:11 UTC by Oleg
Modified: 2013-05-21 08:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
My doxyfile (81.73 KB, application/octet-stream)
2013-05-16 13:31 UTC, Oleg
Details

Description Oleg 2013-05-16 13:11:44 UTC
It is impossible to create an ordered list with whitespaces and a text between list items, e.g.:

-# Item 1

    Text of Item 1 with 4 spaces (1 tab)

-# Item 2
 
    Text of Item 2

gives the following result:

1. Item 1

    Text of Item 1 with 4 spaces (1 tab)

1. Item 2
 
    Text of Item 2

But http://www.stack.nl/~dimitri/doxygen/manual/markdown.html#mddox_code_blocks tells that:

"Note that list markers are not counted when determining the relative indent:

1.  Item1

    More text for item1

2.  Item2

        Code block for item2

For Item1 the indentation is 4 (when treating the list marker as whitespace), so the next paragraph "More text..." starts at the same indentation level and is therefore not seen as a code block."
Comment 1 Oleg 2013-05-16 13:31:46 UTC
Created attachment 244405 [details]
My doxyfile
Comment 2 Dimitri van Heesch 2013-05-18 15:59:21 UTC
Confirmed. Should be fixed in the next subversion update.
Comment 3 Dimitri van Heesch 2013-05-19 12:36:21 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.4. 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.
Comment 4 Oleg 2013-05-21 08:08:35 UTC
Thanks a lot, everything is OK now.