Markdown Extra Spec: Parsing Section

[John MacFarlane]

Just to clarify: Most implementations allow newlines and embedded
brackets in link text. But pandoc and peg-markdown seem to be the only
ones that currently allow them in link reference definitions:

http://babelmark.bobtfish.net/?markdown=[hi%0D%0Athere][]%0D%0A%0D%0A[hi+there]%3A+%2Furl%0D%0A%0D%0A[hi%0D%0Aagain][]%0D%0A%0D%0A[hi%0D%0Aagain]%3A+%2Furl%0D%0A%0D%0A[[hi]](%2Furl)%0D%0A%0D%0A[[hello]]%0D%0A%0D%0A[[hello]]%3A+%2Furl%0D%0A&normalize=on&src=1&dest=2

+++ Tomas Doran [May 09 08 21:19 ]:


>>>  Still, why shouldn't refnames be allowed to have embedded brackets

>>>  and newlines, if explicit links can?

>>

>> To me those seem to be two entirely different things...  The _text_ of

>> the link has to be flexible to allow almost anything.  refnames, on

>> the other hand are identifiers and as such it makes sense for them to

>> be more constrained.  For instance, if you allow new lines in them it

>> opens a whole bunch of questions as to what white space "counts".

>>

>

> In Text::Markdown, I'm allowing new lines in link text:

>

> http://svn.kulp.ch/cpan/text_multimarkdown/trunk/t/Text- 

> Markdown.mdtest/Links_multiline_bugs_1.text

> http://svn.kulp.ch/cpan/text_multimarkdown/trunk/t/Text- 

> Markdown.mdtest/Links_multiline_bugs_2.text

>

> As it was specifically reported to me as a bug:

>

> http://bugs.debian.org/459885

>

> Cheers

> Tom

>

>

> _______________________________________________

> Markdown-Discuss mailing list

> Markdown-Discuss at six.pairlist.net

> http://six.pairlist.net/mailman/listinfo/markdown-discuss

>