Age | Commit message (Collapse) | Author | Files | Lines |
|
Text such as /*this*/ was not correctly parsed as a strong, emphasised
word. This was due to the end-of-word recognition being to strict as it
did not accept markup chars as part of a word. The fix involves an
additional parser state field, listing the markup chars which might be
parsed as part of a word.
|
|
The default pandoc ParserState is replaced with `OrgParserState`. This
is done to simplify the introduction of new state fields required for
efficient Org parsing.
|
|
|
|
The bug: If a level 2 list was followed by a level 1 list, the first
item of the level 1 list would be lost.
Closes #1213.
|
|
|
|
|
|
Fix #1162, #1175 and rewrite textile and HTML backend to use the builder
|
|
Previously normalisation was handled by the `normalizeSpaces` function. The behavoir of the builder monoid is slightly different and melds together more items such as consecutive strings and spaces adjacent to line breaks. The tests have been changed to reflect this.
All relevant tests passed when the string melding line of the builder monoid was commented out.
|
|
element and updated files accordingly
|
|
|
|
The reader did not correctly parse inline markup. The behavoir is now as follows.
(a) The markup must start at the start of a line, be inside previous
inline markup or be preceeded by whitespace.
(b) The markup can not span across paragraphs (delimited by \n\n)
(c) The markup can not be followed by a alphanumeric character.
(d) Square brackets can be placed around the markup to avoid having
to have white space before it.
In order to make these changes it was either necessary to convert the parser to return a list of inlines or to convert the whole reader to use the builder. The latter approach whilst more work makes a bit more sense as it becomes easy to arbitarily append and prepend elements without changing the type.
Tests are accordingly updated in a later commit to reflect the different normalisation behavoir specified by the builder monoid.
|
|
Closes #1210.
|
|
If the content contains a backtick fence and there are
attributes, make sure longer fences are used to delimit the code.
Note: This works well in pandoc, but github markdown is more
limited, and will interpret the first string of three or more
backticks as ending the code block.
Closes #1206.
|
|
We now look for a \caption inside the environment; if one is
found, it is attached to the graphic or tabular found there.
Closes #1204.
|
|
This is primarily for use in the LaTeX reader, so far.
|
|
This reverts commit 82ddec698e782fef83dcd1b1fba79cd3b698c717.
|
|
Plan is to use this instead of ParserState in LP.
|
|
Removed updateHeaderMap, setHeaderMap, getHeaderMap,
updateIdentifierList, setIdentifierList, getIdentifierList.
|
|
Contrary to the previous commit message, there was no API
change, since Text.Pandoc.Parsing is not an exposed module.
|
|
Previously these were typeclasses of monads. They've been changed
to be typeclasses of states. This ismplifies the instance definitions
and provides more flexibility.
This is an API change! However, it should be backwards compatible
unless you're defining instances of HasReaderOptions, HasHeaderMap,
or HasIdentifierList. The old getOption function should work as
before (albeit with a more general type).
The function askReaderOption has been removed.
extractReaderOptions has been added.
getOption has been given a default definition.
In HasHeaderMap, extractHeaderMap and updateHeaderMap have been added.
Default definitions have been given for getHeaderMap, putHeaderMap,
and modifyHeaderMap.
In HasIdentifierList, extractIdentifierList and updateIdentifierList
have been added. Default definitions have been given for
getIdentifierList, putIdentifierList, and modifyIdentifierList.
The ultimate goal here is to allow different parsers to use their
own, tailored parser states (instead of ParserState) while still
using shared functions.
|
|
Positioning options no longer rendered verbatim.
Partially addresses #1204.
|
|
This moves \intbl after \pard.
|
|
MediaWiki reader: Accept image links in more languages
|
|
|
|
|
|
Closes #1203.
|
|
Ported from LaTeX template. Thanks to KarolS for the patch.
|
|
|
|
|
|
See #1170.
|
|
This should resolve the rest of #1170, but it needs
extensive testing.
Note that we now use a 'media' directory rather than 'images'.
|
|
src and poster will both be incorporated into content.opf
and the epub container.
This partially address #1170.
Still need to do something similar for <audio>.
|
|
Closes #1197.
Note that there are still problems with the formatting of
the tables inside tables with output produced from the input
file in the original bug report. But this fixes the stack
overflow problem.
|
|
Closes #1195.
|
|
PDF: Use / as path separators in latex input only
|
|
Fixes compile error on Windows for 5040f3e
Reverted back to canonical file separators </> in all places except for
arguments to the LaTeX builder and in TEXINPUTS
See #1151.
Note: Temporary directories still fail to be removed in Windows due to
call of ByteString.Lazy.readFile creating process ownership of the
compiled pdf file.
|
|
This is needed for texlive.
Note that the / is used only in the body of withTempDir,
so when the directory is deleted, the original separators will
be used.
See #1151.
|
|
This seems to be necessary for texlive.
Closes #1151 (again!).
|
|
Also affects EPUB writer.
Closes #877.
|
|
Closes #1188.
|
|
Closes #1133.
Note: If address is a YAML object and you just have $address$
in your template, the word "true" will appear, which may be
unexpected. (Previously nothing would appear.)
|
|
|
|
|
|
|
|
|
|
Add a simple Emacs Org-mode reader
|
|
|
|
The basic structure of org-mode documents is recognized; however,
org-mode features like todo markers, tags etc. are not supported yet.
|
|
|
|
Formerly a closing div tag would be missed if it came right
after other block-level tags.
|