Re: text/markdown effort in IETF (invite)

[Sreeharsha Mudivarti]

On Fri, Jul 11, 2014 at 3:58 AM, John MacFarlane  :

>
>
> Here is some math: \\(e=mc^2\\).
>
>
> Here's my current list of extensions/variations (from the pandoc
> source code).  Of course, it's nowhere near exhaustive:
>
>  Ext_footnotes   -- ^ Pandoc/PHP/MMD style footnotes
>| Ext_inline_notes-- ^ Pandoc-style inline notes
>| Ext_pandoc_title_block  -- ^ Pandoc title block
>| Ext_yaml_metadata_block -- ^ YAML metadata block


As much as admirable pandoc is, testing that is difficult.

Given that features can nested, the combinations is easily greater
than the number of lines in

https://github.com/jgm/pandoc/blob/master/tests/Tests/Readers/Markdown.hs

Markdown is an over-loaded term. It is safe to say that,
there are at-least two useful Markdowns

1) Plain

Useful for,

* Non-technical publishing
* Simple comment systems

( Markdown.pl )

2) Complete

* DocBook / Latex style publishing
* Editors

( MultiMarkdown )

A third type of Markdown can be labelled "Proprietary Markdown",
of which Github Markdown is a prime example.

Markdown implementations can give pre-processors and post-processors,
which can implement "Proprietary Extensions".

I don't understand why different things have to be conflated together.

If the IETF draft is from the perspective of publishing 1) can be ignored.
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: text/markdown effort in IETF (invite)

[Sreeharsha Mudivarti]

>
> So, you might have:  content-type="text/markdown"
> flavor="tables+titleblock" processor="floobity-1.2.3"
>
>
That looks fine, but it has too many Combinations.

I don't think Markdown should be standardised.

It is,

1) Incomplete as compared to asciidoc

2) Self-Contradicting

No general escaping

3) No formal grammar

It is typically implemented by regexes.
So unlike html, a bold phrase, can't span two lines.

In the meantime you can standardise asciidoc, multimarkdown, wikicreole
which are saner than the original markdown and they already have specs.

Makrdown dubs its formatting on email conventions.
That's not true, because email conventions are free-form ascii.
Consider this email thread, for example.

Cheers,
Harsha
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss