| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
generates opening double quote.
|
| |\
| |
| | |
Make smarty extension work together with attr_list
|
| | |
| |
| |
| | |
To make it easier to notice (and fix) the failure.
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Previously, the code was ignoring whether this was a new term when determining
whether the currect item should be loose or not. Fixes #243. Thanks for the
report @Anomareh.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Like headers (h1-6) dt's can only be on one line, so we need to use
the header regex on dt's. This was implemented after considering a recent
[discussion](http://six.pairlist.net/pipermail/markdown-discuss/2013-July/002859.html)
on the markdown mailing list. Prior to that discussion, I never considered
that it was impossable to set block level attrs on dt's. Now it is.
|
| |
|
|
|
|
|
|
|
|
| |
A header can be only one line - so unlike other block level elements, a
attr_list must be at th eend of the line. To disingush it from an inline
attr_list on the last child in a header, we must require at least one
space before th eblock-level attrt_list.
Always intended it to work that way. Not sure how I missed that before.
At least we're testing for it now.
|
| |
|
|
|
|
|
|
|
|
| |
Not sure how I missed that when committing ea4af0d. Also as a side-effect,
this fixes #230 - which brought my previous oversight to my attention.
Thanks for the report @divisoryang.
Also added some tests - including tests of list items without attr_lists.
Sometimes I forget to test markup that does not use an extension when an
extension is enabled. That's what resulted in #230 being reported.
|
| |
|
|
|
|
| |
A list item with a nested list complicates were the attr_list can be.
Fixes #218. Thanks for the report @jpzimmer.
|
| | |
|
| | |
|
| |
|
|
|
| |
If an adminition title is capitalized, the html class on the
div should still be lowercased.
|
| |\
| |
| |
| |
| |
| | |
Conflicts:
docs/extensions/index.txt
tests/extensions/test.cfg
|
| | |
| |
| |
| |
| |
| | |
Fixes #177. When using both extensions, breaks (`<br>`) must have a linebreak (`\n`) after them before attr_list is run. This patch reorders the treeprocessors so that happens ('attr_list' runs after 'prettify' not before).
Also had to alter headerid extension so it runs after 'prettify' or it would run before 'attr_list' if loaded before 'attr_list' by user.
|
| | |
| |
| |
| | |
Fixes #171. While that report provided an example of an unordered list item that started with a colon, any block that starts with a colon and has no siblings before it (paragraph as begining if document, list item, etc) all exhibit this same behavior. Following PHP Markdown Extra's lead, these are not definition items as they have no term before them.
|
| | |
| |
| |
| | |
crash the serealizer.
|
| | |
| |
| |
| | |
use an explicit blank title to not have the <p> tag with the title rendered.
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As HTML5 has depreciated use of `rev=anything` and `rel=footnotes`, they are no
longer inlcuded in the output when the output_format is set to HTML5. Note that
if someone successful registers a spec for `rel=footnotes` in the future (as
a microformat), then that could be considered valid. But until that happens,
it is invlaid to use in HTML5. Therefore, we remove it from the output (when
outputing HTML% only).
As an alternative, two new classes are set (in all output_formats). On the link
to the footnote (where `rel=footnotes` was used), we set `class=footnote-ref`
and on the backlink (where `rev=footnote` was used), we set
`class=footnote-backref`.
Also updated the tests to reflect to the new classes in the output.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
This is an extension which alters the behavior of lists to be less surprising.
If turned out to be rather simple to code. I'm surprised no one had written it
yet.
I should note that this extension does not generate separate lists if different
unordered list markers are used (`*` verses `-` verses `+`) The way the parser
works that would be a little more tricky.
|
| |
|
|
|
|
| |
Codehilite generates differant output with differant versiosn of pygments.
We support those various versions of pygments but can't unsure that the
same version is always available on every platform tests are run on.
|
| |
|
|
| |
type.
|
| | |
|
| | |
|
| |
|
|
| |
extension source
|
| |
|
|
| |
used by github
|
| |
|
|
| |
previously merged). Thanks Marcin. Also added a test for not-indented secondary lines of a first paragraph in a footnote definition.
|
| |\ |
|
| | | |
|
| |/
|
|
| |
code to provide a few other minor improvements s that output more closely matches php's output. Thus the changes in the tests.
|
| |
|
|
| |
Thanks to skurfer for report and inital patch.
|
| | |
|
| |
|
|
| |
output xhtml. This fixes #9 among other bugs. The test suite even had bad tests that should have been failing. They also have been corrected.
|
| |
|
|
| |
differant output and I'm tired of seeing the test fail when there is no real problem.
|
| |
|
|
| |
coresponding definition no longer raise an error. They now pass through as plain text - which is the same behavior as PHP Markdown Extra. Thanks for the report Benjamin Bach.
|
| |
|
|
| |
markdown document results in the placeholder actually being replaced. Also added a test for this. Note that if the placeholder paragraph has other text, that text is lost. Not sure if this is a bug or bad markdown syntax.
|
| |
|
|
| |
secondary lines.
|
| |
|
|
| |
This was a recently added feature, but older versions of pygments don't know what the 'tango' style is, so we now use pygemnts 'default' by default. Not sure why the 'tango' style was used here in the first place. I'm guess it was the preferance of whoever contributed the patch.
|
| |
|
|
| |
div around line numbers).
|
|
|
in everyones site-packages. We just need to distrubute them in the tarball for people to run before installing etc.
|
