similar to: reference-style/shortcut syntax

> [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

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 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

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

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 want to use fixed font like a code block but also use italics and bold at same time. For example in HTML: <tt>$ <b>mail -u <i>user</i></b></tt> What is the best way to do this in markdown, especially if I have several lines of content that needs to be spaced out correctly? Thanks Jeremy C. Reed

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

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

I searched the list but didn't find an answer to this question. Why is the caret[^c] preferred over the asterisk[*a] for footnote markers? [^c]: http://en.wikipedia.org/wiki/Caret [*a]: http://en.wikipedia.org/wiki/Asterisk

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

I see that the well-defined order for transforming a page to HTML is: - Transform the content using the content converter ... - Replace tags I think it should be the other way around. I wrote this plugin that transform {flickr: <url of the photo>} into something like: <div> Foto, caption, etc. </div> Now, because of the order of transformations, the

Hi, I have written my own implementation of markdown in Scala. I only later realized there is already one ( <http://tristanhunt.com/projects/knockoff/> ), but I put quite some work into mine and I think it is never bad to have alternatives, so I wanted to release it anyway. I want to use the same BSD License as the original markdown, but before I put it out into the wild I wanted to ask

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.

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

Hi folks, I expect that the response to this post will be "we don't need such a thing", but humour me for a moment by pretending that in fact we do. HTML5 added a number of new tags to the mix, but arguably the most significant is the `time` element. It associates a machine-readable timestamp with a human-readable string (e.g. `<time

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

Hi everybody! As the easter holidays have now finally arrived and all the exams are over, I will have more time for webgen again! Summary ======= * Changes included in the upcoming 0.4.3 release * webgen repository * Status on 0.5.0 * Detailed information on the new 0.5.0 plugin system Changes for 0.4.3 ----------------- I have collected all mails/forum entries/ML postings in which bugs