Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
+ This ensures that test-pandoc gets built.
+ 'cabal test' now runs this.
+ The old tests/RunTests.hs has been removed, and
src/test-pandoc.hs added.
|
|
Resolves Issue #274.
|
|
output.
|
|
This is necessary as the latex citation commands include there own
punctuation, which resulted in doubled commas for markdown documents
where citeproc output works correctly.
|
|
|
|
|
|
|
|
There was a bug in parsing '_emph_, ...': when followed by
a comma, underscore emphasis did not register. (Thanks to
gwern for pointing this out.)
This bug was introduced by the change in
c66921f2acea456af527b93e2daa1d8594798642
|
|
This allows different writers to handle punctuation in the suffix
differently.
|
|
|
|
|
|
|
|
|
|
E.g., Mr.
Frank.
|
|
|
|
|
|
* The recent change allowing spaces and newlines in the URL
caused problems when reference keys are stacked up without
blank lines between. This is now fixed.
* Added test.
|
|
Moved inlineNote parser after superscript parser,
so ^[link](/foo)^ gets recognized as a superscripted
link, not an inline note followed by garbage.
Thanks to Conal Elliott for pointing out the problem.
|
|
|
|
Use --template instead.
|
|
The JSON reader is about 20x faster than the native reader.
So this can be a good way to serialize a pandoc document.
|
|
Previously you'd get unexpected behavior on a document that
contained '\begin{document}' in, say, a verbatim block.
|
|
This allows library users to avoid repetitive case statements...
|
|
|
|
This is better done on the resulting HTML; use the xss-sanitize library
for this. xss-sanitize is based on pandoc's sanitization, but improves
it.
- Removed stateSanitize from ParserState.
- Removed --sanitize-html option.
|
|
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.
|
|
This change avoids repeated parsing of inline lists for 'plain'
blocks.
|
|
This is faster to parse than native.
|
|
|
|
We now parse PBS(Public Broadcasting System) as if it were
"PBS (Public Broadcasting System)".
|
|
Resolves issue #258.
Note that there are some differences in how docutils and
pandoc treat footnotes. Currently pandoc ignores the numeral
or symbol used in the note; footnotes are put in an auto-numbered
ordered list.
|
|
Don't skipNonindentSpaces in noteMarker, since it's also
used in the inline note parser.
|
|
|
|
|
|
|
|
Now “Hi” gets parsed as a Quoted DoubleQuote inline.
|
|
|
|
|
|
Previously we allowed '. . .', ' . . . ', etc. This caused
too many complications, and removed author's flexibility in
combining ellipses with spaces and periods.
|
|
+ Parameterized smartPunctuation on an inline parser.
+ Handle smartPunctuation in Textile reader.
|
|
|
|
The 'str' parser now reads internal _'s as part of the string.
This prevents pandoc from getting started looking for an emphasized
block, which can cause exponential slowdowns in some cases.
Resolves Issue #182.
|
|
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.
|
|
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.
|
|
|
|
+ Added tables.org and writer.org to tests.
+ Added org.template to templates.
+ Changed RunTests.hs as required.
+ Minor changes to Org writer.
|
|
+ Added Text/Pandoc/Writers/Org.hs
+ Added to pandoc.cabal
+ Added to pandoc.hs and Text/Pandoc.hs exports.
|
|
Conflicts:
src/Text/Pandoc/Definition.hs
|
|
The smartPuncutation parser from the markdown parser
was being used, but this creates two problems:
* smart punctuation rules are slightly different in textile,
for example, a single dash wish space around becomes an
En dash.
* the following gets parsed as a double quoted string followed
by a colon, rather than as a link:
"emphasized text":http://my.url.com
This needs rethinking.
|