similar to: Formal Grammar — some thoughts

> Anyway, a spec for Markdown Extra would contain a spec for Markdown as > well, wouldn't it? I think the whole enterprise would be a lot more valuable, if we produce a combined spec, which would be self-contained, and call it Markdown 2.0. I don't think we necessarily need a formal grammar. What we need is to create a document, starting with "Markdown Syntax" perhaps,

Has anyone seen any attempts to give Markdown a PEG (parsing expressions grammar) recognizable by some ruby PEG parser generator grammar like Treetop? http://treetop.rubyforge.org/

There's been a lot of discussion on this list about creating a formal grammar for markdown. I had a go at writing a [parsing expression grammar] for markdown. I used Haskell and John Meacham's Frisby PEG parsing library, but it should not be too hard to port the grammar to PEG libraries in other languages. [parsing expression grammar]:

While we're talking about new syntax, I thought that I'd throw out an idea I had to extend the footnote syntax as it currently exists in PHP Markdown Extra. I'm not sure that it's the best way to solve this particular problem, but I figured I'd throw it out there to get any comments on it. It relates to the problem of specifying a document's GUID. A few months back,

Hi, I'm in the process of adding support for Markdown to a minimal CMS in Rails, [Railfrog][railfrog], which uses mime types to select appropriate processing. I have had a look through the archives but have not been able to see that a consensus has emerged as to what such a mime type for Markdown should look like. My reading of the RFCs suggests that it should be within the "text/*"

Reed, Are you working on a grammar of the LLVM syntax or also on a full semantics? Steve Zdancewic's group at U. Penn. is working on a formal operational semantics for LLVM. It is partially complete and Greg Morrisett at Harvard is planning to build further on it. Regards, --Vikram Professor, Computer Science University of Illinois at Urbana-Champaign http://llvm.org/~vadve On Oct 20,

I have a doubt about the standard syntax (actually, it's the only test that maruku doesn't pass yet). Lists MUST be preceded by an empty line? So the following are only 4 paragraphs, without list items, right? ----------- Paragraph and no space: * ciao Paragraph and 1 space: * ciao Paragraph and 3 spaces: * ciao Paragraph and 4 spaces: * ciao ----------- In other words, a

I've just uploaded an implementation of markdown in C. It defines the syntax using a PEG grammar, so it should be easy to extend and modify. Right now it can produce output in either HTML or LaTeX, but it would be simple to add other output formats. It's very fast: on my machine, it converts a 178K markdown file in 0.14 seconds (vs. 9.6 seconds for the latest Markdown.pl and 0.57 seconds

Hello to all! Maruku is a Markdown interpreter written in Ruby. It is released under the GPL. Maruku implements the original Markdown syntax and all the improvements in PHP Markdown Extra. Moreover, it implements some ideas from MultiMarkdown, and adds a syntax for specifying metadata for block elements. Unlike Bluecloth, Maruku creates an in-memory representation of the document tree, and this

I can't escape backticks if on a line with other code: $ echo 'maybe use `fixed face` for `/path/to/file` by using \`back ticks\` around it' | /usr/pkg/bin/Markdown <p>maybe use <code>fixed face</code> for <code>/path/to/file</code> by using \<code>back ticks\</code> around it</p> and this is even more wrong: $ echo 'maybe use

I am doing unit-tests for Maruku and every once in a while I run into some doubts. I am posting a lot to the list, but all of these messages should be in-topic (tell me if not). Consider the input: --- `There is a literal backtick (\`) here.` `There is a literal backtick (\\`) here.` ``There is a literal backtick (`) here.`` --- The documentation says that line 2 and 3 are equivalent.

Here is another implementation of Markdown, this time in c++ using the Boost Spirit library. Spirit Markdown is written in (hopefully!) idiomatic modern c++ and a full suite of unit tests are provided. It is licensed under the Boost Software License (OSI compliant). The purpose of writing this is: * for me to gain expertise in the use of Spirit, both through direct experience and public review,

Hello all, I've began writing the parsing section of the spec, and I though I'd let you know about where I'm heading with all this. Basically, parsing is defined as three consecutive passes: parsing document elements, parsing block elements and parsing span elements. Each pass is going to contain a set of rules the parser should attempt to match while parsing the input. Rules

Hi John, there?s a bug in Markdown.pl: [foo*bar](#) [baz*quux](#) This expands to the following: <p><a href="#">foo<em>bar</a> <a href="#">baz</em>quux</a></p> Those `*` should either be disregarded or the tags should nest correctly: 1. <p><a href="#">foo*bar</a> <a

As many of you know, when a piece of open-source software languishes with bugs for 3 years it's often forked Markdown.pl is licensed under the BSD license. (do `>tail -35 /path/to/Markdown.pl`) Has anyone thought of forking and maintaining Markdown.pl (hopefully with Gruber's blessing) to fix some of the known bugs? I'm not volunteering (I'd be horrible)... just seeing if

[Note to markdown-discuss readers: for context see <http://lists.canonical.org/pipermail/kragen-hacks/2008-June/000488.html>] * Kragen Javier Sitaker <kragen at pobox.com> [2008-06-07 09:40]: > Stylesheeting comes naturally. I just put a `<style>` element > at the top with a few lines inside of it to format nicely. Note that Markdown ends up wrapping `<link>` and

FYI, There was an interest from a few people to create a formalization of Markdown as it is currently implemented. A W3C Community Group has been created for moving forward and exploring the idea and create a spec if necessary. A W3C Community Group [1] is a platform for discussing, publishing about a topic. You just need a free public W3C account [2] The community markdown group [3] has

Hi, I'm getting what I believe to be a bug. If I put the following in markdown: 1. This is a numbered list 2. Blah 9. This is another list item 10. Ok, weird bug here 11. It's really bothering me And when I run it through markdown.pl 1.01 I get out the following: <ol> <li>This is a numbered list</li> <li>Blah</li> <li>This is another

(In the following I write <tab> because my MUA strips tabs) Consider the code: ---- Paragraph <tab> <tab> Line <tab> ---- or even: ---- Paragraph <tab><space> <tab> Line <tab> ---- Markdown.pl ignores the leading blank line in the code block. Is this intended behaviour? -- Andrea Censi "Life is too important to be taken

Hi guys, I wrote a markdown based Web editor thing for my sister: http://ws.dabase.com/ And she has trouble styling blocks of markdown. Since <div markdown=1>markdown here</div> does not work on my Debian markdown binary. Is there a formal definition of markdown? Or some sort of conformance test? And certain markdown implementations I should be using, and certain ones I should be