Age | Commit message (Collapse) | Author | Files | Lines |
|
This way, you can put your special.template.latex in ~/.pandoc
and use it from any directory.
|
|
This uses lualatex to create the PDF.
|
|
Deprecated `writerXeTeX` and the `--xetex` option.
The latex writer now produces a file that can be processed
by latex, pdflatex, lualatex, or xelatex, so this option isn't
needed.
The option is still neded in markdown2pdf, however, which
has been modified to take some options that aren't in pandoc.
|
|
\verb is simply too fragile; it doesn't work inside command
arguments.
|
|
This goes with the earlier change to -halt-on-error.
|
|
This requires using a custom version of readProcessWithExitCode
that uses utf8-string's conversions instead of the system ones.
utf8-string's utf-8 conversion doesn't crash on invalid
encoding.
|
|
markdown2pdf: reading log with non-UTF8 characters
|
|
If there's a subtitle, it is added to the title,
separated by a colon and linebreak. Closes #280.
|
|
Closes #279.
|
|
Replaced 'UTF8.readFile logFile' with 'liftM toString $ BS.readFile logFile'
|
|
Before, we used -interaction=batchmode, which just ignored errors.
This leads to bad results--users should know when something goes wrong.
|
|
This prevents extra blank lines.
|
|
The indented `\end{verbatim}` was causing an extra blank line in
the output.
Closes #277.
|
|
Moved getMimeType from Text.Pandoc.Shared to Text.Pandoc.MIME,
so we won't have an API change.
|
|
This fixes a bug in ODTs containing images. LibreOffice would signal
that these ODTs were corrupt, because the manifest.xml did not contain
a reference to the image files.
|
|
|
|
Also do this when copying image files into EPUBs and ODTs.
Closes #263.
|
|
(e.g. PDFs).
Closes #264.
|
|
For example, in
Just a few glitches remaining.
<ul><li> In this situation, one loses the list.
</ul>
And in this, the preformatting.
<pre>Preformatted text not starting with its own blank line.
</pre>
Thansk to Dirk Laurie for noticing the issue.
|
|
Closes #274.
|
|
Textile reader: Make it possible to have colons after links.
|
|
|
|
* Skip spaces after <b>, <emph>, etc.
* Convert Plain elements into Para when they're in a list
item with Para, Pre, BlockQuote, CodeBlock.
An example of HTML that pandoc handles better now:
~~~~
<h4> Testing html to markdown </h4>
<ul>
<li>
<b> An item in a list </b>
<p> An introductory sentence.
<pre>
Some preformatted text
at this stage comes next.
But alas! much havoc
is wrought by Pandoc.
</pre>
</ul>
~~~~
Thanks to Dirk Laurie for reporting the issues.
|
|
* Use ctable package, which allows footnotes and
provides additional options.
* Made cell alignments work in multiline tables.
* Closes #272.
|
|
Closes #271.
|
|
|
|
|
|
Some EPUB e-readers, such as the Nook, require a meta element inside the
OPF metadata block to ensure the cover image is properly displayed.
When generating an EPUB using the `--epub-cover-image` option, this
patch adds the following meta element to the OPF metadata block in
`content.opf`:
<meta name="cover" content="cover-image" />
|
|
|
|
|
|
|
|
|
|
This prevents the code block from being interpreted as part of the list.
|
|
Otherwise LaTeX complains about \verb inside command argument.
Thanks to bbanier for reporting the bug.
|
|
Resolves Issue #304: problems with
(@item1; @item2)
because the final paren was being parsed as part of
the item key.
|
|
This reverts commit ec5410bc4e9d228b7dc0123061d80f9addf825bf.
|
|
This should make it easier to change the types later.
|
|
|
|
These previously caused infinite looping and stack overflows.
For example:
[^1]
[^1]: See [^1]
Note references are allowed in reST notes, so this isn't a full
implementation of reST. That can come later. For now we need to
prevent the stack overflows.
Partially resolves Issue #297.
|
|
This is also a cleaner way of inserting the slide divs.
Resolves Issue #296.
|
|
|
|
|
|
Instead of passing the epub cover image as a parameter, we now pass
it in the list of variables. This avoids the API change introduced
in f5cbb68534c52b292c57aaf741ab94442ddadd7a without losing the
new functionality.
|
|
|
|
CircleCode pointed out that the following markdown produces
out-of-order footnote markers in HTML:
-8<------------------------
some text^[with a footnote which will be #1]
issue
some other text^[with a footnote which will be #2]
-8<------------------------
This fixes the problem.
|
|
Thanks to Sivaram Gowkana for the patch.
|
|
So, in RST, 'http://google.com.' should be parsed as a link
to 'http://google.com' followed by a period.
The parser is smart enough to recognize balanced parentheses,
as often occur in wikipedia links: 'http://foo.bar/baz_(bam)'.
Also added ()s to RST specialChars, so '(http://google.com)'
will be parsed as a link in parens.
Added test cases.
Resolves Issue #291.
|
|
(Not just headers, as in the last patch.)
Patch from Andrea Rossato, slightly modified by JM.
|
|
API change: Added a parameter for the cover image path to
writeEPUB.
Followed best practices outlined in
http://blog.threepress.org/2009/11/20/best-practices-in-epub-cover-images/
|
|
The bug affected field lists with multi-line items at the
end of the list.
|