Age | Commit message (Collapse) | Author | Files | Lines |
|
This is easier to read and maintain.
Also, formatting is now stripped from the locator prefix,
so you can write e.g. '*p.* 33'.
|
|
|
|
If suffix doesn't begin with punctuation, include opening
comma and space in result.
Previously,
@item [only a suffix]
would result in something like
Doe (2002only a suffix)
because there was no opening delimiter.
|
|
Patch from Nathan Gass.
|
|
|
|
|
|
This is more perspicuous.
|
|
* Don't look for bibliography in ~/.pandoc. Reason: doing
this requires a read + parse of the bibliography even when
the document doesn't use citations. This is a big performance
drag on regular pandoc invocations.
* Only look for default.csl if the document contains references.
Reason: avoids the need to read and parse csl file when the
document contains no references anyway.
* Removed findFirstFile from Shared.
|
|
|
|
|
|
Thus --csl behaves like --reference-odt, --template, etc.
|
|
Now we handle a suffix after a bare locator, e.g.
@item1 [p. 30, suffix]
The suffix now includes any punctuation that introduces it.
A few tests fail because of problems with citeproc (extra space
before the suffix, missing space after comma separating multiple
page ranges in the locator).
|
|
Suffixes and prefixes are now [Inline]. The locator is separated
from the citation key by a blank space. The locator consists of
one introductory word and any number of words containing at
least one digit. The suffix, if any, is separated from the locator
by a comma, and continues til the end of the citation.
|
|
|
|
|
|
citationPrefix now [Inline] rather than String;
citationSuffix added.
This change presupposes no changes in citeproc-hs.
It passes a string for these values to citeproc-hs.
Eventually, citeproc-hs should use an [Inline] for
these as well.
|
|
|
|
|
|
Added a form for in-text citations:
@doe99 [30; see also @smith99].
|
|
|
|
|
|
Patch from Andrea Rossato.
|
|
Previously '<code><a>x</a></code>' would be parsed as
Code "<a>x</a>", which is not what you want.
|
|
|
|
So,
aaa <!-- comment --> bbb
can be a single paragraph.
|
|
By Cabal policy, the API should not change depending on flags.
|
|
|
|
We now get Text.Pandoc.Definition from the new pandoc-types package.
This will make it possible for other programs to supply output
in Pandoc format, without depending on the whole pandoc package.
|
|
|
|
Patch from Andrea Rossato.
|
|
Patch from Andrea Rossato.
|
|
It seems to work better, and the default config can be used.
|
|
Patch from Andrea Rossato.
Note: the markdown syntax is preliminary and will probably change.
|
|
Added --mathjax option.
Added MathJax to HTMLMathMethod.
Supported MathJax in HTML writer.
Resolves Issue #259.
|
|
|
|
Example:
\newcommand{\plus}[2]{#1 + #2}
$\plus{3}{4}$
yields:
3+4
|
|
This avoids unwanted interpretation as optional arguments
in some contexts, which caused the brackets to silently
disappear!
|
|
Complete list: \acute, \grave, \breve, \check, \dot,
\mathring, \vec, \overrightarrow, \overleftarrow, \hat,
\tilde, \bar.
|
|
|
|
Resolves Issue #252 (pandoc doesn't properly handle unicode filenames).
|
|
Thanks to Jonathan Daugherty for the patch.
The gladTeX program gives finer control over the LaTeX environment
used to render its input. The latest version (1.1) uses the
"displaymath" environment by default, which is nice for large,
block-level equations, but it isn't so nice for inline math (where
"math" is more appropriate). This patch causes the HTML writer to
differentiate between the two by explicitly setting the LaTeX
environment on the generated EQ tag.
|
|
Now it doesn't export a writer, just some CSS and JS.
|
|
|
|
Now s5 is handled in more or less the same way as slidy,
as a variant of HTML.
|
|
S5 default is now to include links, rather than a full copy
of scripts and stylesheets.
|
|
|
|
|
|
|
|
This avoids a problem on Windows reading from stdin.
Previously we'd get an error from hGetBufNonBlocking.
|
|
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.
|