Yes, I implemented an extension to Python-Markdown a few weeks back
which should be available in a release real soon now. Docs are here:
https://github.com/waylan/Python-Markdown/blob/master/docs/extensions/attr_list.txt
The other implementation is
On Wednesday, July 13, 2011 at 12:54 PM, David Parsons wrote:
Adding classes ids are kind of hideous. What I did with discount
was to extend the []() syntax to allow class: and id: pseudo-classes
(like [postoffice](class:caps) or version [2.1.0](id:v2.1.0) on spans
I can’t say I am a fan
On Jul 13, 2011, at 1:12 PM, Alan Hogan wrote:
On Wednesday, July 13, 2011 at 12:54 PM, David Parsons wrote:
Adding classes ids are kind of hideous. What I did with discount
was to extend the []() syntax to allow class: and id: pseudo-classes
(like [postoffice](class:caps) or version
It seems to me that your syntax, compared to Maruku's attribute lists, is less
powerful, less commonly implemented, and more ambiguous; and that its only
upshot is looking better to your eyes.
Fair enough? Or am I missing something?
Alan Hogan
http://blogic.com
cont...@alanhogan.com
On
According to John Gruber's syntax page
http://daringfireball.net/projects/markdown/syntax#blockquote
it is possible to nest a code block in a blockquote.
But Markdown.pl 1.0.1 shows some strange behavior in this respect.
Let me take the following text example (I use `***BEGIN**` and `***END***`
To be clear, I am 100% focused on this syntax in this email (and probably the
last email or two):
[span contents here](class:someClass)
On Wednesday, July 13, 2011 at 8:00 PM, David Parsons wrote:
You're looking at markdown like some sort of intermediate
language that's not designed for
On Jul 13, 2011, at 8:33 PM, Alan Hogan wrote:
On Wednesday, July 13, 2011 at 8:00 PM, David Parsons wrote:
You're looking at markdown like some sort of intermediate
language that's not designed for writing; I'm trying to
use existing constructs to add marginally useful features
without
