search for: 29mtuz102

Noticed the patterns for setext style headings are: ^(.+)[ \t]*\n=+[ \t]*\n+ Should be: ^(.+?)[ \t]*\n=+[ \t]*\n+

Seeing how no-one should send application/xhtml+xml to the browser [1], and development of the HTML standard is again happening [2], it would make sense to have Markdown.pl default to HTML tags. Maybe too late to change a default though. How does PHP Markdown and other implementations deal with this issue? [1]: http://www.hixie.ch/advocacy/xhtml [2]:

A user has table-formatted data which contains accents and finds it problematic that his tables misalign after going through Markdown. This is because he made them align using tab characters and Markdown will convert these to spaces even in pre-formatted text and Markdown is not multi-byte aware. This raises two questions: 1. Should Markdown convert tabs to spaces in pre-formated text?

I was recently made aware of the the Markdown 1.0.2 beta 4 and naturally downloaded it in great anticipation, as I am a big fan of Markdown :) Though I did notice a significant performance drop: The TextMate manual is 3,000 lines (173 KB) and previously took 4-5 seconds to convert to HTML (measuring only time spent by `Markdown.pl`.) With the new version this has increased to almost 30

I recently subscribed and saw in the archive that Eric Astor was asking for a formal grammar (unlikely the first time for such request.) Currently there are a few problems in making such a thing so I was curious if Mr. Gruber has made any thoughts about moving toward one? This would also allow a more ?clean? parser which would get rid of some of the current problems (bad nesting[^1],