Re: What is the most recent offical test suite ?

Le 2009-02-27 à 19:58, david parsons a écrit : I just recently became aware of MarkdownTest_1.0.3 (which discount fails, due to the behavior of code blocks changing from "leave whitespace alone except on the first line" to "leave whitespace alone", and the addition of a new kind of magic link

What is the most recent offical test suite ?

I just recently became aware of MarkdownTest_1.0.3 (which discount fails, due to the behavior of code blocks changing from "leave whitespace alone except on the first line" to "leave whitespace alone", and the addition of a new kind of magic link that doesn't seem to be documented); is this the mos

Re: Cpp-Markdown 1.00

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Since no one seemed to notice the question in my announcement message a couple days ago, I'm asking again: I've been trying to add Cpp-Markdown to the markdown wiki page at , but I can't seem to log in there with my redd

re: elastic tabstops, proportional fonts, and more

sherwood said: >Nice rant. um... thanks... i guess... although i consider a "rant" to be an emotional outburst, and i save my emotions for my poetry, and try to be _rational_ on listserves... >I sympathize.  Ain't going to happen. why not? > you're proposing that browsers >inte

Re: RFC: Markdown Table Syntax

> The problem I can see, however, is that it forces the common cases to adopt > the syntax required by the edge cases. In general, I think that tables will > often *not* have multiline cells. My proposal is for supporting _two_ table syntaxes. One simple that would work just like the current MD-Ex

Re: RFC: Markdown Table Syntax

On Feb 27, 2009, at 8:55 AM, David E. Wheeler wrote: id |name | description | price ==|=|==| 1 | gizmo | Takes care of the doohickies | 1.99 ‐‐+‐ +‐‐ +

Re: RFC: Markdown Table Syntax

On Feb 26, 2009, at 11:22 PM, Yuri Takhteyev wrote: Why not have two different kinds of table: one where each line is a row, and one where rows are show explicitly with dashes. The second type could use = or something else after the header: id |name | description

Re: elastic tabstops, proportional fonts, and more

G'day Nice rant. I sympathize. Ain't going to happen. In a nut shell, you're proposing that browsers interpret a whole new language. A simpler one than html, but non-the-less a new language. That new language is weak compared to html, in the sense that by itself it can't say, "Float this pictu