Re: Output of Markdown Code

The clearest way to define an input-output mapping for a spec like this is,
I think, to offer a test suite that markdown parsers can use to see if
they're up to spec. Some existing test suites are linked from
http://kramdown.rubyforge.org/tests.html

Ryan



On Tue, Nov 20, 2012 at 2:52 AM, Dave Pawson <dave.pawson@gmail.com> wrote:

> On 19 November 2012 21:40, Karl Dubost <karld@opera.com> wrote:
> >
> > Le 20 nov. 2012 à 01:11, Dave Pawson a écrit :
> >> How would you like to see the transform defined?
> >> A simple table of input to HTML output?
> >
> > I would suggest we look at what is *already* done currently. Because if
> we defined something which is not already a practice, we will have little
> chances to help people adjust their code.
> >
> > Maybe by checking the first step is to analyze the most popular
> libraries in PHP, Ruby, Python, JavaScript and just understand what they
> are doing with MarkDown markup.
> >
> >
>
> I like it.
> Specifically for semantics though, i.e. how others are defining the
> input to output mapping?
> Is that what you mean?
>
> For me clarity here is the prime goal, to make sure we consider how
> others might read it
> to stop the 'surprise' we sometimes get when we expect A and get B!
>
> regards
>
>
>
>
>
>
> --
> Dave Pawson
> XSLT XSL-FO FAQ.
> Docbook FAQ.
> http://www.dpawson.co.uk
>
>