- From: Dave Pawson <dave.pawson@gmail.com>
- Date: Fri, 23 Nov 2012 07:32:03 +0000
- To: Markdown List <public-markdown@w3.org>
On 22 November 2012 19:44, Max Albrecht <1@178.is> wrote: > > On 22 Nov 2012, at 19:20, Shane McCarron <ahby@aptest.com> wrote: > > Beyond that, I feel it would be nice if we could avoid 'invalidating' > existing MD content that adheres to the syntax rules specified in that > original MD spec. > > > I strongly agree. > Disclaimer: I am completely new to this process, but I *think* I understood > the 'scope' of the 'baseline' as Dave explained. > But: What good is (even a 'baseline') a spec if it breaks the output of > existing content? If we followed that logic we would do nothing, i.e. accept the current syntax definition and implementations? I assume you mean accepts *all* current syntax. the baseline/core is intended to support a subset of the current MD spec, intending to support that syntax common to most implementations. I doubt it is possible to support all implementations due to lax specification and different interpretations. > > In case of the # Title #####: > What practical arguments speak against not including it? Complexity for implementers? Compare parsing that to parsing # title > > Wouldn't something along the lines of "An "ATX-Style"* Title can be followed > by any number of #-characters" be sufficent? IMHO that adds to complexity with no advantage. regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. http://www.dpawson.co.uk
Received on Friday, 23 November 2012 07:32:34 UTC