Re: standard-izing extended markdown
Michel == Michel Fortin [EMAIL PROTECTED] writes: Hello Michel, Michel Well, I plan to specify and define unambiguously the syntax for Michel Markdown Extra, with an eye on keeping that spec usable to Michel implement a plain Markdown parser too. I hope to convince some Michel other Markdown implementers to follow the parsing model in that Michel spec to help improve interoperability and compatibility both Michel with standard and extra features. Hey this are good news :-) Michel You can read the current draft here: Michel http://michelf.com/specs/markdown-extra/ Thanks for the link. I stumbled upon it sometime in the past (replacing support for markdown in PHP Markdown with M-extra in CMSMS), but forgot about it... Michel Development of that spec is somewhat stalled right now, as I'm Michel working on other things. Note that these other things include an Michel experimental incremental parser for PHP Markdown and PHP Michel Markdown Extra... which could count as advancing the spec anyway Michel by looking at what is practical and what is not. (Some problems Michel with the current approach in the spec convinced me to experiment Michel a little before writing further.) Good, good. Let's hope that nice 'standard' for Markdown Extra will emerge out of it...It makes Markdown very powerful for authoring of all kinds of documents. Sincerely, Gour -- Gour | Zagreb, Croatia | GPG key: C6E7162D pgpkkJwgbzBOn.pgp Description: PGP signature ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
standard-izing extended markdown
Hello! On the markdown site it is written: Markdown’s syntax is intended for one purpose: to be used as a format for writing for the web., although recently I moved from Emacs Muse to Markdown markup for writing my study notes and plan to use it for writing technical documentation as well. However, in order to be able to use the features I had in Muse, I write using 'extended' syntax and use Pandoc to convert my study notes to *.odt (and to *.doc to my mentor), while I plan to convert markdown to ConTeXt for my own publishing needs. Pandoc will get bibliographic citations support and it already has support for stuff like footnotes, tables, and definition lists. That's why I'm interested to know what is the plan in regard to standardizing some of those 'extra' features which put markdown markup in the category of (more) serious authoring solutions? I appreciate the simplicity of markdown, but still consider that the above features do not taint the basic model, but provide powerful authoring solution along with converters like Pandoc which does LaTeX/ConTeXt/... Sincerely, Gour -- Gour | Zagreb, Croatia | GPG key: C6E7162D pgpxFxHFn4Yen.pgp Description: PGP signature ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
