| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
for documentation purposes, they are no longer being run. Perhaps I'll delete them later and add links to the online docs or something.
|
| |
|
| |
|
| |
|
|
|
|
| |
homepage).
|
| |
|
| |
|
|
|
|
| |
Also added a test. Thanks for the report.
|
|
|
|
|
| |
Also refactored the reference preprocessor to make this a little easier to
implement. Regex does more now.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
| |
Final fix to issue introduced in fix for #59. Weird stuff inside
angle brackets now also work in safe_mode='escape'. We just did the
same thing as with block html, let the (x)html searializer do the
escaping. Tests updated including the standalone test moved to match
the non-escape cases.
|
|
|
|
|
| |
Markdown markup inside angle bracktes now gets rendered properly
in all cases except when safe_mode='escape'. Also added tests.
|
| |
|
|
|
|
| |
type.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
See tests/html4_safe/html_then_blockquote.(txt|html).
It looks like having unclosed block-level html elements was causing
further processing not to happen, even in the case where we're
escaping HTML. Since we're escaping HTML, it seems like it shouldn't
affect processing at all. This changes output results in a couple
of other tests, but the new output seems reasonable to me.
|
|
|
|
|
| |
Interestingly, the change to the misc/mismatched-tags test is inline with
PHP Markdown Extra's behavior but not markdown.pl, which produces invalid html.
|
| |
|
|
|
|
| |
mode on.
|
| |
|
|
|
|
| |
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.
|
|/
|
|
| |
atomic grouping, which was slowing the HR regex down if a long HR ended with a non HR char (casing the regex to backtrack). Therefore, we have to simulate atomic grouping. Fortunately, we only need to match end-of-line or end-of-string after the atomic group here, so it was an easy case to simulate. Just remove the '$' from the end of the regex and manualy check using m.end(). The run method was refactored while I was at it, saving us from running the regex twice for each HR.
|
|
|
|
| |
differs from markdown.pl and we match markdown.pl. A few others are skipped because we have to adjust for a few edge cases. See comments in tests/php/test.cfg for details.
|
|
|
|
| |
if inlinepatterns will probably be needed for this. Putting it on hold till after 2.1-final is released.
|
| |
|
|
|
|
| |
it even though it is not documented.
|
|
|
|
| |
chars (the set defined by JG in the syntax rules). All other backslashes are passed through unaltered by the parser. If extensions want to add to the escapable chars, they can append to the list at markdown.ESCAPED_CHARS.
|
|
|
|
| |
updated.
|
|
|
|
| |
favor of testCase.assertTrue. Might as well be using the right method in our tests.
|
|
|
|
| |
unicode anyway.
|
|
|
|
| |
framework. With a simple addition to our subclass (which we then make use of), this is an easy fix.
|
|
|
|
| |
positional arguments back then.
|
|
|
|
| |
handler. Also added a note to the docs. Anyone doing their own encoding of output should be as well.
|
| |
|
|
|
|
| |
tails. Tests included.
|
|
|
|
| |
Thanks to skurfer for report and inital patch.
|
|
|
|
| |
Somehow we stopped checking for a single inline html element when swapping back in raw html. Added a test. Also patched a weird (invalid) comment test. Seeing the input is not really a valid html comment - it doesn't matter what we do with it. I suppose we test it to make sure it doesn't break the parser. Actual output is not so important. As a side note, this has exposed a preexisting (unrelated) bug with the extra extension's handling of raw html. That test is failing following this fix.
|
|
|
|
| |
previous commits. This addes the missing tests.
|
|
|
|
| |
markdown.util.etree not markdown.etree. This may be a backward incompatable change for some extensions.
|