-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
showndown doesnt translate correctly ordored list to html. #158
Comments
@be-next-hotdog showdown does indeed support ordered lists. In fact i could not reproduce the bug you described. Can you provide more context? Heres a working fiddle with showdown parsing correctly a ordered list... |
For the test cases : Test case 1 :
Transformation result 1:
Test case 2 :
Transformation result 2 :
It seems like that showdown will transform to ordered / unordered list according to the first list element type. Otherwise caused by definition of markdown syntax ? I couldn't put these 2 kinds of etiquette (star/number) in the same list ? Thx a lot. |
yeap.
#like this, add an list separator
|
@be-next-hotdog yes, this is a known bug/gotcha/feature (we haven't really decided was that is). John Gruber's (the markdown creator) lib had this odd behavior. According to the author, it is in fact intended. I doubt it... but we haven't yet decided to "fix" this since we want to adhere to the original spec as much as possible. As a workaround, you can add any character bewteen the 2 lists (as @8Miles-Mai suggested). |
Duplicate of #142 |
Yepp, I knew this solution before, and we could also type a space to each element as :
in this case, the showdown will regard the second ordered list as a sublist. StackEdit follows this rule either, also the github comment tool which we use here. Thx all the same guys ! |
While i was trying to input an ordered list as follow :
showdown would transfer these to an unordered list in html :
eventually a bug ? Or showdown is not able to differentiate ordered list and unordered list ?
The text was updated successfully, but these errors were encountered: