Skip to content
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

Prevent that every number followed by a dot is interpreted as order list #924

Closed
rico opened this issue Aug 14, 2017 · 4 comments
Closed
Labels
category: lists L2 - annoying Similar to L1 - broken but there is a known workaround available for the issue

Comments

@rico
Copy link

rico commented Aug 14, 2017

Is there a way to prevent marked from rendering / interpreting every number followed by a dot as an ordered list item?

The problem is, that here in Switzerland we format a date as follows: 14. August 2017. Now if I run this through marked I get 1. August 2017 (first item of ordered list). Not exactly what I want :-)

@joshbruce
Copy link
Member

See #982

@bambooom
Copy link

Hi, I'm still seeing this issue, demo on marked.js.org

What's my input:

# Some title

The development work of the something something  started in 
2016. It was pioneered by somebody and some others.
Over the past 2 years or so, a lot of bugs have been fixed in
mode
and our recent extensive testings show that it is already mature enough
for our own production use.

What I get:
Screenshot 2019-04-26 at 1 27 56 PM

However, 2016. is just the end to the previous sentence, it should not be rendered as ordered list. I do can just move it to the previous line for now, but how should I prevent this later? Thanks.

@UziTech UziTech added category: lists L1 - broken Valid usage causes incorrect output OR a crash AND there is no known workaround for the issue and removed help wanted question labels Apr 26, 2019
@UziTech UziTech reopened this Apr 26, 2019
@UziTech
Copy link
Member

UziTech commented Apr 26, 2019

looks like this is fixed when gfm: false demo

@UziTech UziTech added L2 - annoying Similar to L1 - broken but there is a known workaround available for the issue and removed L1 - broken Valid usage causes incorrect output OR a crash AND there is no known workaround for the issue labels Apr 26, 2019
@UziTech
Copy link
Member

UziTech commented Nov 3, 2020

Looks like this was fix in v0.7.0

@UziTech UziTech closed this as completed Nov 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: lists L2 - annoying Similar to L1 - broken but there is a known workaround available for the issue
Projects
None yet
Development

No branches or pull requests

4 participants