Le 20-juin-2013 à 14:48, Alexander Veit <[email protected]> a écrit : > The book of [Life](https://en.wikipedia.org/wiki/Life_(textbook) "Life > textbook"). > > which is converted to > > <p>The book of <a > href="https://en.wikipedia.org/wiki/Life_(textbook">Life</a> "Life > textbook").</p>
Most Markdown implementations out there do the right thing: matching opening and closing parenthesis. It's just sad that Markdown.pl doesn't. http://johnmacfarlane.net/babelmark2/?normalize=1&text=The+book+of+%5BLife%5D(https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FLife_(textbook)+%22Life+textbook%22).%0A > However, there's probably a solution to this problem. RFC 2396, 2.4.3 defines > the left and right angle brackets as delimiters and explains that > >> The angle-bracket "<" and ">" and double-quote (") characters are >> excluded because they are often used as the delimiters around URI in >> text documents and protocol fields. > > This means that left and right angle brackets will never occur as part of an > URI. So deprecating parentheses, and replacing the parentheses with angle > brackets in Markdown's inline link syntax would resolve the problem > described. As an additional benefit, this would unify Markdown inline link > syntax and reference-style link syntax, and simplify link parsing. Angle brackets surrounding the URL are supported by most Markdown parsers, but the URL must be kept inside the parens. Unfortunately, only some parsers correctly use them to disambiguate: http://johnmacfarlane.net/babelmark2/?normalize=1&text=%5BBrackets%5D(%3Chttps%3A%2F%2Fen.wikipedia.org%2Fwiki%2F)%3E+%22Brackets%22).%0A -- Michel Fortin [email protected] http://michelf.ca _______________________________________________ Markdown-Discuss mailing list [email protected] http://six.pairlist.net/mailman/listinfo/markdown-discuss
