| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
* We now correctly handle field lists that are indented more than
3 spaces.
* We treat an "aafig" directive as a code block with attributes,
so it can be processed in a filter. (Closes #1212.)
|
|
Closes #1270.
|
|
|
|
Fixes #1269.
|
|
See #1269. This reveals some test failures.
|
|
|
|
Copyright housekeeping
|
|
It already worked for writer.
|
|
We now check the writerName for a lua script in pandoc.hs, so that
lowercasing and format parsing aren't done. Note this behavior
change: getWriter in Text.Pandoc no longer returns a custom writer on
input "foo.lua".
|
|
In preparation for a fix to #1267.
|
|
The documented default values of variables now agree with their true
default values as defined in Writer/HTML.hs.
|
|
Some files are no longer distributed with pandoc, the respective
copyright and licensing information is removed.
|
|
All code in pandoc licensed under the GPL version 2 or later is just
marked as being licensed under the GPL. There are multiple versions of
the GPL, most notably version 2, version 3 and the Affero GPL. As to
avoid possible confusion, licensing info is updated to be more specific
about the GPL and its version.
|
|
We use 'author' for metadata, not 'authors'.
|
|
This adds nocite citations to a metadata field, `nocite`.
These will appear in the bibliography but not in the text
(unless you use a `$nocite$` variable in your template, of
course).
|
|
Previously image links with queries were not recognized,
leading to use of an embed tag rather than an img tag.
|
|
|
|
|
|
Improvements handling of internal links
|
|
Prepend `\label{span-id}` to span contents iff `span-id` is defined.
|
|
Internal links in Org are possible by using an anchor-name as the target
of a link:
[[some-anchor][This]] is an internal link.
It links <<some-anchor>> here.
|
|
|
|
change tabs to spaces in pandoc.cabal
|
|
Previously we used 0-width spaces, an ugly hack.
Closes #980.
|
|
|
|
|
|
The change to aeson > 0.7 caused numbers to be rendered with
decimals. This change causes them to be rendered without decimals
wehn possible.
|
|
Anchors (like <<this>>) are parsed as empty spans.
|
|
This adds support for plain links (like http://zeitlens.com) and angle
links (like <http://moltkeplatz.de>).
|
|
The generated link to PEPs had a duplicate 'http://' in its URL.
|
|
This fixes a problem with duplicate extensions for fonts and
images with the same base name but different extensions.
Closes #1254.
|
|
|
|
MathMLinHTML: Fix deprecation warning
|
|
The use of `nodeValue` on `Attr` objects causes a deprecation warning in
Firefox since version 7. This patch causes calls to `value` instead of
`nodeValue` for all `Attr` objects.
This closes #362.
|
|
Org reader improvements
|
|
This adds a brief note to the COPYRIGHT file, declaring the code in the
org-reader files to be licensed under the GPL.
|
|
Use `Text.Pandoc.Shared.compactify'DL` to allow for compact definition
lists.
|
|
The function `compactify'DL`, used to change the final definition item of a
definition list into a `Plain` iff all other items are `Plain`s as well, is
useful in many parsers and hence moved into Text.Pandoc.Shared.
|
|
Footnotes can consist of multiple blocks and end only at a header or at
the beginning of another footnote. This fixes the previous behavior,
which restricted notes to a single paragraph.
|
|
Fixed a false assumption about the precedence of (&&) vs (||).
|
|
The `Table` blocktype already takes the caption as an argument, while code
blocks are wrapped in a `Div` block together with a labelling `Span`.
|
|
This adds support for LaTeX fragments like the following:
```
\begin{equation}
\int fg \mathrm{d}x
\end{equation}
```
|
|
Loose lists (i.e. lists with blankline separated items), were parsed as
multiple lists, each containing a single item. This patch fixes this
issue.
|
|
Support for standard org-blocks is improved. The parser now handles
"HTML", "LATEX", "ASCII", "EXAMPLE", "QUOTE" and "VERSE" blocks in a
sensible fashion.
|
|
|
|
This introduces a Reader environment in the style of
Text.Pandoc.Parsing.F, but adapted to the Org reader parser.
|
|
|
|
Use module description analogous to the markdown reader's.
Use (<$) where it makes sense.
|
|
9 and numbers ending in 9 would end with "IXIV."
Thanks to Jesse Rosenthal. Closes #1249.
|
|
Otherwise we have problems with integers being rendered with
decimal points.
|
