similar to: best way to use emphasis within code?

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

The following benchmarks have been obtained using the TextMate manual as the input source: <http://macromates.com/textmate/manual/source.tbz> Using PHP Markdown, parsing the 24 files separately (with the reference file appended to each of them), I get this (on an iBook G4 1.2 Ghz): Total Avg. Min. Q1. Med. Q3. Max. Parse Time (ms):

I also agree that single bracket reference-style syntax is not prudent. As Jacob suggested, it creates ambiguity for the reader (Is it an edit or a link?). It also creates a new problem of potential conflict, however rare that may be. It seems reasonable to prefix a marker colon (possibly followed by whitespace): [:ref link] or [: ref link] And perhaps the same for attributes: {:att ref} or {:

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, 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/*"

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

Happy new year! This is the revised revised proposal: http://maruku.rubyforge.org/proposal.md http://maruku.rubyforge.org/proposal.html http://maruku.rubyforge.org/proposal.pdf I wait for comments. -- Andrea Censi "Life is too important to be taken seriously" (Oscar Wilde) Web: http://www.dis.uniroma1.it/~censi

Hello to all! This is the revised 2005 proposal for meta-data, much more in detail: http://maruku.rubyforge.org/proposal.md http://maruku.rubyforge.org/proposal.html http://maruku.rubyforge.org/proposal.pdf I wait for comments. At the end of the document, there are some open issues. And I need a regexp wizard to look over the "grammar" section. Cheers, -- Andrea Censi

> [John Fraser:] Being able to wrap Markdown text in divs and spans ... I find div and span tags quite useful. Here is an example of the syntax I'm presently using. [[ {#orchard} Contents of div here. And ~this{.plum}~ is how I do spans. ]] becomes <div id="orchard"> <p>Contents of div here. And <span class="plum">this</span> is how I do

I'm currently attempting to write a spec for parsing Markdown Extra, and since one goal is to minimize the differences in output between implementations, I've made a tool allowing me to compare who does what for any given input. I hope this can also facilitate future discussions about the syntax. So here's Babelmark, a testbed for various Markdown implementations were you

So here's an interesting bug I just discovered: [Like this][d]: [here][h]. [d]: foo [h]: bar The output here should be: <a href="foo">Like this</a>: <a href="bar">here</a>. But instead the output is completely empty. I see this bug in both Markdown.pl and PHP Markdown. The problem is that all three lines are being

(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

What's the difference between: <em>emphasis</em> and <i>italicized</i> and <strong>strong</strong> and <b>bold</b> It seems to subtle for my browsers. The only "difference" I've been able to find is that according to the O'Reilly book <strong> and <emphasis> are semantic tags, while <b> and <i>

This is a new release for PHP Markdown, following Markdown.pl 1.0.2b7 from a few weeks ago. It fix the same bugs, and some more; it also introduce more radical backend changes. It can be downloaded here: <http://www.michelf.com/docs/projets/php-markdown-1.0.2b7.zip> and you can test it on the PHP Markdown Dingus: <http://www.michelf.com/projects/php-markdown/dingus/> This

Howdy, The following bug report was sent to the Debian BTS. Is there a way to have a code block immediately follow an unordered list? ----- Forwarded message from Joey Hess <joeyh at debian.org> ----- Consider this markdown: * bla * bla2 this should be treated as code block and it is not ... but if bullets are not above this, it works If the first code block is indented with

Markdowners, just a short heads-up to a newly released Markdown implementation: "pegdown" (http://github.com/sirthias/pegdown) implements a Java Markdown-to-HTML processor based on a PEG parser with the grammar being based on John MacFarlanes C implementation "peg-markdown". pegdown uses "parboiled" (http://www.parboiled.org) for the actual parsing work and, as

This update to PHP Markdown fix a bug that slipped in the WordPress interface with the last update. It also introduce a new "feature": you can now instruct the parser to ignore HTML tags and/or entities in the input. You can do this by instantiating yourself the parser and setting the `no_markup` or `no_entities` properties to true: $parser = new Markdown_Parser;

>>> I'm not sure the indentation feature is so useful. After all, you >>> can use the old syntax if you want indentation. What do you think? >> >> I'd prefer to keep it simple and leave out the indentation feature. I would also prefer to leave this out. >>> Perhaps an alternative would be to use ++++s instead of ~~~~s. >> Advantages: Not

Hello, What should the following input produce? Dutch has shifted Germanic g to the velar fricatives [?] and [x], but retained the spelling with <g> and thus at least a visual similarity to German; English and Frisian have shifted g to [j] before palatal vowels The Dingus says: <p>Dutch has shifted Germanic g to the velar fricatives [?] and [x], but retained the spelling

Does anyone know which version of Markdown is best for Wordpress? I see online that there are a few and was wondering which one people prefer. Also, is there any chance John Gruber will write an official Markdown plugin for Wordpress, given how popular it's becoming? -------------------------------------------------------- robdumas at gmail.com http://obnoxio.us/