Re: evolving the spec (was: forking Markdown.pl?)

On 1 Mar 2008, at 19:19, David Parsons wrote: I agree that Markdown needs to be defined unambiguously, but I don't think that's feasible with plain English [...] I'm not so sure about this. I managed to write a markdown implementation without using anything other than the daring fir

Re: evolving the spec (was: forking Markdown.pl?)

In article <[EMAIL PROTECTED]>, John Fraser wrote: >On Mar 1, 2008, at 1:19 PM, david parsons wrote: >>> I agree that Markdown needs to be defined unambiguously, but I don't >>> think that's feasible with plain English in the loop. For something >>> as complex and flighty as Markdown, we need wo

Re: evolving the spec (was: forking Markdown.pl?)

On Mar 1, 2008, at 1:19 PM, david parsons wrote: I agree that Markdown needs to be defined unambiguously, but I don't think that's feasible with plain English in the loop. For something as complex and flighty as Markdown, we need working code. I'm not so sure about this. I managed to writ

Re: spaces and newlines before list markers (was: evolving the spec)

Joseph Lorenzo Hall wrote on 2008/03/01 19:34: Is there any use case other than the copy and pasting example that gets you whitespace before a list item marker? Do people do this on purpose? best, Joe I do. Which is probably a guarantee that it is outlandish and uncivilised -- but I prefer i

Re: spaces and newlines before list markers (was: evolving the spec)

In article <[EMAIL PROTECTED]>, Joseph Lorenzo Hall wrote: >Is there any use case other than the copy and pasting example that >gets you whitespace before a list item marker? Do people do this on >purpose? I do it all the time. I indent text by 4 spaces, and do * text or 1.

Re: evolving the spec (was: forking Markdown.pl?)

I think many of Michel's points are quite reasonable. Given that we agree on many parts, how about we start off with those things we agree on and deal with other issues later. Specifically, I suggest that we start with hammering out the "macro" part of "Level 1" of the spec. I.e., let's not worry

Re: spaces and newlines before list markers (was: evolving the spec)

Is there any use case other than the copy and pasting example that gets you whitespace before a list item marker? Do people do this on purpose? best, Joe -- Joseph Lorenzo Hall UC Berkeley School of Information http://josephhall.org/ ___ Markdown-Discu

[ANN] discount

I've written an implementation of Markdown in C, for people like me who shout BAH! and wave their canes at modern programming languages. (I needed a decent markup language for my website and weblog, and didn't want to have to install any new programming languages on the machine.) Discount

Re: evolving the spec (was: forking Markdown.pl?)

In article <[EMAIL PROTECTED]>, John Fraser wrote: > >On Feb 29, 2008, at 10:13 AM, Michel Fortin wrote: > >> I think the syntax needs to be defined unambiguously, not >> necessarily as a formal grammar, but certainly not with code either. >> My idea, currently, is to write a parsing procedur

Re: evolving the spec (was: forking Markdown.pl?)

I'm going to comment both on Yuri and Waylan's message here. Le 2008-03-01 à 0:31, Waylan Limberg a écrit : On Fri, Feb 29, 2008 at 6:04 PM, Yuri Takhteyev <[EMAIL PROTECTED]> wrote: Since Joe called for procedural suggestion, here is what I think we should do: 1. First, I think there were