markdown/.git - A Python implementation of John Gruber’s Markdown with Extension support.

	Commit message (Collapse)	Author	Age	Files	Lines
*	When safe mode is 'escape', don't allow bad html to stop further processing.	Mike Dirolf	2012-01-14	4	-21/+28
\| \| \| \| \| \| \| \| \| \|	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.
*	Fixed #68. Blank line is not required after html comments.	Waylan Limberg	2012-01-15	3	-2/+12
\| \| \| \| \|	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.
*	Fixed #57. Multiline HTML Blocks no longer require a blank line after them.	Waylan Limberg	2012-01-15	3	-2/+17
\|
*	attempt at a fix for issue w/ MD links inside of html tagish stuff with safe ↵	Mike Dirolf	2012-01-12	3	-0/+5
\| \| \| \|	mode on.
*	also undo changes to the test.cfg	Daniel Gottlieb	2011-12-27	1	-4/+0
\|
*	appropriately move the tests to the fenced code documentation in the ↵	Daniel Gottlieb	2011-12-27	2	-150/+0
\| \| \| \|	extension source
*	Allow tildes or backticks in the fenced_code extension to support the syntax ↵	Daniel Gottlieb	2011-12-27	3	-1/+155
\| \| \| \|	used by github
*	Some more tests for issue #51. An upate to Marcin Kasperski's tests (which I ↵	Waylan Limberg	2011-11-17	3	-2402/+1212
\| \| \| \|	previously merged). Thanks Marcin. Also added a test for not-indented secondary lines of a first paragraph in a footnote definition.
*	Merge git://github.com/Mekk/Python-Markdown into mekk	Waylan Limberg	2011-11-17	2	-0/+10796
\|\
\| *	Example test for #51 (crash on docs with +1000 footnotes)	Marcin Kasperski	2011-11-10	2	-0/+10796
\| \|
* \|	Fixed #51. Removed recussion from footnote preproccessor. Also refactors the ↵	Waylan Limberg	2011-11-18	3	-14/+7
\| \| \| \| \| \| \| \|	code to provide a few other minor improvements s that output more closely matches php's output. Thus the changes in the tests.
* \|	Fixed #47. Improved HRProccessor.\n\nPython's re module does not support ↵	Waylan Limberg	2011-11-17	2	-1/+7
\|/ \| \| \|	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.
*	No longer skipping all tests from PHP test suite. We skip some because PHP ↵	Waylan Limberg	2011-10-06	1	-1/+38
\| \| \| \|	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.
*	Skipped 3 failing pl tests with some weird edge cases. A significant rewrite ↵	Waylan Limberg	2011-10-06	1	-0/+12
\| \| \| \|	if inlinepatterns will probably be needed for this. Putting it on hold till after 2.1-final is released.
*	Run a few more pl tests. Some of them are failing but should be easily fixable.	Waylan Limberg	2011-08-27	2	-0/+12
\|
*	Added greater-than as an escaped character. Apparently markdown.pl escapes ↵	Waylan Limberg	2011-08-27	2	-0/+3
\| \| \| \|	it even though it is not documented.
*	Fixed #39. Refactored escaping so that it only escapes a predifined set of ↵	Waylan Limberg	2011-08-17	2	-3/+0
\| \| \| \|	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.
*	Added some fadfile commands to (re)generate tests when they are added or ↵	Waylan Limberg	2011-08-04	1	-5/+38
\| \| \| \|	updated.
*	TestCase.assert_ and TestCase.failUnless are depreciated in Python 3 in ↵	Waylan Limberg	2011-07-28	1	-3/+3
\| \| \| \|	favor of testCase.assertTrue. Might as well be using the right method in our tests.
*	Skip the UnidoceDecodeError API test in Python 3.x as all input should be ↵	Waylan Limberg	2011-07-28	1	-2/+3
\| \| \| \|	unicode anyway.
*	Python 3.2 made some changes to the configparser which broke the testing ↵	Waylan Limberg	2011-07-28	2	-5/+5
\| \| \| \|	framework. With a simple addition to our subclass (which we then make use of), this is an easy fix.
*	Fixed a Python 2.4 incompatability in last commit. 'encode' only accepted ↵	Waylan Limberg	2011-07-28	1	-1/+1
\| \| \| \|	positional arguments back then.
*	All internal encoding of output now uses the 'xmlcharrefreplace' error ↵	Waylan Limberg	2011-07-28	1	-1/+1
\| \| \| \|	handler. Also added a note to the docs. Anyone doing their own encoding of output should be as well.
*	All API tests now utilize our own searializers.	Waylan Limberg	2011-07-27	1	-3/+5
\|
*	Fixed #31. Headers in tight lists now get inline patterns run on their ↵	Waylan Limberg	2011-07-21	2	-4/+4
\| \| \| \|	tails. Tests included.
*	Fixed #30. Tables now allow three spaces of indent like PHP Markdown Extra. ↵	Waylan Limberg	2011-06-29	2	-1/+62
\| \| \| \|	Thanks to skurfer for report and inital patch.
*	Fixed #28. Inline raw html is now enclosed in p tags. This used to work. ↵	Waylan Limberg	2011-06-28	3	-2/+4
\| \| \| \|	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.
*	Added test for escaping chars in link urls. Closes #14 which was fixed in ↵	Waylan Limberg	2011-06-23	2	-0/+10
\| \| \| \|	previous commits. This addes the missing tests.
*	Fixed a few failing API tests. ElementTree is only available from ↵	Waylan Limberg	2011-06-21	1	-5/+5
\| \| \| \|	markdown.util.etree not markdown.etree. This may be a backward incompatable change for some extensions.
*	Added docs and tests to attr_list ext. Closes #7.	Waylan Limberg	2011-06-20	3	-0/+55
\|
*	Added our own xhtml searializer. We no longer use a xml searializer to ↵	Waylan Limberg	2011-06-16	4	-16/+16
\| \| \| \|	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.
*	Fixed #21. A header and paragraph not seperated by a blank line inside a ↵	Waylan Limberg	2011-06-15	2	-0/+34
\| \| \| \|	list item are now parsed correctly. One of those crazy wierd edge cases that no one would ever test for, but is obvious once you see it.
*	Fixed #19. Improved Start Emphasis regex.	Waylan Limberg	2011-06-07	2	-1/+3
\|
*	Fixed #15. Setext Headers now work with any number of - or = characters.	Waylan Limberg	2011-06-01	2	-1/+9
\|
*	Added new HTML5 block elements to known block level elements	Horst Gutmann	2011-05-22	2	-0/+30
\|
*	Made lazy ordered lists a settable option. The previous behavior (on) is the ↵	Waylan Limberg	2011-04-29	4	-2/+39
\| \| \| \|	default.
*	The Testing Framework will now pass any non-reserved args set in test.cfg ↵	Waylan Limberg	2011-04-29	2	-6/+9
\| \| \| \|	files as keyword arguments to Markdown for a given syntax test. As Markdown ignores unknown args, this should be safe and will allow testing of any newly added keywords without additional modification of the testing framework.
*	Merge commit 'refs/merge-requests/13' of ↵	Waylan Limberg	2011-04-28	1	-2/+2
\|\ \| \| \| \| \| \|	git://gitorious.org/python-markdown/mainline into merge-requests/13
\| *	fixed startindex reset in multiple ul	Rohan Jain	2011-04-05	1	-2/+2
\| \| \| \| \| \| \| \| \| \|	Now the startindex would be reset if continual unordered lists are present (tests are passed).
* \|	Update tests for logging changes. No more message function.	Waylan Limberg	2011-04-28	1	-21/+6
\|/
*	Skipping codehilite test as differant versions of pygments give slightly ↵	Waylan Limberg	2010-11-04	1	-0/+2
\| \| \| \|	differant output and I'm tired of seeing the test fail when there is no real problem.
*	Fixed Ticket 74. AtomicStrings should now be ackowledged (and preserved) in ↵	Waylan Limberg	2010-11-04	1	-0/+45
\| \| \| \|	all instances. This was a real pain to debug, but an easy fix once I found it. Thanks to obs for the report.
*	Fixed previous two commits. cElementTree cannot use ElementTree nodes in the ↵	Waylan Limberg	2010-10-31	1	-2/+6
\| \| \| \|	tree, but it still uses ElementTree Comment assinged to a node's tag to test for Comment nodes. Also no longer considering Commet nodes to be block level.
*	Fixed Ticket 80. Added support for ElementTree Comments to be included by ↵	Waylan Limberg	2010-10-29	1	-0/+36
\| \| \| \|	third party extensions when using cElementTree.
*	Added short reference links. No more hanging empty brackets on reference ↵	Waylan Limberg	2010-10-11	2	-1/+11
\| \| \| \|	links; i.e., [this works]. Associated with and noted as missing when debuging Ticket 79.
*	Fixed Ticket 79. Linebreaks in reference link identifiers are now ignored. ↵	Waylan Limberg	2010-10-11	2	-1/+17
\| \| \| \|	This matches the most recent version of markdown.pl among other implementations and allows links to work after editors do autolinebreak stuff to text.
*	Fixed Ticket 71. Wrapper functions no longer do there own thing with ↵	Waylan Limberg	2010-08-29	1	-2/+2
\| \| \| \|	extensions. All behavior is now within the class.
*	Added test files for bug fix to ticket 62	Gerry LaMontagne	2010-09-02	4	-0/+70
\|
*	Fixed Ticket 70 and added a test. Footnote references whithout a ↵	Waylan Limberg	2010-08-25	2	-0/+3
\| \| \| \|	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.
*	Fixed problem hidden by Ticket 68. Defining a footnote placeholder in a ↵	Waylan Limberg	2010-08-02	2	-0/+15
\| \| \| \|	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.