in this case. True,
you may have users who fail to use the backticks to start with, but
the problem is easy to spot and a simple addition to your FAQ page
should cover those issues.
[1]: http://daringfireball.net/projects/markdown/syntax#code
--
Waylan Limberg
[EMAIL PROTECTED
multiple line breaks, and we have multiple blocks (code or
quotes) seperated by line breaks. How can markdown know which is
intended? I considered suggesting some force-end-of-block marker,
but that just doesn't seem right.
--
Waylan Limberg
[EMAIL PROTECTED
that the whitespace is not visable to
the editor/writer which could make it difficult for document
editors/writers to debug display problems. that said, it still makes
sense to me.
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss mailing list
Markdown
@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
and 4 spaces:
* ciao
/p
pParagraph before header:
/p
h1Header/h1
pParagraph before blockquote:
gt; Some quote.
/p
--
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http
preview (etc) to show exactly what it will like like upon
submission. However, I did notice that when the preview is switched to
'HTML Output' or 'Syntax Guide', upon returning to 'Preview' the
highlighting is lost. Just a FYI.
--
Waylan Limberg
[EMAIL PROTECTED
of the curve on this one.
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
-discuss
[4]: http://sourceforge.net/tracker/?group_id=153041
PS: We had intended on making an official announcement, but wanted to
clean some things up first. But when opportunity knocks... Well, let's
just say I felt compelled to respond.
--
Waylan Limberg
[EMAIL PROTECTED
]: http://achinghead.com/markdown/codehilite/
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
, but the
differing lengths are easy enough for my eyes to catch.
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
down to the
end.
On Dec 4, 2007 11:43 PM, Waylan Limberg [EMAIL PROTECTED] wrote:
On Dec 4, 2007 4:29 PM, Thomas Nichols [EMAIL PROTECTED] wrote:
I've been using the ~~~ syntax for marking code blocks for a few weeks,
and it's certainly an improvement over the existing four-space indent
simple rule to pick up.
If your going to do that, you might as well just use raw html. While I
agree that it looks nice, it's just more to type and too similar to
html for my tastes.
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss
/markdown-discuss
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
?
Thanks in advance.
Kind regards,
PA.
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
--
Waylan Limberg
[EMAIL PROTECTED
PROTECTED]
http://michelf.com/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
--
Waylan Limberg
[EMAIL PROTECTED
, I don't know that such a strict specification is desirable
in this instance. If you search the archives, you'll find previous
discussions on this.
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss mailing list
Markdown-Discuss
Monday) adds the ability to *escape* all raw html instead of removing
it, which would provide your desired behavior. Of course it would also
affect valid html tags in your documents. However, with the simple
extension api, it would be easy to override that behavior with your
own.
--
Waylan
must have the
spaces, then it would be *vary easy* (relatively speaking) to write
your own extension using python-markdown's extension api.
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
-discuss
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
) to define their syntax would
be nice.
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
). These
are all things we need to discuss and consider if and when a spec is
developed and I hadn't yet seen that conversation yet. Additionally, I
may not have used the best words at times and you called me on that,
so thank you.
--
Waylan Limberg
[EMAIL PROTECTED
to require the author to add a blank line between
each item? I don't.
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
!
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
, but now
I know how much effort s/he put into it. If it's obvious the author
doesn't care about it, then I probably won't be so easily persuaded by
the point s/he's trying to make. I'd say there's no harm done.
--
Waylan Limberg
[EMAIL PROTECTED
replace with a customizable
message, remove completely, or escape the html). Of course, to stay in
line with the Markdown standard, it is off by default, but very easy
to turn on in your code. Other implementations may offer a similar
option.
--
Waylan Limberg
[EMAIL PROTECTED
the entire url (perhaps replace with blank string or #)
3. Leave the markup for the entire link as plan text (in other words -
its not considered a match)
4. Do some kind of escaping (not sure what at this point) and leave it
in the url
--
Waylan Limberg
[EMAIL PROTECTED
/syntax#html
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
%2Fen.wikipedia.org%2Fwiki%2FZIP_%28file_format%29+%22ZIP+%28file+format%29+-+Wikipedia%2C+the+free+encyclopedia%22%29normalize=on
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http
%26param2%3Dvalue1%29normalize=onsrc=1dest=2
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
feel like an idiot. Thanks for
bringing me back.
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
extract the abbr defs (one per line) from it.
[1]: http://www.freewisdom.org/projects/python-markdown/
[2]: http://www.freewisdom.org/projects/python-markdown/Writing_Extensions
[3]: http://achinghead.com/markdown/abbr/
--
Waylan Limberg
[EMAIL PROTECTED
with. A review of that will
answer some of your questions about current behavior. And, we must
also never forget the (even as implementors) we should not care so
much about how hard it is to implement if it makes if easier (and more
permisive/relaxed) for the document author.
--
Waylan Limberg
(~) and ends on the
next line with the same number of consecutive tilde. Here's an
example:
Hello World!
[snip]
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss mailing
. I suspect that was the reasoning behind
Highligh.js.
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
(text)
IIRC, there was a bugfix in 1.7 that also addressed the raw html
wrapped in p tags thing. So, upgrade to 1.7 and that problem should
go away.
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss mailing list
Markdown-Discuss
, but for the above to work, then the converse
also needs to work (perhaps not technically - but for consistency)
which forces us to only accept option A - even if it's not my personal
favorite.
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss mailing list
.
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
strike against
IMO. I also think that the above option D it not only a lot harder to
implement, but also not intuitive at all. At least with A, B or C, the
user can look at the resulting list(s) and get a few clues about what
might be wrong in their source text.
--
Waylan Limberg
[EMAIL
list monkey
business that we've discussed before and no-one has bothered to
implement. Which, btw, is another reason why I like C better than A.
Either C or E works for me, but I'll settle with A as a lousy
compromise seeing it already appears to have the popular vote.
--
Waylan Limberg
[EMAIL
:
Any way of writing definition lists?
Andreas
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
--
Waylan Limberg
[EMAIL PROTECTED
.mail.ox.ac.uk%253e%3Esrc=1dest=2
--
Waylan Limberg
[EMAIL PROTECTED]
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
that
syntax when I do *not* expect the text I'm typing (i.e.: mailing list
discussions) to be feed through a markdown parser. As long as that's
the case, none of the above arguments (for or against) are relevant as
I see it.
--
Waylan Limberg
[EMAIL PROTECTED
for single-bracketed
text than I use and see on a daily basis. As I mentioned before, I see
it more as a shortcut footnote type syntax for links only when text is
expected to be read in plain text format.
--
Waylan Limberg
[EMAIL PROTECTED
On Fri, Nov 21, 2008 at 12:26 PM, Jason Blevins
[EMAIL PROTECTED] wrote:
Waylan Limberg wrote:
On Fri, Nov 21, 2008 at 11:36 AM, Jason Blevins
[EMAIL PROTECTED] wrote:
I couldn't find any discussion of it on the list, but here's the
changelog entry:
1.0.2b2 - 20 Mar 2005
.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
link PHP Extra's. Anything more than that will get raw HTML.
[1]: http://daringfireball.net/projects/markdown/syntax#html
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http
]``, or if the marker is not found, at the beginning of
the document.
[1]:
http://gitorious.org/projects/python-markdown/repos/mainline/blobs/master/markdown/extensions/toc.py
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown
of the differences in Python-Markdown's output compared to perl
and/or php have been eliminated.
* And much more... See the changelog and [Git log][] for more details.
[Git log]: http://gitorious.org/projects/python-markdown/repos/mainline/logs
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
at it, change the download
link on that page to PyPI: http://pypi.python.org/pypi/Markdown/2.0
Also, the available extensions page has some formatting issues. The
wikilinks in a nested list aren't working. Looks like a bug in your
wiki.
On Mon, Apr 6, 2009 at 10:25 PM, Waylan Limberg way...@gmail.com
. Makes sense to me.
[1]: http://daringfireball.net/projects/markdown/syntax#html
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
. But I've
already explained my position on that before.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
colons or not.
Sorry, that was supposed to say ...which *currently* support
definition lists...
Apologies for any confusion my fat fingers may have caused.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown
of work to build such a
table. A lot more than some of the existing proposals out there.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
break thousands of
existing documents.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
and is entirely
entitled to such a position. I would very likely take a simple
position if I was in his shoes and/or shared his opinion. Currently,
my opinion regarding the need for a fork/restart/refresh is
'undecided'.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
think their assumptions about newlines is way off. But otherwise,
the additions they added make sense in the context of that site.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http
://www.w3.org/TR/html5/semantics.html#the-dl-element
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
project that you
will be maintaining. What do I care?
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
On Wed, Sep 15, 2010 at 9:24 PM, Waylan Limberg way...@gmail.com wrote:
While I realize youtube can be extracted from parsing the url, by
An interesting thought just occurred to be when re-reading this. Why
do you need any special syntax at all? Why not just:
[Soda Pop Stop](http
. It's the later for me mostly.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
a rather long post mostly about why I think
javascript solutions are the better choice, even if they don't (yet)
always offer better output.
[1]: http://achinghead.com/archive/88/syntax-highlighting-web/
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
, is this something we should care about as
implementors?
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
-generated-from-source reference
should usually be in addition to the primary documentation. At least,
that is if you want a well documented project.
[1]: http://apydia.ematia.de/index.html
[2]: http://sphinx.pocoo.org/
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
://daringfireball.net/projects/markdown/syntax#html
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
#attribute_lists
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
picked datetime because that is the
name of the html attribute the same value would be assigned to. But
time is certainly shorter. Maybe you won't need either as Michel
suggests.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing
-attribute-lists
On Wed, Jul 13, 2011 at 2:53 PM, Alan Hogan cont...@alanhogan.com wrote:
Waylan, out of curiosity, which implementations are those? Is yours one?
Alan Hogan
http://blogic.com
cont...@alanhogan.com
On Wednesday, July 13, 2011 at 6:02 AM, Waylan Limberg wrote:
On Wed, Jul 13
implementation, mostly because I wasn't convinced that
Maruku's reference syntax was right.
[1]: http://maruku.rubyforge.org/proposal.html#using_tags
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
. However, the more I think about it, I'm not
really sure how that would be translated to an edit-in-place feature.
[1]:
https://github.com/waylan/Python-Markdown/blob/master/markdown/extensions/rss.py
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
/listinfo/markdown-discuss
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
you'll need to specify which
implementation you are using.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
)
Code 2
Code 3
* Another list item
If you don't want the extra paragraph, check
http://babelmark.bobtfish.net/ for implementations that don't require
it.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss
Just letting everyone know that I just released Python-Markdown 2.1.0.final.
Get from PyPi: http://pypi.python.org/pypi/Markdown/2.1.0
Read the release notes on github:
https://github.com/waylan/Python-Markdown/blob/master/docs/release-2.1.0.md
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
).
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
Python Markdown version 2.1.1 has been released.
This is a bug fix release which fixes a few bugs which caused the
parser to choke on certain edge cases.
Everyone is encouraged to upgrade.
http://pypi.python.org/pypi/Markdown/2.1.1
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
into the document. Markdown does not generally
expect to have the already generated document run through it -
although I know some people have had success using it that way in
specific controlled environments.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown
are you suggesting that output? Standard Definition
List HTML? How would that translate to a caption?
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo
On Fri, Jun 22, 2012 at 12:04 PM, Jakob ja...@gmx.at wrote:
Von: Waylan Limberg way...@gmail.com
Hmm, what HTML are you suggesting that output? Standard Definition
List HTML? How would that translate to a caption?
In the meantime I rethought my proposal, but for the sake of being backwards
and alters how it is displayed. Again, a
non-proposal as far as Markdown is concerned.
[1]: http://maruku.rubyforge.org/proposal.html#attribute_lists
[2]: http://packages.python.org/Markdown/extensions/attr_list.html
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
On Tue, Aug 7, 2012 at 2:06 PM, Michel Fortin michel.for...@michelf.ca wrote:
Le 2012-08-06 à 21:07, Waylan Limberg way...@gmail.com a écrit :
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
On Tue, Aug 7, 2012 at 10:30 PM, Michel Fortin michel.for...@michelf.ca wrote:
Le 2012-08-07 à 15:43, Waylan Limberg way...@gmail.com a écrit :
Of course, following markdown.pl's lead, the default is XHTML, so
yeah, most will never get HTML5 output. Although, I suppose we could
easily have
none of them use
rel attributes (or rev for that matter). Maybe we should just drop
that usage altogether in markdown.
On Wed, Aug 8, 2012 at 3:35 PM, Waylan Limberg way...@gmail.com wrote:
On Tue, Aug 7, 2012 at 10:30 PM, Michel Fortin michel.for...@michelf.ca
wrote:
Le 2012-08-07 à 15:43
that helps.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
mentioned, Python-Markdown also parses the url with parenthesis
correctly. I would suggest filing a bug report with whichever
implementation Stack Overflow uses and hope that that implementation is
still under active development.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss
On Wed, Oct 24, 2012 at 4:18 PM, Waylan Limberg way...@gmail.com wrote:
On Wed, Oct 24, 2012 at 4:09 PM, Thomas Maibaum thomasmaib...@gmail.com
wrote:
Hello everyone,
First off, I'm new to this list, so if this has been dealt with before, I
apologize. I was unable to find a solution
I'd use it to browse markdown.pl's source -
rather than downloading the zip file.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
ornery.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
+one%0Athe+mouse+ran+down%0A%3C%2Fpre%3E
I'm not sure if Pandoc will parse inline markdown in there or not
(some parers might if you set markdown=1 on the pre tag). And I'm not
sure how any of the above will translate to PDF. But that should get
you started.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan
Fortin
michel.for...@michelf.ca
http://michelf.ca/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
://github.com/waylan/Python-Markdown/issues/133
[9]: http://sphinx-doc.org/theming.html
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
be careful when introducing new syntax. John
MacFarlane's FAQ [2] is evidence of that.
[1]: http://daringfireball.net/projects/markdown/syntax#html
[2]: http://johnmacfarlane.net/babelmark2/faq.html
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown
guess is
that you found an edge case which tripps up the code that swaps out the
placeholders for the parsed html.
Waylan Limberg
way...@gmail.com
On Jun 28, 2013 11:55 AM, Wolfgang Faust wolfgang...@gmail.com wrote:
I was building a markdown document today when my document suddenly went
blank
/attr_list.html
[2]: http://pythonhosted.org/Markdown/extensions/definition_lists.html
[3]:http://pythonhosted.org/Markdown/extensions/extra.html
[4]:https://github.com/waylan/Python-Markdown/commit/a9ca97325e9039de90eae29fb3d8879bc9f367f6
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
There is a third-party extension to python-markdown for embedding
youtube videos in a document. You might find it interesting:
https://code.google.com/p/python-markdown-video/
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
On Thu, Nov 14, 2013 at 1:06 PM, Johannes Wärn warn.johan...@gmail.com wrote
` not in a `ol` or `ul` in not valid HTML.
Therefore markdown doesn't fix it to make it valid. Markdown's
understanding of HTML is way to limited for that.
Hope that explains things for you.
[1]: http://daringfireball.net/projects/markdown/syntax#html
--
Waylan Limberg
1 - 100 of 113 matches
Mail list logo