similar to: Leading blank lines in codeblocks ignored?

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

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

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

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

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

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

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

I get this error: ERROR -- Invalid page file </Users/andrea/06MELANIA/censi-2006/andrea_web_site/wg/src/index.page>: Invalid structure of meta information part on a file that starts with: --- title: Sample hello page inMenu: true --- which is copied from one of the examples. I attach the whole file. -- Andrea Censi "Life is too important to be taken seriously" (Oscar

I want to create a tag processor that is activated by something like: {flickr: http://www.flickr.com/photos/censi/232006603/} (it then downloads from flickr the description of the photo -- look for example at http://www.dis.uniroma1.it/~acensi/category/sss06.html) This is my flickr.rb: load_plugin ''webgen/plugins/tags/tag_processor'' module Tags class FlickrTag <

S5 - http://meyerweb.com/eric/tools/s5/ - is an html-based slide-show system. It produces professional-looking slideshows from text with a little xml markup. Has anyone tried using Markdown to generate S5 slide-shows? I think this would be a pretty neat system. I'm thinking a level-1 header could be the slideshow title, and level-2 headers could define individual slides. Any thoughts? - Dan

> There is already a plugin in the feature request tracker (created by > Fritz Heinrichmeyer) which provides blogging and rss support > (although for webgen 0.3.8). Based on this and comments of other > people I have taken notes so as to what one would expect from such a > plugin and when I have enough time I will post them to this mailing > list for further discussion! I add

Hi, I've just posted the first public version of Showdown, a full javascript port of Markdown. It's 10KB and works in all major browsers. Try out the sample app: <http://www.attacklab.net/showdown-gui.html> Full source code is available: <http://www.attacklab.net/showdown-v0.9.zip> All the heavy lifting is done by the browser's regular expression engine, so

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

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

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

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

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 again! This is the revised revised revised proposal: http://maruku.rubyforge.org/proposal.md http://maruku.rubyforge.org/proposal.html http://maruku.rubyforge.org/proposal.pdf The main change was to use an opening string of brace+colon "{:" to not lock-up the precious "{" forever, so that in the future one could think of using the braces also for other purposes.

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