# Markdown link not parsed when prepended with \`\[Text\] \`
**URL:** https://meta.discourse.org/t/markdown-link-not-parsed-when-prepended-with-text/55770
**Category:** Bug
**Tags:** markdown-it-review
**Created:** [1월 14, 2017, 5:55오후 UTC](https://meta.discourse.org/t/markdown-link-not-parsed-when-prepended-with-text/55770 "2017-01-14T17:55:47Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@jooize](https://meta.discourse.org/u/jooize)
#### Post date: [1월 14, 2017, 5:55오후 UTC](https://meta.discourse.org/t/markdown-link-not-parsed-when-prepended-with-text/55770/1 "2017-01-14T17:55:47Z")
## Example
[Text] [Link](https://meta.discourse.org)
[Link](https://meta.discourse.org) [Text] [Link](https://meta.discourse.org)
---
### Author:  [@cpradio](https://meta.discourse.org/u/cpradio)
#### Post date: [1월 14, 2017, 6:01오후 UTC](https://meta.discourse.org/t/markdown-link-not-parsed-when-prepended-with-text/55770/2 "2017-01-14T18:01:21Z")
> [@jooize](#):
>
> [Text] [Link](https://meta.discourse.org)
This works on
> **[commonmark.js demo](https://spec.commonmark.org/dingus/)**
So it will likely get resolved when Discourse moves to it.
---
### Author:  [@Silvanus](https://meta.discourse.org/u/Silvanus)
#### Post date: [1월 15, 2017, 1:16오전 UTC](https://meta.discourse.org/t/markdown-link-not-parsed-when-prepended-with-text/55770/3 "2017-01-15T01:16:01Z")
Are we migrating from markdown to this new thing, then?
---
### Author:  [@cpradio](https://meta.discourse.org/u/cpradio)
#### Post date: [1월 15, 2017, 1:26오전 UTC](https://meta.discourse.org/t/markdown-link-not-parsed-when-prepended-with-text/55770/4 "2017-01-15T01:26:41Z")
It will still be markdown, just an actual spec.
---
### Author:  [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [1월 15, 2017, 1:48오전 UTC](https://meta.discourse.org/t/markdown-link-not-parsed-when-prepended-with-text/55770/5 "2017-01-15T01:48:38Z")
From the CommonMark website:
> ##Why is CommonMark needed?
> John Gruber’s [canonical description of Markdown’s syntax](http://daringfireball.net/projects/markdown/syntax) does not specify the syntax unambiguously.
> In the absence of a spec, early implementers consulted the original `Markdown.pl` code to resolve these ambiguities. But `Markdown.pl` was quite buggy, and gave manifestly bad results in many cases, so it was not a satisfactory replacement for a spec. `Markdown.pl` was last updated December 17th, 2004.
> Because there is no unambiguous spec, implementations have diverged considerably over the last 10 years. As a result, users are often surprised to find that a document that renders one way on one system (say, a GitHub wiki) renders differently on another (say, converting to docbook using Pandoc). To make matters worse, because nothing in Markdown counts as a “syntax error,” the divergence often isn’t discovered right away.
> There’s no standard test suite for Markdown; [MDTest](https://github.com/michelf/mdtest/) is the closest thing we have. The only way to resolve Markdown ambiguities and inconsistencies is [Babelmark](http://johnmacfarlane.net/babelmark2/), which compares the output of 20+ implementations of Markdown against each other to see if a consensus emerges.
> We propose a **standard, unambiguous syntax specification for Markdown** , along with a **suite of comprehensive tests** to validate Markdown implementations against this specification. We believe this is necessary, even essential, for the future of Markdown.
> That’s what we call CommonMark.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [6월 26, 2017, 1:57오후 UTC](https://meta.discourse.org/t/markdown-link-not-parsed-when-prepended-with-text/55770/6 "2017-06-26T13:57:59Z")
Rebaked OP and all appears to be working now!
> [@CommonMark testing started here!](https://meta.discourse.org/t/commonmark-testing-started-here/65121):
>
> Per our [migration plans](https://meta.discourse.org/t/discourse-commonmark-migration-plans-confetti-ball-balloon), I just enabled [markdown.it](https://github.com/markdown-it/markdown-it) at Meta. It is an excellent [CommonMark](http://commonmark.org/) compliant engine. I expect quite a few edges to be found during this period of testing. Do not open bugs about the new Engine, just reply here. I/we will be updating the top post here with the list of issues and striking out stuff as it is fixed. Current known issues (to be fixed)white_check_mark Onebox vanishes after you start typing and works not-super consistently white_check_mark pending…
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [6월 26, 2017, 1:58오후 UTC](https://meta.discourse.org/t/markdown-link-not-parsed-when-prepended-with-text/55770/7 "2017-06-26T13:58:03Z")