Age | Commit message (Collapse) | Author | Files | Lines |
|
Uses the new gridTable in Writers.Shared, which is here
improved to better handle 0-width cells.
Closes #3516.
|
|
|
|
Rewrote functions in RST reader and writer to avoid the need
for it.
Closes #1530.
|
|
Otherwise we get invalid RST. There seems to be no
way to escape the space.
Closes #3496.
|
|
|
|
|
|
Currently the support for the `.. table` directive is a bit
limited; we don't yet support the `widths` field. But at least
you can have a proper captioned table.
|
|
|
|
Moved unsmartify to Writers.Shared.
|
|
This reverts commit f02a12aff638fa2339192231b8f601bffdfe3e14.
|
|
Since PandocMonad is an instance of MonadError, this will allow us, in a
future commit, to change all invocations of `error` to `throwError`,
which will be preferable for the pure versions. At the moment, we're
disabling the lua custom writers (this is temporary).
This requires changing the type of the Writer in Text.Pandoc. Right now,
we run `runIOorExplode` in pandoc.hs, to make the conversion easier. We
can switch it to the safer `runIO` in the future.
Note that this required a change to Text.Pandoc.PDF as well. Since
running an external program is necessarily IO, we can be clearer about
using PandocIO.
|
|
Update all writers to take into account page breaks.
A straightforwad, far from complete, implementation of page
breaks in selected writers.
Readers will have to follow in the future as well.
|
|
Previously setting writerStandalone = True did nothing unless
a template was provided in writerTemplate. Now a fragment
will be generated if writerTemplate is Nothing; otherwise,
the specified template will be used and standalone output
generated. [API change]
|
|
The bugs caused spurious blank lines in grid tables
when we had things like
blankline $$ blankline
Closes #3251.
|
|
The following markup features are used to output the lines of the `LineBlock`
element:
- AsciiDoc: a `[verse]` block,
- ConTeXt: text surrounded by `\startlines` and `\endlines`,
- HTML: `div` with an per-element style setting to interpret the content as
pre-wrapped,
- Markdown: line blocks if the `line_blocks` extension is enabled, a simple
paragraph with hard linebreaks otherwise,
- Org: VERSE block,
- RST: a line block, and
- all other formats: a paragraph, containing hard linebreaks between lines.
Custom lua writers should be updated to use the `LineBlock` element.
|
|
Closes #2615.
|
|
Added threefold wrapping option.
* Command line option: deprecated `--no-wrap`, added
`--wrap=[auto|none|preserve]`
* Added WrapOption, exported from Text.Pandoc.Options
* Changed type of writerWrapText in WriterOptions from
Bool to WrapOption.
* Modified Text.Pandoc.Shared functions for SoftBreak.
* Supported SoftBreak in writers.
* Updated tests.
* Updated README.
Closes #1701.
|
|
mb21-new-image-attributes
* Bumped version to 1.16.
* Added Attr field to Link and Image.
* Added `common_link_attributes` extension.
* Updated readers for link attributes.
* Updated writers for link attributes.
* Updated tests
* Updated stack.yaml to build against unreleased versions of
pandoc-types and texmath.
* Fixed various compiler warnings.
Closes #261.
TODO:
* Relative (percentage) image widths in docx writer.
* ODT/OpenDocument writer (untested, same issue about percentage widths).
* Update pandoc-citeproc.
|
|
This reverts commit c423dbb5a34c2d1195020e0f0ca3aae883d0749b.
|
|
This is needed for ghci to work with pandoc, given that we
now use a custom prelude.
Closes #2503.
|
|
- The (non-exported) prelude is in prelude/Prelude.hs.
- It exports Monoid and Applicative, like base 4.8 prelude,
but works with older base versions.
- It exports (<>) for mappend.
- It hides 'catch' on older base versions.
This allows us to remove many imports of Data.Monoid
and Control.Applicative, and remove Text.Pandoc.Compat.Monoid.
It should allow us to use -Wall again for ghc 7.10.
|
|
If we're producing a fragment, just skip normalization.
After all, the fragment might be somewhere in the middle
of the document. It's more important for fragments to
have consistency in rendering (so they can be pieced
together) than to normalize.
This closes #2394. It's simpler and more robust than
my earlier fix.
|
|
This reverts commit 476b383c578699567ac4630391a15855521ab3d4.
|
|
These changes are intended to make the writer more
useful to people who are processing small fragments,
which may for example look like this:
### third level header from previous section
## second level header
Previously such fragments got turned into two
headers of the same level. The new algorithm
avoids doing any normalization until we hit the
minimal-level header in the fragment (here, the
second level header).
Closes #2394.
|
|
|
|
...before Cite and Span elements that begin with a "complex"
element. Closes jgm/pandoc-citeproc#157.
|
|
E.g. `` [:sup:`3`] `` is okay; you don't need `` [:sup:`3`\ ] ``.
|
|
|
|
(mb21)
|
|
|
|
|
|
This is pretty much required by docutils.
|
|
Previously the depth was being rendered as a floating point
number with a decimal point. Thanks to Nick Yakimov for
noticing this.
|
|
We use `` :raw-latex:`...` `` and add a definition for this
role to the template.
Closes #1961.
|
|
https://ghc.haskell.org/trac/ghc/wiki/Migration/7.10#GHCsaysNoinstanceforFoldable...arisingfromtheuseof...
|
|
Now we do as before, including blank lines after list items in
loose lists (even though RST doesn't care -- this is just a matter
of visual appeal). But we chomp any excess whitespace after the
last list item, which solves #1777.
|
|
They are optional in RST (except after the last list item,
of course).
Fixes #1777.
|
|
|
|
Closes #1769.
|
|
Improves on fix to #1656.
|
|
Closes #1656.
Fixing pandoc to wrap the lines but insert spaces would be much
more complicated. This at least makes the output semantically
correct.
|
|
|
|
|
|
|
|
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 #992.
|
|
It allows fragments identifiers.
|
|
Otherwise we get indentation problems, and part of the next
paragraph may be rendered as part of the math.
|
|
Textile, MediaWiki, Markdown, Org, RST will emit raw HTML div tags for divs.
Otherwise Div and Span are "transparent" block containers.
|
|
|