similar to: links named after their own text

It was a very useful feature for e-mail parsing and I miss it. I use PHP Markdown extra to send multipart alternative e-mail, and the short syntax [link] instead of [link][] is very clean and lean. Do you plan to implement it anymore? Or is there a tweak to get the present PHP Markdown Extra to parse [links] as [links][]? BTW I did not find mention of this in

Taking David's example further, here is a first try: id | name | description | more info -----+---------+-------------------+----------------- 6 | Inset | An inset element | just one element 8 | Stories | Another element | another element : with 2 lines, without : colons on the left. 9 | Other

from : benoit at transmekong.com to : markdown-discuss at six.pairlist.net Subj.: Use of Markdown Extra in a forum Date : Apr 19th 2007, 15:24:25 (GMT+7) Dear all, I have tried to implement PHP Markdown Extra in a forum (PunBB) and found that however well each message is translated, there are collisions when different messages in the same page have the same inside link names (footnotes, title

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

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

I just received a [bug report] for Python-Markdown complaining that colons are used in the ids of footnotes. For reference, we [output] the same format at PHP Markdown Extra. The general complaint is that the colon in the id attribute (`id="fnref:1"`) causes jquery to choke when referencing that id from javascript because jquery uses colons to indicate pseudo elements (as does CSS). As

Time for an update to PHP Markdown and PHP Markdown Extra. <http://michelf.com/project/php-markdown/> This new version of PHP Markdown Extra adds support for "fenced" code blocks (which I was previously calling "flat"). Fenced code blocks overcome many limitations of Markdown's indented code blocks: they can can be put immediately following a list item, can

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

How can we improve URL detection in Markdown? I posted a question on Stack Overflow and happened to click a URL in my post. To my surprise, it wasn't functional, and it took three different, nonintuitive manipulations before I achieved a functional URL. Stack Overflow says "not my problem", so I'm deferring to Markdown itself. Here's a

It would be useful if defining headers (either Setext and atx style), if Markdown would also generate corresponding anchors: ## This is an H2 ## would create: <a name="This is an H2"/> <h2>This is an H2</h2> Or something like that. Or is that available some different way? Thanks, Jeremy C. Reed

Hello Everyone, Can someone spot the error in the following snippet of link text? It doesn't work through php-markdown in wordpress and I just wanted to know if there's something obvious I'm missing. Thanks in advance! can come of us. "Every good and perfect gift comes from above" ([James

2009/10/20 Lou Quillio <public at quillio.com> > On Mon, Oct 19, 2009 at 3:20 PM, AJG Baeumel > <ajgb at st-maurices.n-lanark.sch.uk> wrote: > > Why is Marksmarty no longersupported in Drupal 6.14? > > It's been a while since I've worked with Drupal, but I remember that > MarkSmarty was really just a hybrid convenience filter. It's better to > apply

Hello, As I am using markdown to write documentation, I am often tempted to make links to terms in definition lists. Since this is not possible for now (at least in php markdown extra), I was wondering if this could be a common addition in major implementation supporting definition lists. the syntax would be term {#id} : definition This syntax tries to follows current convention and

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 got a problem with UL followed by by OL when I using perl module "Text-Markdown-1.0.5". I wrote the following markdown code. - a - b 1. 1 2. 2 I expected that Text-Markdown would produce the following HTML. <ul> <li>a</li> <li>b</li> </ul> <ol> <li>1</li> <li>2</li> </ol> However, "Text-Markdown-1.0.5"

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

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

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