Re: A quick experiment with markdown

Thanks. The 1 1/2 was an easy fix, as was the <br/>.
I don't remember which definition of Markdown I was using when I started; the whole Markdown area is a bit of a mess.

Steven.

On Monday 24 October 2022 11:18:14 (+02:00), Norm Tovey-Walsh wrote:

> Steven Pemberton <steven.pemberton@cwi.nl> writes:
> > I did a little more work on it.
>
> Interesting. I happened to have a Markdown file for a sourdough crumpet
> recipe in /tmp, so I pointed it at that.
>
> It didn’t like this paragraph:
>
> You can use SR Flour, just add 1/2 teaspoon baking powder in place of
> 1 1/2 teaspoons of baking powder.
>
> The leading 1 on the second line confused it:
>
> <fail xmlns:ixml="http://invisiblexml.org/NS" ixml:state="failed">
> <line>35</line>
> <column>2</column>
> <pos>1944</pos>
> <unexpected>1</unexpected>
> <permitted>#A, ~['`#*+->'; Nd; #A]</permitted>
> </fail>
>
> I don’t think newlines in Markdown prose are supposed to be literal.
> Assuming newlines before and after, I think:
>
> Some text.
> Some more text.
>
> should be
>
> <p>Some text.
> Some more text.</p>
>
> and not
>
> <p>Some text.<br/>
> Some more text.</p>
>
> Though I suppose that depends on who’s Markdown definition your parsing.
> I mostly rely on CommonMark because it has, you know, a specification!
>
> Be seeing you,
> norm
>
> --
> Norm Tovey-Walsh
> Saxonica
>

Received on Monday, 24 October 2022 14:41:25 UTC