similar to: Fenced-Code-Blocks in Python-Markdown

I am happy to announce the release of Python-Markdown 2.0 final. We have versions for Python 2.3-2.6 and Python 3.0! See the release notes here: https://sourceforge.net/project/shownotes.php?release_id=674043&group_id=153041 Download from PyPI here: http://pypi.python.org/pypi/Markdown/2.0 -- ---- \X/ /-\ `/ |_ /-\ |\| Waylan Limberg

On Fri, Mar 14, 2008 at 11:22 PM, Michel Fortin <michel.fortin at michelf.com> wrote: > > "Safe mode" you say? Yeah, well, I didn't paint that bike shed. > > PHP Markdown also has a no-markup mode which would filter script tags > and any other HTML tags. But this doesn't prevent anyone from > inserting their own script on the page. Do you know you can

Python-markdown currently replaces all straight quotes (`"`) with the html entity (`&quot;`). Someone recently complained about this in a [bug report][]. As it turns out the quote was the symptom that brought the real problem to light[^1]. In any event, the reporter pointed out that markdown.pl does not replace straight quotes with the html entity. I know John Gruber has mentioned before

I am pleased to announce that after much hard work, a Release Candidate for Python Markdown version 2.0 is now available for [download][]. Please, download it, install it, test it, beat it... and report any [bugs][]. Assuming no major bugs, we will release 2.0 final approximately one month from today. Until then, the project [site][] will continue to document version 1.7. Updated documentation is

I just received a report [1] that the footnote output we use in Python-Markdown (an exact copy of PHP Markdown Extra [3]) is not valid HTML [3]. If you notice he's using HTML5. At least the footnote syntax does valid on XHTML1 or HTML4. Anyway, any suggestions on how the various footnote implementations want to move forward with this? [1]: https://github.com/waylan/Python-Markdown/issues/129

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

Hello, I need to to slightly extend the markdown syntax. (place an image (img tag) in text which URL has not yet been determined). Therefore I want to define something like $[Alt text](img.jpg) which would be replaced by my pre-processor with  and then sent to markdown. Is there any special syntax that should be used for such 3rd party extensions? How would you do

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

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

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

This is an Extra-only release for fixing an embarrassing bug with fenced code blocks. <http://michelf.com/projects/php-markdown/> Extra 1.2.1 (27 May 2008): * Fixed a problem where Markdown headers and horizontal rules were transformed into their HTML equivalent inside fenced code blocks. In other words, this: ~~~ # hello - - - ~~~ would generate a header and

Here's another update to PHP Markdown and PHP Markdown Extra featuring some bug fixes. See the download link on the project's page: <http://michelf.com/projects/php-markdown/> This update also features a new emphasis parser which process regular and strong emphasis in one pass instead of two and four for previous versions of PHP Markdown and PHP Markdown Extra. The new parser

Last night I released version 2.3 of Python Markdown (see the release notes [1] for all the details). In addition to various other improvements, a new **experimental** extension was included that added a syntax for generating rST-style admonitions [2]. For a summary of the syntax, see the documentation [3]. A broader sample of the output can be seen on this page [4]. The source text can be found

On 10/6/07, Lou Quillio <public at quillio.com> wrote: [snip] > Wish there were an 'Extra' for Python. > There is. Sort of. Python-Markdown has an extension interface [1]. There's a number already available and its fairly easy to write your own. I've slowly been adding many of php extra's features [2]. Unfortunately, some things are still hard, but were working to

I've rewritten the code block grammar in the Markdown Extra [spec][] to match what Markdown.pl and PHP Markdown do. It should now handle things such as this: ~~~ > One Two > Three Four Five ~~~ as one blockquote containing only one code block with five lines, equivalent to this one (using fenced code blocks instead for clarity): ~~~ > One >

Hello, I've published a Ruby gem that lets you create slide shows and author slides in plain text using a wiki-style markup language that's easy-to-write and easy-to-read. Yes, that's Markdown. (Textile is supported too ;-) You can find two samples online in Markdown: o http://slideshow.rubyforge.org/svn/samples/rest.text o

Question: what should be the output for this: > for me the point of having my blog as a static site is mainly easy deployment<br> > I don't have to worry about even configuring PHP<br> > I just put html on a web server and boom! instant win > > <footer>? [Igor Wiedler wins](https://igor.io)</footer> The real question is how to treat

Hello List, I have recently started using Michel Fortin's PHP "Markdown Extra" implementation to programmatically transform my markdown text files into HTML. Firstly I'd like to say markdown is very cool -- thanks to everyone involved :) I'd also like to suggest two additions to markdown: 1) I very often use /this/ markdown to indicate emphasis since I find it much

Hello all, I'm announcing python-markdown2 -- another Python implementation of Markdown. (MIT license.) http://code.google.com/p/python-markdown2/ It should be a drop-in replacement for [markdown.py](http://www.freewisdom.org/projects/python-markdown/). It fixes some issues that I ran into with markdown.py [^1]. I believe that it is faster than markdown.py [^2] and on par or a little

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;