| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
|
|
Closes #1389.
|
|
|
|
This fixed a bug wherein `--filter ./caps.py` would run `caps.py` from
the system path, even if there was a `caps.py` in the working directory.
|
|
|
|
|
|
Previously pandoc would say that a filter was not found,
even in a case where the filter had a syntax error.
|
|
Changes also include generalising the types of reader allowed. The
mechanism now mimics the more general output mechanism.
|
|
|
|
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.
|
|
Closes #1155.
|
|
Pandoc first tries to find the executable (searching the path
if path isn't given). If it fails, but the file exists and has
a .py, .pl, .rb, .hs, or .php extension, pandoc runs the filter
using the appropriate interpreter.
This should make it easier to use filters on Windows, and make
it more convenient for everyone.
Closes #1096.
|
|
|
|
The basic structure of org-mode documents is recognized; however,
org-mode features like todo markers, tags etc. are not supported yet.
|
|
This is to debug backtracking-related parsing bugs.
So far it is only implemented for markdown, but it would
be good to extend it to latex and html readers.
|
|
So, if you're using `--natbib` or `--biblatex`, you can just use
`--bibliography=foo.bib` instead of `-V bibliofiles=foo`.
|
|
Don't add pandoc-citeproc filter if natbib or biblatex is used
|
|
Remove parens enclosing a single element.
|
|
Replaces long conditional chains with calls to `elem` and `notElem`.
|
|
(Use openURL from Shared instead of simpleHTTP.)
|
|
|
|
|
|
How could this happend? sry
|
|
See https://github.com/jgm/pandoc-templates/issues/42
|
|
Note that anything not parseable as a YAML boolean or string
is treated as a literal string.
Note that you can still get a string value with "yes" or any
of the strings interpretable as booleans:
-M boolvalue=yes -M stringvalue='"yes"'
|
|
No more "resource vanished (broken pipe)"!
|
|
This also has the effect that `--bibliography` can be repeated,
as before.
|
|
|
|
But only if pandoc-citeproc isn't already specified as a filter.
|
|
This could lead to double filtering if the user specifies `-F`
too.
|
|
Also documented in README.
|
|
|
|
These are now implemented as:
--bibliography FILE => --metadata bibliography=FILE --filter pandoc-citeproc
--csl FILE => --metadata csl=FILE
--citation-abbreviations FILE => --metadata csl-abbreviations=FILE
|
|
This is like `--variable/-V`, but actually adds to metadata, not
just variables.
|
|
|
|
Going forward we'll use pandoc-citeproc, as an external filter.
The `--bibliography`, `--csl`, and `--citation-abbreviation` fields
have been removed. Instead one must include `bibliography`, `csl`,
or `csl-abbrevs` fields in the document's YAML metadata. The filter
can then be used as follows:
pandoc --filter pandoc-citeproc
The `Text.Pandoc.Biblio` module has been removed. Henceforth,
`Text.CSL.Pandoc` from pandoc-citations can be used by library users.
The Markdown and LaTeX readers now longer format bibliographies and
citations. That must be done using `processCites` or `processCites'`
from Text.CSL.Pandoc.
All bibliography-related fields have been removed from `ReaderOptions`
and `WriterOptions`: `writerBiblioFiles`, `readerReferences`,
`readerCitationStyle`.
API change.
|
|
Avoid showing spurious output and avoid double error messages.
|
|
|
|
See scripts subdirectory.
|
|
Closes #943.
|
|
Previously we used to store the directory of the first input file,
even if it was local, and used this as a base directory for
finding images in ODT, EPUB, Docx, and PDF.
This has been confusing to many users. It seems better to look for
images relative to the current working directory, even if the first
file argument is in another directory.
writerSourceURL is set to 'Just url' when the first command-line
argument is an absolute URL. (So, relative links will be resolved
in relation to the first page.) Otherwise, 'Nothing'.
The ODT, EPUB, Docx, and PDF writers have been modified accordingly.
Note that this change may break some existing workflows. If you
have been assuming that relative links will be interpreted relative
to the directory of the first file argument, you'll need to
make that the current directory before running pandoc.
Closes #942.
|
|
This way filters can figure out what the target format is
and react appropriately.
Example:
#!/usr/bin/env runghc
import Text.Pandoc.JSON
import Data.Char
main = toJSONFilter cap
where cap (Just "html") (Str xs) = Str $ map toUpper xs
cap _ x = x
This capitalizes text only for html output.
|
|
This reverts commit 2e5edbb27837372f658b1abbe05371be57415847.
|
|
This reverts commit 85dacbb282f34dc45a810d7c7b5a2d639b70e1f5.
|
|
This makes it easier to use JSON filters. Instead of
doing
pandoc -t json | ./filter | pandoc -f json
you can just do
pandoc --filter ./filter
|
|
* `Text.Pandoc.PDF` exports `makePDF` instead of `tex2pdf`.
(API change.)
* `makePDF` walks the pandoc AST and checks for the existence of
images in the local directory. If they are not found, it attempts
to find them, either in the directory containing the first source
file, or at an absolute URL, or at a URL relative to the base URL
of the first command line argument.
* Closes #917.
|
