summaryrefslogtreecommitdiff
path: root/tests/markdown-reader-more.native
Commit message (Collapse)AuthorAge
* Revised URI parser.John MacFarlane2013-01-15
| | | | | | | | * It no longer uses Network.URIs URI parser, which is too restrictive (not allowing unicode URIs unless encoded). * It allows many more schemes. * It better handles punctuation so as to avoid capturing trailing punctuation in bare URLs.
* Parsing: Fixed uri -- escape unicode URLs.John MacFarlane2013-01-14
| | | | | Otherwise Network.URI.parseURI fails on e.g. Chinese URLs. Changed an incorrect test in markdown-reader-more.
* Added tests for markdown line blocks and explicit header attributes.John MacFarlane2013-01-13
|
* Added Attr field to Header.John MacFarlane2013-01-09
| | | | | | | | | | Previously header ids were autogenerated by the writers. Now they are generated (unless supplied explicitly) in the markdown parser, if the `header_identifiers` extension is selected. In addition, the textile reader now supports id attributes on headers.
* Don't put the text of an autolink in Code font.John MacFarlane2013-01-06
|
* Added tests for implicit header references.John MacFarlane2013-01-03
|
* Major rewrite of markdown reader.John MacFarlane2012-08-01
| | | | | | | | | | | | | | | | | | | | | | | | | | * Use Builder's Inlines/Blocks instead of lists. * Return values in the reader monad, which are then run (at the end of parsing) against the final parser state. This allows links, notes, and example numbers to be resolved without a second parser pass. * An effect of using Builder is that everything is normalized automatically. * New exports from Text.Pandoc.Parsing: widthsFromIndices, NoteTable', KeyTable', Key', toKey', withQuoteContext, singleQuoteStart, singleQuoteEnd, doubleQuoteStart, doubleQuoteEnd, ellipses, apostrophe, dash * Updated opendocument tests. * Don't derive Show for ParserState. * Benchmarks: markdown reader takes 82% of the time it took before. Markdown writer takes 92% of the time (here the speedup is probably due to the fact that everything is normalized by default).
* Complete rewrite of LaTeX reader.John MacFarlane2012-02-04
| | | | | | | | | | | | | | | | | | | | | | | * The new reader is more robust, accurate, and extensible. It is still quite incomplete, but it should be easier now to add features. * Text.Pandoc.Parsing: Added withRaw combinator. * Markdown reader: do escapedChar before raw latex inline. Otherwise we capture commands like \{. * Fixed latex citation tests for new citeproc. * Handle \include{} commands in latex. This is done in pandoc.hs, not the (pure) latex reader. But the reader exports the needed function, handleIncludes. * Moved err and warn from pandoc.hs to Shared. * Fixed tests - raw tex should sometimes have trailing space. * Updated lhs-test for highlighting-kate changes.
* Markdown reader: Fix parsing of consecutive lists.John MacFarlane2012-01-02
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Pandoc previously behaved like Markdown.pl for consecutive lists of different styles. Thus, the following would be parsed as a single ordered list, rather than an ordered list followed by an unordered list: 1. one 2. two - one - two This patch makes pandoc behave more sensibly, parsing this as two lists. Any change in list type (ordered/unordered) or in list number style will trigger a new list. Thus, the following will also be parsed as two lists: 1. one 2. two a. one b. two Since we regard this as a bug in Markdown.pl, and not something anyone would ever rely on, we do not preserve the old behavior even when `--strict` is selected.
* Shared: Removed unescapeURI, modified escapeURI.John MacFarlane2011-12-02
| | | | | | | | | | | | escapeURI now only escapes space characters, leaving unicode characters as they are, instead of converting them to octets and URL-encoding them, as before. This gives more readable URIs. User agents now do the percent-encoding themselves. URIs are no longer unescaped at all on conversion to markdown, asciidoc, rst, org. Closes #349.
* Add support for attributes in inline Code.John MacFarlane2011-01-26
| | | | | | | | Additional related changes: * URLs in Code in autolinks now use class "url". * Require highlighting-kate 0.2.8.2, which omits the final <br/> tag, essential for inline code.
* Updated tests.John MacFarlane2011-01-26
|
* Distinguish latex & context environments; blank line after in writers.John MacFarlane2011-01-26
|
* Bumped version to 1.8; depend on pandoc-types 1.8.John MacFarlane2011-01-26
| | | | | | | The old TeX, HtmlInline and RawHtml elements have been removed and replaced by generic RawInline and RawBlock elements. All modules updated to use the new raw elements.
* Updated tests for new native format.John MacFarlane2011-01-20
|
* pandoc: Add newline to output unless standalone.John MacFarlane2011-01-06
| | | | | | | This avoids output that does not end with a newline, which is inconvenient when working with many tools. Updated tests accordingly.
* Markdown reader: Allow linebreaks in URLs (treat as spaces).John MacFarlane2010-12-10
| | | | | | Also, a string of consecutive spaces or tabs is now parsed as a single space. If you have multiple spaces in your URL, use %20%20.
* Markdown reader: handle curly quotes better.John MacFarlane2010-12-06
| | | | | | | | Previously, curly quotes were just parsed literally, leading to problems in some output formats. Now they are parsed as Quoted inlines, if --smart is specified. Resolves Issue #270.
* Fix regression: markdown references should be case-insensitive.John MacFarlane2010-12-05
| | | | | | | | | | | | | | | | This broke when we added the Key type. We had assumed that the custom case-insensitive Ord instance would ensure case-insensitive matching, but that is not how Data.Map works. * Added a test case for case-insensitivity in markdown-reader-more * Removed old refsMatch from Text.Pandoc.Parsing module; * hid the 'Key' constructor; * dropped the custom Ord and Eq instances, deriving instead; * added fromKey and toKey to convert between Keys and Inline lists; * toKey ensures that keys are case-insensitive, since this is the only way the API provides to construct a Key. Resolves Issue #272.
* Allow HTML comments as inline elements in markdown.John MacFarlane2010-11-09
| | | | | | So, aaa <!-- comment --> bbb can be a single paragraph.
* Added test for macros.John MacFarlane2010-10-26
|
* Made spacing at end of output more consistent.John MacFarlane2010-07-20
| | | | | | | | | | | | Previously some of the writers added spurious whitespace. This has been removed, resolving Issue #232. NOTE: If your application combines pandoc's output with other text, for example in a template, you may need to add spacing. For example, a pandoc-generated markdown file will not have a blank line after the final block element. If you are inserting it into another markdown file, you will need to make sure there is a blank line between it and the next block element.
* Added tests for example lists.John MacFarlane2010-07-12
|
* Added multilingual URL tests for markdown reader.John MacFarlane2010-03-23
|
* Disallow blank lines in inline code span.fiddlosopher2010-03-06
| | | | | | Also added additional test cases for markdown code spans. git-svn-id: https://pandoc.googlecode.com/svn/trunk@1860 788f1e2b-df1e-0410-8736-df70ead52e1b
* Allow multi-line titles and authors in meta block.fiddlosopher2010-02-28
| | | | | | | | | | | | | | Based on a patch by Justin Bogner. Titles may span multiple lines, provided continuation lines begin with a space character. Separate authors may be put on multiple lines, provided each line after the first begins with a space character. Each author must fit on one line. Multiple authors on a single line may still be separated by a semicolon. git-svn-id: https://pandoc.googlecode.com/svn/trunk@1854 788f1e2b-df1e-0410-8736-df70ead52e1b
* Added accessors (docTitle, docAuthors, docDate) to Meta type.fiddlosopher2010-02-28
| | | | git-svn-id: https://pandoc.googlecode.com/svn/trunk@1853 788f1e2b-df1e-0410-8736-df70ead52e1b
* Markdown reader: properly escape URIs.fiddlosopher2010-02-27
| | | | | | | | | | | | | | | + Resolves Issue #220. + Added escapeURI function to Markdown reader. This escapes links in a way that makes sense for markdown. If they've used URI escapes like %20 in their link, these will be preserved. But if they've used a special character or space without escaping it, it will be escaped. This should make sense in most cases. + Previously pandoc collapsed adjacent spaces and replaced these sequences of spaces with + characters. That isn't correct for a URI path (+ is to be used only in the query part). We've also removed the space-collapsing behavior. git-svn-id: https://pandoc.googlecode.com/svn/trunk@1847 788f1e2b-df1e-0410-8736-df70ead52e1b
* Changed Meta author and date types to Inline lists instead of Strings.fiddlosopher2009-12-31
| | | | | | | | | | | | Meta [Inline] [[Inline]] [Inline] rather than Meta [Inline] [String] String. This is a breaking change for libraries that use pandoc and manipulate the metadata. Changed .native files in test suite for new Meta format. git-svn-id: https://pandoc.googlecode.com/svn/trunk@1699 788f1e2b-df1e-0410-8736-df70ead52e1b
* Markdown reader: Treat a backslash followed by a newline as hard linebreak.fiddlosopher2009-12-05
| | | | | | Resolves Issue #154. git-svn-id: https://pandoc.googlecode.com/svn/trunk@1646 788f1e2b-df1e-0410-8736-df70ead52e1b
* Markdown reader: Use + rather than %20 for spaces in URLs.fiddlosopher2009-11-29
| | | | git-svn-id: https://pandoc.googlecode.com/svn/trunk@1633 788f1e2b-df1e-0410-8736-df70ead52e1b
* Properly handle commented-out list items in markdown.fiddlosopher2009-11-01
| | | | | | | | | | | | | Example: - a <!-- - b --> - c Resolves Issue #142. git-svn-id: https://pandoc.googlecode.com/svn/trunk@1615 788f1e2b-df1e-0410-8736-df70ead52e1b
* Fix inline math parser so that \$ is allowed in math.fiddlosopher2009-10-12
| | | | | | Resolves Issue #169. git-svn-id: https://pandoc.googlecode.com/svn/trunk@1609 788f1e2b-df1e-0410-8736-df70ead52e1b
* Gobble space after Plain blocks containing only raw html inline.fiddlosopher2009-01-31
| | | | | | | | | Otherwise following header blocks are not parsed correctly, since the parser sees blank space before them. Resolves Issue #124. git-svn-id: https://pandoc.googlecode.com/svn/trunk@1534 788f1e2b-df1e-0410-8736-df70ead52e1b
* Markdown reader: Allow blank space at end of horizontal rules.fiddlosopher2008-11-01
| | | | git-svn-id: https://pandoc.googlecode.com/svn/trunk@1480 788f1e2b-df1e-0410-8736-df70ead52e1b
* Markdown reader: cleaner handling of spaces in URLs.fiddlosopher2008-11-01
| | | | | | | | Consecutive spaces are now collapsed into one %20, and final spaces are removed. Also, a test case has been added. git-svn-id: https://pandoc.googlecode.com/svn/trunk@1477 788f1e2b-df1e-0410-8736-df70ead52e1b
* Parse raw ConTeXt environments as TeX in markdown reader.fiddlosopher2008-08-11
| | | | | | | | | | | | | | | | | | | | | | | | | | Resolves Issue #73. Also made some structural changes to parsing of raw LaTeX environments. Previously there was a special block parser for LaTeX environments. It returned a Para element containing the raw TeX inline. This has been removed, and the raw LaTeX environment parser is now used in the rawLaTeXInline parser. The effect is exactly the same, except that we can now handle consecutive LaTeX and ConTeXt environments not separated by spaces. This new flexibility is required by the example in Issue #73: \placeformula \startformula L_{1} = L_{2} \stopformula API change: The LaTeX reader now exports rawLaTeXEnvironment' (which returns a string) rather than rawLaTeXEnvironment (which returns a block element). This is more likely to be useful in other applications. Added test cases for raw ConTeXt environments to markdown-reader-more.txt. git-svn-id: https://pandoc.googlecode.com/svn/trunk@1405 788f1e2b-df1e-0410-8736-df70ead52e1b
* Allow newline before URL in markdown link references. Resolves Issue #81.fiddlosopher2008-08-10
Added tests for this issue in new "markdown-reader-more" tests. Changed RunTests.hs to run these tests. git-svn-id: https://pandoc.googlecode.com/svn/trunk@1401 788f1e2b-df1e-0410-8736-df70ead52e1b
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-27 08:19:47 +0000