aboutsummaryrefslogtreecommitdiffstats
path: root/markdown
Commit message (Collapse)AuthorAgeFilesLines
* Fix a minor Python 3 incompatability in the headerid extension's slugify ↵Waylan Limberg2011-07-281-1/+1
| | | | function. The url is being encoded (with errors ignored) as an easy means of removing non-ascii chars, but we have to re-encode it *before* running the regex on it, not after.
* Fixed a Python 2.4 incompatability in last commit. 'encode' only accepted ↵Waylan Limberg2011-07-281-1/+1
| | | | positional arguments back then.
* All internal encoding of output now uses the 'xmlcharrefreplace' error ↵Waylan Limberg2011-07-281-3/+6
| | | | handler. Also added a note to the docs. Anyone doing their own encoding of output should be as well.
* Stripped out encoding/decoding in the searializers.Waylan Limberg2011-07-272-48/+38
| | | | | | | | | | | | | | | | | | | | | | | Those extra steps always bothered me as being unnecessary. Additionally, this should make conversion to Python 3 easier. The 2to3 tool wasn't converting the searializers properly and we were getting byte strings in the output. Previously, this wasn't a major problem because the default searializer was the xml searializer provided in the ElementTree standard lib. However, now that we are using our own xhtml searializer, it must work smoothly in all supported versions. As a side note, I believe the thought was that we needed to do the encoding to take advantage of the "xmlcharrefreplace" error handling. However, using the example in the python [docs](http://docs.python.org/howto/unicode.html#the-unicode-type): >>> u = unichr(40960) + u'abcd' + unichr(1972) >>> u.encode('utf-8', 'xmlcharrefreplace').decode('utf-8') == u True There's no point of using the "xmlcharrefreplace" error handling if we just convert back to the original Unicode anyway. Interestingly, the Python 3 standard lib is doing essentially what we are doing here, so I'm convinced this is the right way to go.
* Fix syntax error in doctests which tripped up the 2to3 tool.Waylan Limberg2011-07-241-6/+6
|
* Fixed a few minor Python2.4 incompatabilities. Runs in 2.4-2.7 cleanly.Waylan Limberg2011-07-222-2/+8
|
* Fixed the bug exposed in 8761cd1780a7cec60123. We no longer should get empty ↵Waylan Limberg2011-07-211-2/+3
| | | | rawhtml blocks. All tests pass again.
* Fixed #31. Headers in tight lists now get inline patterns run on their ↵Waylan Limberg2011-07-211-1/+12
| | | | tails. Tests included.
* Updated toc extension's anchorlink option to work properly with recent refactor.Waylan Limberg2011-07-141-2/+6
|
* Refactored the toc extension. Fixes #33: The [TOC] marker is now ignored in ↵Waylan Limberg2011-07-141-28/+17
| | | | code blocks/spans. A better fix for #4: Only the *text* from the header is caried over to the toc (without *any* inline formatting). Also refactored the extension to better work in tandem with the refactored headerid extension and the new attr_list extension.
* Fixed #34. Better support for unicode text with the html_tidy extension. ↵Waylan Limberg2011-07-141-2/+5
| | | | Force input and output of tidy to use UTF-8 and encode before and decode after passing in the text.
* Refactored HeaderId extension to no longer include defining ids. It only ↵Waylan Limberg2011-06-302-78/+76
| | | | autogenerates ids. If you want to define your own, use the attr_list extension. Also expanded HeaderId extension to use the same algorithm as the TOC extension (which is better) for slugifying the header text. Added config settings to override the default word separator and the slugify callable. Closes #16 as the reported bug is for a removed feature.
* Fixed #30. Tables now allow three spaces of indent like PHP Markdown Extra. ↵Waylan Limberg2011-06-291-6/+7
| | | | Thanks to skurfer for report and inital patch.
* Fixed #28. Inline raw html is now enclosed in p tags. This used to work. ↵Waylan Limberg2011-06-281-1/+12
| | | | 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.
* also respect encoding when reading from a user-provided fileTravis Parker2011-06-251-1/+1
|
* Added html5 and xhtml5 output formats. These are just aliases to html4 and ↵Waylan Limberg2011-06-231-0/+4
| | | | xhtml1 searializers respectively.
* Cleaned up backward compatability of old positional arguments. Some people ↵Waylan Limberg2011-06-231-12/+44
| | | | may be using them, so we should continue to support them. Also adjusted docs to encourage using keyword args only. However, if existing code was using positional args in previous versions, it should still work.
* Added nl2br extension. Closes #13. Thanks to Brian Neal for writing the code ↵Waylan Limberg2011-06-211-0/+35
| | | | and allowing us to use it.
* Cleaned up markdown namespace. This may be a backward incompatible change ↵Waylan Limberg2011-06-201-5/+2
| | | | for some extensions. They should be importing from markdown.util
* Made the searializer wrapping code a little more dry and more clearly ↵Waylan Limberg2011-06-201-20/+10
| | | | defined the public methods.
* Updated searializers to handle boolean attributes. html gets the value only ↵Waylan Limberg2011-06-201-2/+5
| | | | and xhtml gets the key=value pair. We didn't need this prior to adding the attr_list ext.
* allow language guessing to be disabled by passing a setting to CodeHilite - ↵Rob McBroom2011-06-192-4/+17
| | | | closes #24
* Added attribute list extension inspired by Maruku's attribute list feature. ↵Waylan Limberg2011-06-171-0/+122
| | | | See issue #7. Also likely to become a replacement for the headerid extension (with a little more work - need a forceid option) which means it will also address issue #16. The extension works with some limited testing. Still needs tests and documentation. Currently breaks toc extension - which should run after attr_list, not before.
* Added our own xhtml searializer. We no longer use a xml searializer to ↵Waylan Limberg2011-06-162-21/+36
| | | | 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 #22. Horizontal rules now work in a few more crazy edge cases. Who ↵Waylan Limberg2011-06-161-1/+1
| | | | actualy useses these? Anyway, we now match markdown.pl.
* Fixed #23. Turns out markdown.pl only allows up to one space between ↵Waylan Limberg2011-06-161-2/+2
| | | | brackets in reference links. Now we do as well.
* Merge branch 'master' of https://github.com/waylan/Python-MarkdownWaylan Limberg2011-06-151-2/+2
|\
| * A few minor tweaks to the smart_strong extension. Thanks to David Chambers ↵Waylan Limberg2011-06-131-2/+2
| | | | | | | | for pointing out the typo.
* | Fixed #21. A header and paragraph not seperated by a blank line inside a ↵Waylan Limberg2011-06-151-4/+27
|/ | | | 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.
* Added smart_strong extension. Fixes Issue #17. Like PHP Markdown Extra, we ↵Waylan Limberg2011-06-072-1/+47
| | | | now include smart handling of double underscores (not just single underscores). The new behavior may be called seperately as the 'smart_strong' extension or as part of the 'extra' extension.
* Fixed #19. Improved Start Emphasis regex.Waylan Limberg2011-06-071-1/+1
|
* Added "." to the characters that may be included in implicit heading ids.David Chambers2011-06-051-1/+1
|
* Minor adjustment to previous commit. Reference links don't need unescaped as ↵Waylan Limberg2011-06-021-4/+4
| | | | they are removed before escaping takes place. Related to issue #14.
* Partial fix of issue #14. hrefs (and titles) are now unescaped, but it ↵Waylan Limberg2011-06-023-12/+25
| | | | uppears that we are loosing escaped backslashes (both in the href and in the link label in the example given in issue 14.
* Fixed #15. Setext Headers now work with any number of - or = characters.Waylan Limberg2011-06-011-1/+1
|
* Added new HTML5 block elements to known block level elementsHorst Gutmann2011-05-221-1/+3
|
* Fix #4. Links in headers no longer munge up table of contents in TOC extension.Waylan Limberg2011-05-041-3/+10
|
* Fixed typo in previous commit. Extension.getConfigs is a method, not a property.Waylan Limberg2011-05-041-1/+1
|
* Extension.getConfigs returns a dict and is used by the extensions that use ↵Waylan Limberg2011-05-046-32/+26
| | | | configs. No more self.config['name'][0] weirdness anymore.
* Minor improvement to Extension settings API. Extension.getConfig now accepts ↵Waylan Limberg2011-04-071-3/+7
| | | | a 'default' keyword and added Extension.getConfigs which returns a list of tuples of all settings without the descriptions.
* Factored out the importing of pygments in CodeHilite Extension so it doesn;t ↵Waylan Limberg2011-04-071-27/+24
| | | | happen every time a block is highlighted. Not sure why I didn't do it this way to begin with.
* Cleaned up CodeHilite extension. When pygments is not available provide ↵Waylan Limberg2011-04-071-25/+12
| | | | simpler markup which should allow for the use of JavaScript Highlighting libraries. In other words, no pygments like <div> and no <ol> for line numbering. Just a <pre><code> block with classes assinged to them. If people want fancier stuff, they can use JavaScript or create their own extension.
* Made lazy ordered lists a settable option. The previous behavior (on) is the ↵Waylan Limberg2011-04-293-12/+9
| | | | default.
* Merge commit 'refs/merge-requests/13' of ↵Waylan Limberg2011-04-281-1/+16
|\ | | | | | | git://gitorious.org/python-markdown/mainline into merge-requests/13
| * fixed startindex reset in multiple ulRohan Jain2011-04-051-6/+4
| | | | | | | | | | Now the startindex would be reset if continual unordered lists are present (tests are passed).
| * add new list item commentRohan Jain2011-04-031-0/+1
| |
| * custom index support for ol tagRohan Jain2011-04-031-1/+17
| | | | | | | | | | | | | | A ol tag with custom start index can be defined by using a different integer as the first item numbering. Search for `3. Bird` on: http://daringfireball.net/projects/markdown/syntax
* | Correctly specify minimum version of cElementTree. Fixes #5.Waylan Limberg2011-04-281-2/+2
| |
* | Corrected behavior of headerid extension to match default behavior when ↵Waylan Limberg2011-04-281-1/+4
| | | | | | | | "Weve got a problem header". We log a warning - not raise an exception.
* | Restored custom error message on UnicodeDecodeError. Otherwise we will be ↵Waylan Limberg2011-04-281-2/+6
| | | | | | | | getting bug reports all the time.