The reader previously did allow this, following redcloth,
which happily parses

    Html blocks can be <div>inlined</div> as well.

as

    <p>Html blocks can be <div>inlined</div> as well.</p>

This is invalid HTML, and this kind of thing can lead
to parsing problems (stack overflows) as well.  So this
commit undoes this behavior.  The above sample now produces;

    <p>Html blocks can be</p>
    <div>
    <p>inlined</p>
    </div>
    <p>as well.</p>

is built with embed_data_files. This fixes a problem with
the original 1.16 binary packages.

I'm not sure why this is needed, but it is. Otherwise
the build fails.

In 1.16 --latex-engine raises an error if a full path is
given. This commit fixes this reversion. Closes #2618.

Avoids the dreaded "the version of cabal being used has
changed" error.

https://www.reddit.com/r/haskell/comments/3f4bgr/the_version_of_cabal_being_used_has_changed/

Closes #2615.

The .stack-work directory is analogous to a cabal sandbox;
it comprises temporary build artifacts.

Add .stack-work to gitignore

Windows cmd doesn't expand wildcards; the application has to
do this.  So on windows we use 'glob' to expand.

This reverts commit 363ecfe.

Previously, if you tried to do `pandoc -s -t /path/to/lua/script.lua`,
pandoc would look for the template in
`~/.pandoc/templates/default./path/to/lua/script.lua`.
With this change it will look in the more reasonable
`~/.pandoc/templates/default.script.lua`.

This makes it possible to store default templates for custom
writers.

Closes #2625.

Closes #2626.

Continue scanning for comment subtrees beyond only the first block.

Note to self: when writing an recursive function, don't forget to, you
know, actually recurse.

Shout to @mrvdb for noticing this.

This fixes #2628.

Allow setting DEBPKGVER.
Bump to stack lts-4.0.
Make output verbose.

Fix function dropping subtrees tagged :noexport:

We get memory exhaustion on lts-4.0.  My guess is that it's
due to aeson-0.10.

…pile.

With aeson 0.10 I was getting an out of memory error on a 2GB Ubuntu
64-bit VM.

Another typo?

Fix typo in stack build files

- Text.Pandoc.XML.fromEntities:  handle entities without a
  semicolon. Always lookup character references with the
  trailing ';', even if it wasn't present.  And never add
  it when looking up numerical entities.  (This is what
  tagsoup seems to require.)
- Text.Pandoc.Parsing.characterReference:  Always lookup
  character references with the trailing ';', and leave off
  the ';' when looking up numerical entities.

This fixes a regression for e.g. `⟨`.

Issue submitted at tagsoup.

A Span is rendered with surrounding {braces}.

This was a regression in 1.16.  Closes #2624.

Closes #2645.

In cases where a match was not found for a quote, everything
from the open quote to the end of the paragraph was being dropped.

See fpco/stackage#1096.

The convention used by pandoc for figures is to mark them by prefixing
the name with "fig:".  The org reader failed to do this if a figure had
no name.  The test for this was broken as well.

This fixes #2643.

Since the 'math' is only put into the template if stMath is
set anyway, there's no need for this conditional.

Change types of divs.

From Docbook "sect#" and "simplesect" to "level#" and
"section."

Add tests.

Add mention of TEI to README.

Small changes to TEI writer.

LaTeX writer: Allow more flexible table alignment

New default is not to include `[c]` option.

Add TEI Writer.

…tei).

This avoids performance problems in documents with many identically
named headers.

Closes #2671.

API change in type of Text.Pandoc.Shared.uniqueIdent.

For example, `py` will now work as well as `python`.
Closes jgm/highlighting-kate#83.

Closes #2674.

Update license year range to 2016

See #2171.

Put them in a list in the metadata so they are all
preserved, rather than (as before) throwing out all
but one..

…mand.

This gives better results when people write e.g. `\TeX{}` in Markdown.

    \TeX{} and \LaTeX{}

now works as expected with `pandoc -f markdown -t latex`.

Closes #2687.

Cleanup of the code for link target handling.  Most notably, the
canonicalization of a link is handled by a separate function.

This fixes #2684.

We want to make sure that links have their spaces removed, and are
appropriately smushed together.

This closes #2689

…mns.

Previously these were given "left" alignment.  Better to leave off
alignment attributes altogether.

Closes #2694.

Previously smart quotes were incorrect in the following:

    '$\neg(x \in x)$'.

(because of the following period).  This commit fixes the problem,
which was introduced by commit 4229cf2.

On my end, in a clean sandbox, I had to run this before I could run the tests, I'm a cabal / haskell noob so that might not be the best way to do so but :)

Closes #2697.

CONTRIBUTING.md : update test enabling documentation

Stack installation instructions have moved to docs.haskellstack.org

Fix stack link in INSTALL

Closes #2707.

This has been tested.

Closes #2718.

cabal sdist has problems on cabal 1.16, because of our
Text.Pandoc.Data module.  So we don't test it.

It doesn't have recent enough dependencies.

The line causes an error with stack 1.0.2:

```
Could not parse '/pandoc-build/pandoc/stack.full.yaml':
AesonException "Error in $.extra-deps: failed to parse field 'extra-deps': failed to parse field extra-deps: expected [a], encountered Null"
See http://docs.haskellstack.org/en/stable/yaml_configuration.html.
```

Remove stray line from stack.full.yaml

We currently treat all memoir templates as books. This means that pandoc
will infer the `--chapters` argument, even if the `article` iption is
set for memoir.

This commit makes pandoc treats the document as an article if there is
an article option (i.e., `\documentclass[12pt,article]{memoir}`).

Note that this refactors out the parsec parsers for document class and
options, to make it a little clearer what's going on.

Make sure that we require the closing bracket.

Remove extra `be`
`overriden` → `overridden`

Fix typos in Readme

This version avoids an exponential performance problem with `<script>` tags,
and it should be faster in general.

Closes #2730.

Org reader: Refactor link-target processing

…line

Markdown writer: Use hyphens for yaml metadata block bottom line

Prefix even empty figure names with "fig:"

We don't infer `--chapters` if `article` document option is set. For
example: `\documentclass[article]{memoir}`.

This should give better performance.

See #2730.

This fixes entity-related problems.

Closes #2734.

Closes #2737.

The docx reader used to use a Modifiable typeclass to combine both
Blocks and Inlines. But all the work was in the inlines. So most of the
generality was wasted, at the expense of making the code harder to
understand. This gets rid of the generality, and adds functions for
Blocks and Inlines. It should be a bit easier to work with going forward.

Add relocatable stack build

e.g. `$$\hbox{$i$}$$`.

Partially addresses #2743.

Very Minor update on the documentation

The feature checklist in the source code was out of date. Update.

Previously an emph element could be parsed across the newline
at the end of the pipe table row.

I thought this would help with #2765, but it doesn't.

We already allowed them in the header, but not in the body
rows, for some reason.  This gives compatibility with org-mode
tables.

Fixes #2765.
Added test case.

 closes #2754

Docx Writer: handle image alt text

+ If the base path does not end with slash, the last component
  will be replaced.  E.g. base = `http://example.com/foo`
  combines with `bar.html` to give `http://example.com/bar.html`.
+ If the href begins with a slash, the whole path of the base
  is replaced.  E.g. base = `http://example.com/foo/` combines
  with `/bar.html` to give `http://example.com/bar.html`.

Closes #2777.

In order to be able to collect warnings during parsing, we add a state
monad transformer to the D monad. At the moment, this only includes a
list of warning strings (nothing currently triggers them, however). We
use StateT instead of WriterT to correspond more closely with the
warnings behavior in T.P.Parsing.

The regular readDocx just becomes a special case.

Have docx reader use it.

Traditionally pandoc operates on multiple files by first concetenating
them (around extra line breaks) and then processing the joined file. So
it only parses a multi-file document at the document scope. This has the
benefit that footnotes and links can be in different files, but it also
introduces a couple of difficulties:

  - it is difficult to join files with footnotes without some sort of
    preprocessing, which makes it difficult to write academic documents
    in small pieces.

  - it makes it impossible to process multiple binary input files, which
    can't be catted.

  - it makes it impossible to process files from different input
    formats.

This commit introduces alternative method. Instead of catting the files
first, it parses the files first, and then combines the parsed
output. This makes it impossible to have links across multiple files,
and auto-identified headers won't work correctly if headers in multiple
files have the same name. On the other hand, footnotes across multiple
files will work correctly and will allow more freedom for input formats.

Since ByteStringReaders can currently only read one binary file, and
will ignore subsequent files, we also changes the behavior to
automatically parse before combining if using the ByteStringReader. If
we use one file, it will work as normal. If there is more than one file
it will combine them after parsing (assuming that the format is the
same).

Note that this is intended to be an optional method, defaulting to
off. Turn it on with `--file-scope`.

JSON files have metadata and list structure, so they can't be simply
catted, but they're useful as intermediate build files in large projects.

Word uses list numbering styles to number its headings. We only call
something a numbered list if it does not also heave a heading style.

We don't want them to turn into a list.

Some word functions -- especially graphics -- give various choices for
content so there can be backwards compatibility. This follows the
largely undocumented feature by working through the choices until we
find one that works.

Note that we had to split out the processing of child elems of runs into
a separate function so we can recurse properly. Any processing of an
element *within* a run (other than a plain run) should go into
`childElemToRun`.

Closes #2787.

Closes #2742.

Add a `\strut` after `\crlf` before space.
Closes #2744, #2745.  Thanks to @c-foster.
This uses the fix suggested by @c-foster.

Mid-line spaces are still not supported, because of limitations
of the Markdown parser.

LaTeX writer: figure label

These aren't in stackage yet.

Instead, create it from a template, distribution.xml.in.

Regardless of input type, we should use default handling if we are
dealing with stdin. In other words, there should be no file-scope if
there are no files. This was an issue with pandoc json, which could be
piped on stdin, but which was read by default with `--file-scope`.

Note that there's no docx template.
Closes #2797.