«> 19. TEXT» is rendered as «> 1. TEXT» Is it a markdown parser bug?

Bug
1
  1. TEXT

Discourse editor:

12.png764×90 3.23 KB

dillinger.io editor

13.png803×319 29.5 KB

1 Like
2

Discourse hasn’t moved to commonmark yet, but it seems to be fixed there, so when they do it should solve this.

Tested at
http://spec.commonmark.org/dingus/

6 Likes
3

If you need to know, the common workaround for this is to backslash escape the period.

19\. TEXT =>

19. TEXT

4 Likes