jgm/pandoc

Universal markup converter

Pandoc

The universal markup converter

Pandoc is a Haskell library for converting from one markup format to another, and a command-line tool that uses this library.

It can convert from

• bibtex (BibTeX bibliography)
• biblatex (BibLaTeX bibliography)
• bits (BITS XML, alias for jats)
• commonmark (CommonMark Markdown)
• commonmark_x (CommonMark Markdown with extensions)
• creole (Creole 1.0)
• csljson (CSL JSON bibliography)
• csv (CSV table)
• tsv (TSV table)
• djot (Djot markup)
• docbook (DocBook)
• docx (Word docx)
• dokuwiki (DokuWiki markup)
• endnotexml (EndNote XML bibliography)
• epub (EPUB)
• fb2 (FictionBook2 e-book)
• gfm (GitHub-Flavored Markdown), or the deprecated and less accurate markdown_github; use markdown_github only if you need extensions not supported in gfm.
• haddock (Haddock markup)
• html (HTML)
• ipynb (Jupyter notebook)
• jats (JATS XML)
• jira (Jira/Confluence wiki markup)
• json (JSON version of native AST)
• latex (LaTeX)
• markdown (Pandoc’s Markdown)
• markdown_mmd (MultiMarkdown)
• markdown_phpextra (PHP Markdown Extra)
• markdown_strict (original unextended Markdown)
• mediawiki (MediaWiki markup)
• man (roff man)
• muse (Muse)
• native (native Haskell)
• odt (ODT)
• opml (OPML)
• org (Emacs Org mode)
• ris (RIS bibliography)
• rtf (Rich Text Format)
• rst (reStructuredText)
• t2t (txt2tags)
• textile (Textile)
• tikiwiki (TikiWiki markup)
• twiki (TWiki markup)
• typst (typst)
• vimwiki (Vimwiki)
• the path of a custom Lua reader, see Custom readers and writers below

It can convert to

• asciidoc (modern AsciiDoc as interpreted by AsciiDoctor)
• asciidoc_legacy (AsciiDoc as interpreted by asciidoc-py).
• asciidoctor (deprecated synonym for asciidoc)
• beamer (LaTeX beamer slide show)
• bibtex (BibTeX bibliography)
• biblatex (BibLaTeX bibliography)
• chunkedhtml (zip archive of multiple linked HTML files)
• commonmark (CommonMark Markdown)
• commonmark_x (CommonMark Markdown with extensions)
• context (ConTeXt)
• csljson (CSL JSON bibliography)
• djot (Djot markup)
• docbook or docbook4 (DocBook 4)
• docbook5 (DocBook 5)
• docx (Word docx)
• dokuwiki (DokuWiki markup)
• epub or epub3 (EPUB v3 book)
• epub2 (EPUB v2)
• fb2 (FictionBook2 e-book)
• gfm (GitHub-Flavored Markdown), or the deprecated and less accurate markdown_github; use markdown_github only if you need extensions not supported in gfm.
• haddock (Haddock markup)
• html or html5 (HTML, i.e. HTML5/XHTML polyglot markup)
• html4 (XHTML 1.0 Transitional)
• icml (InDesign ICML)
• ipynb (Jupyter notebook)
• jats_archiving (JATS XML, Archiving and Interchange Tag Set)
• jats_articleauthoring (JATS XML, Article Authoring Tag Set)
• jats_publishing (JATS XML, Journal Publishing Tag Set)
• jats (alias for jats_archiving)
• jira (Jira/Confluence wiki markup)
• json (JSON version of native AST)
• latex (LaTeX)
• man (roff man)
• markdown (Pandoc’s Markdown)
• markdown_mmd (MultiMarkdown)
• markdown_phpextra (PHP Markdown Extra)
• markdown_strict (original unextended Markdown)
• markua (Markua)
• mediawiki (MediaWiki markup)
• ms (roff ms)
• muse (Muse)
• native (native Haskell)
• odt (OpenOffice text document)
• opml (OPML)
• opendocument (OpenDocument)
• org (Emacs Org mode)
• pdf (PDF)
• plain (plain text)
• pptx (PowerPoint slide show)
• rst (reStructuredText)
• rtf (Rich Text Format)
• texinfo (GNU Texinfo)
• textile (Textile)
• slideous (Slideous HTML and JavaScript slide show)
• slidy (Slidy HTML and JavaScript slide show)
• dzslides (DZSlides HTML5 + JavaScript slide show)
• revealjs (reveal.js HTML5 + JavaScript slide show)
• s5 (S5 HTML and JavaScript slide show)
• tei (TEI Simple)
• typst (typst)
• xwiki (XWiki markup)
• zimwiki (ZimWiki markup)
• the path of a custom Lua writer, see Custom readers and writers below

Pandoc can also produce PDF output via LaTeX, Groff ms, or HTML.

Pandoc’s enhanced version of Markdown includes syntax for tables, definition lists, metadata blocks, footnotes, citations, math, and much more. See the User’s Manual below under Pandoc’s Markdown.

Pandoc has a modular design: it consists of a set of readers, which parse text in a given format and produce a native representation of the document (an abstract syntax tree or AST), and a set of writers, which convert this native representation into a target format. Thus, adding an input or output format requires only adding a reader or writer. Users can also run custom pandoc filters to modify the intermediate AST (see the documentation for filters and Lua filters).

Because pandoc’s intermediate representation of a document is less expressive than many of the formats it converts between, one should not expect perfect conversions between every format and every other. Pandoc attempts to preserve the structural elements of a document, but not formatting details such as margin size. And some document elements, such as complex tables, may not fit into pandoc’s simple document model. While conversions from pandoc’s Markdown to all formats aspire to be perfect, conversions from formats more expressive than pandoc’s Markdown can be expected to be lossy.

Installing

Here’s how to install pandoc.

Documentation

Pandoc’s website contains a full User’s Guide. It is also available here as pandoc-flavored Markdown. The website also contains some examples of the use of pandoc and a limited online demo.

Contributing

Pull requests, bug reports, and feature requests are welcome. Please make sure to read the contributor guidelines before opening a new issue.

License

© 2006-2023 John MacFarlane ([email protected]). Released under the GPL, version 2 or greater. This software carries no warranty of any kind. (See COPYRIGHT for full copyright and warranty notices.)

pandoc's Issues

styles in ODT output

This might be too specialized, but I'll ask anyway.

As I'm wrapping up an article manuscript, my workflow is as follows:

1. convert to ODT
2. open ODT file in OOo
3. change all paragraphs but first in section to (included by default) "First line indent" paragraph style to achieve the sort of default output in LaTeX; gets tedious for a long manuscript
4. adjust default "text body" style

Just wondering, then, if it might be valuable for pandoc to help with item 3?

I suppose I could also write a macro in OOo to handle this (not sure how hard that would be), but as I say, thought I'd ask.

Better support for literate haskell

It would be nice to be able to write literate haskell programs that could
easily be converted to various formats using pandoc. It is currently
possible to write valid literate haskell in pandoc's markdown, using
delimited code blocks:

> numbers = [1..]

But this approach has some problems. First, if the document contains
regular blockquotes, they will be treated as haskell code by GHC. Second,
it is inconvenient to have to repeat the tildes and the (optional)
{.haskell} annotation. Third, blank spaces are needed before and after the
bird-track sections. The current SVN version of pandoc collapses this
blank space, but that's not such desirable behavior in general (what if one
wants a code block with leading or trailing blank lines?) (The blank-space
requirement can be turned off in ghc using the flags '-optL -q', but it is
not ideal to expect people to know or remember this.)

Here is a proposal. Add a new command-line flag, '--lhs', to indicate that
the input file is literate haskell. (This can be turned on automatically
if the extension is '.lhs'.) When '--lhs' is specified and the input
format is markdown, bird-track sections are treated as code blocks (with
class attribute "haskell"), not as block quotes. Indented code blocks are
still treated as code blocks.

When '--lhs' is specified and the input is latex, special lhs-specific
constructions are recognized (e.g. \begin{code}...\end{code}).

'--lhs' could have an effect on output as well. Obviously, for markdown
output it would output haskell code blocks in bird tracks. (What about
HTML output? Probably bird tracks should be used there, too, so people
could cut and paste from the HTML and have valid lhs.)

Google Code Info:
Issue #: 89
Author: [email protected]
Created On: 2008-10-07T00:00:15.000Z
Closed On: 2008-12-02T22:48:16.000Z

hsmarkdown / pandoc convert " " to "+" in [img] syntax

Originally filed by nfjinjing on 2010-02-25T02:31:47

What steps will reproduce the problem?

echo "" | hsmarkdown

What is the expected output? What do you see instead?

expected: markdown.pl gives:

!test image

I see: hsmarkdown gives:

</p

What version of the product are you using? On what operating system?

pandoc-1.4, mac / linux both reproducible

Please provide any additional information below.

none

`markdown2pdf` crash when using verbatim in table caption

I was expecting to be able to use verbatim code in a table's caption, but LaTeX doesn't obey. This might be a LaTeX limitation, but it would be nice if markdown2pdf could clean this up before handing it to the (limited) writer.

This document does not work

 1  2
-- --
 a  b

Table: broken caption with `verbatim`

Unexpected results from html/markdown conversions for arrow character.

Command:

echo "

This is a line of < text and more > text.

" | pandoc -f html -t markdown --
strict | pandoc -f markdown -t html --strict

Expected output:

This is a line of < text and more > text.

Actual output:

This is a line of \ text.

Seems like pandoc gets escaping of "<" wrong? - and also eats up space to ">".
Removing the --strict from the last conversions gives me the expected result.

pandoc 0.46 on FreeBSD 7.0.

Google Code Info:
Issue #: 96
Author: [email protected]
Created On: 2008-10-22T20:49:10.000Z
Closed On: 2009-07-18T19:16:59.000Z

hsmarkdown / pandoc convert " " to "+" in [img] syntax

What steps will reproduce the problem?

echo "" | hsmarkdown

What is the expected output? What do you see instead?

expected: markdown.pl gives:

!test image

I see: hsmarkdown gives:

</p

What version of the product are you using? On what operating system?

pandoc-1.4, mac / linux both reproducible

Please provide any additional information below.

none

Google Code Info:
Issue #: 220
Author: [email protected]
Created On: 2010-02-25T02:31:47.000Z
Closed On: 2010-02-27T03:09:14.000Z

Raw HTML in man output

pandoc -t man
Hi

The output contains the raw HTML comment (or any other HTML).
This is a bug, I think.

Also check behavior of other output formats with raw HTML,
and especially with HTML comments.

Google Code Info:
Issue #: 183
Author: [email protected]
Created On: 2009-12-07T08:34:39.000Z
Closed On: 2009-12-07T23:34:54.000Z

Space around $$ in markdown display math

Currently pandoc requires that the $$ that mark out a display math
environment are adjacent to the math itself:
yes: $$e = mc^2$$
no: $$ e = mc^2 $$
But it is natural to write display math on a separate line:
$$
e = mc^2
$$
and there seems to be little danger of capturing $'s used to indicate
currency when they are doubled like this.

So, I propose to change pandoc's behavior to allow space after the opening
$$ and before the closing $$.

Google Code Info:
Issue #: 105
Author: [email protected]
Created On: 2008-11-09T00:36:09.000Z
Closed On: 2008-11-25T00:09:35.000Z

Book references not working, when ISBN field present

What steps will reproduce the problem?

1. Use citations, with a BibTex format bibliography
2. Reference a book, whose bibtext record contains an ISBN

What is the expected output? What do you see instead?

Citation isn't produced in the output.

What version of the product are you using? On what operating system?
1.8.1.1 Compiled with citeproc support.

pandoc doesn't correctly handle unicode filenames

Originally filed by fiddlosopher on 2010-08-21T16:19:23

% pandoc Náó.page
pandoc: N??.page: openBinaryFile: does not exist (No such file or directory)
% ls Náó.page
Náó.page

LaTeX Reader: Expects Document to end after \end{document}

I commonly see documents with comments after \end{document}. Pandoc should be able to ignore the text after the \end{document} command.

HTML Tags include carriage return before >

All tags are similar to:

><li
  >

Option to use xetex in markdown2pdf

Patch due to Jonas Smedegaard:

--- a/markdown2pdf
+++ b/markdown2pdf
@@ -1,7 +1,8 @@
#!/bin/sh -e

-REQUIRED="pdflatex"
-SYNOPSIS="converts markdown-formatted text to PDF, using pdflatex."
+PDFTEX="pdflatex"
+REQUIRED="$PDFTEX"
+SYNOPSIS="converts markdown-formatted text to PDF, using $PDFTEX."

THIS=${0##*/}

@@ -87,9 +88,9 @@
finished=no
runs=0
while [ $finished = "no" ]; do

•  pdflatex -interaction=batchmode $texname.tex >/dev/null || {
  

•  $PDFTEX -interaction=batchmode $texname.tex >/dev/null || {
   errcode=$?
  

•    err "${THIS}: pdfLaTeX failed with error code $errcode"
  

•    err "${THIS}: $PDFTEX failed with error code $errcode"
   [ -f $texname.log ] && {
     err "${THIS}: error context:"
     sed -ne '/^!/,/^[[:space:]]*$/p' \
  

New LaTeX.header (will work with both xetex and pdflatex):

\documentclass{article}
\usepackage{ifpdf,ifxetex}
\ifxetex
\usepackage{fontspec,xltxtra,xunicode}
\else
\usepackage[utf8x]{inputenc}
\fi
\usepackage{amsmath}
\usepackage[mathletters]{ucs}
\usepackage{listings}
\lstnewenvironment{code}{\lstset{language=Haskell,basicstyle=\small\ttfamily}}{
}
\setlength{\parindent}{0pt}
\setlength{\parskip}{6pt plus 2pt minus 1pt}

Google Code Info:
Issue #: 185
Author: [email protected]
Created On: 2009-12-12T16:49:46.000Z
Closed On: 2009-12-31T01:18:08.000Z

default language for codeblocks

see the text below for a description of the enhancement, which i posted
recently to pandoc-discuss.

a diff is attached; please feel free to use/modify/ignore it.

note that i have not updated README to mention the new option

---

i love the new syntax-highlighting of codeblocks, but the one downside
for me is having to use delimited-codeblock sytax and the language
annotation for all my code snippets, where previously the indented-
code syntax was so simple and readable.

but it was easy (what nice code!) to add a --default-codeblock-class
option to pandoc, which is then used to populate a new writer option
that specifies the classes to use for a codeblock when none have been
specified (which is the result of an indentation-style codeblock).

now all my code is magically highlighted, without changing the
markdown at all! (and for the rare case of code that shouldn't be
highlighted, i can use the delimited syntax to give some non-assigned
"language" like "ignore".)

Google Code Info:
Issue #: 87
Author: [email protected]
Created On: 2008-10-03T23:05:03.000Z
Closed On: 2009-12-01T06:56:47.000Z

--sanitize-html should whitelist URIs in links

Currently pandoc allows links to execute scripts, even when
--sanitize-html is supplied. For example:

[link](jAvAsCrIpT:alert%28'Hello%20world!'%29)

http://www.mail-archive.com/[email protected]/msg01186.html

The best approach seems to be whitelisting URIs in sanitize mode.
As a first approximation: allow (http:|ftp:|mailto:|news:)?[^:]+
Anything else to include/exclude?
Or use the URI parser?

Google Code Info:
Issue #: 62
Author: [email protected]
Created On: 2008-03-15T16:09:46.000Z
Closed On: 2008-03-22T20:43:18.000Z

A css footnotes option for html writer

Hello John,

Perhaps you may consider adding a css footnotes option to the HTML writer?

The princexml formatter converts (X)HTML or XML to PDF using CSS paged media.
All footnote related processing is done via the formatter and CSS. All that is required in the
HTML, is an inline span with class "footnote" containing the actual footnote content, as below:

... figure with a caption.<span class="footnote"><p>This feature is not yet implemented for RTF, OpenDocument, or ODT. In those formats, you'll just get an image in a paragraph by itself, with no caption.</p></span> (In LaTeX ...

This implies that the HTML writer insert the footnote content, as a span in the document, where the footnote number should appear.
The reference links, backlinks, and list of footnotes at the document end, become superfluous.

It would be really neat if you could add an option to pandoc to accomplish this, perhaps:
pandoc --css-footnote

Currently, I run a script to change my HTML output prior to producing the PDF.
I think only princexml supports this, (other browers likely won't) so it's hardly a priority, but would
be greatly appreciated.

Thank you for all your structured procrastination on pandoc, it makes my life much easier.
Regards
Laurence R Buchanan

pandoc: ð: openFile: does not exist (No such file or directory)

I'm trying to update pandoc for Macports, and I'm getting a very strange error when I try to install it on my machine. Here's the Portfile and build log: https://gist.github.com/780678

Unfortunately, I know little to nothing about Haskell, so I haven't the faintest idea how to interpret the ð symbol. I just want to use pandoc. :)

Request for command-line control(s) over email obfuscation

Provide cmd line switch so that javascript email obfuscation (and or entity encoding) can be
disabled (on converting to HTML).

Google Code Info:
Issue #: 97
Author: [email protected]
Created On: 2008-10-22T21:46:35.000Z
Closed On: 2009-01-24T20:01:56.000Z

Producing output with the style Stanford Encyclopedia of Philosophy

Hi John,

The SEP has a set of requirements about the HTML formatting of entries. I am not sure how much work it would take to format HTML output from pandoc to suit this style (seems it should be minimal). Still, it would be nice to know if someone already went this route, and what's involved.

Cheers
Ehud

Add mathml math option

Use texmath to generate mathml for html.

Google Code Info:
Issue #: 187
Author: [email protected]
Created On: 2009-12-18T18:26:34.000Z
Closed On: 2010-12-06T03:48:01.000Z

pandoc fails test suite when compiled with pretty-1.0.1.0

Compile pandoc with ghc 6.10 and pretty-1.0.1.0.

Run 'cabal test'.

Watch the tests for the markdown and rst writers fail.

for example:
rst writer ---> FAILED
|NORM| 1. Item 1, graf one.
|TEST| 1.
|TEST| Item 1, graf one.

The problem arises for ordered and unordered list items that take up more
than one line.

This might be a bug in the prettyprinting library, or it might be a bug in
the way we're using it -- I'm not sure.

Google Code Info:
Issue #: 111
Author: [email protected]
Created On: 2008-12-01T05:00:51.000Z
Closed On: 2008-12-17T18:51:04.000Z

Adding new section element to HTML5 output

With a basic input file like ...
# Section Heading 1

Foo bar.

# Section Heading 1

Foo bar.

... the new HTML5 output mode exports those structures just as it does in the standard XHTML mode, with an id on the headings.

But one nice thing about HTML5 is it adds more DocBook/XHTML2-like structures. Most relevant here is section (and potentially article). So output result would, then, be:

<section id="section-heading-1">
  <h1>Section Heading 1</h1>
  <p>Foo bar.</p>
</section>
<section id="section-heading-2">
  <h1>Section Heading 2</h1>
  <p>Foo bar.</p>
</section>

--sanitize-html is over-aggressive

What steps will reproduce the problem?

% pandoc --sanitize-html
hi

What is the expected output?

hi

What do you see instead?

hi</p

Note: the problem does not occur in pandoc 0.46.

Google Code Info:
Issue #: 88
Author: [email protected]
Created On: 2008-10-06T02:20:17.000Z
Closed On: 2008-10-16T01:01:42.000Z

numbered sections in html output

I think it would be useful if pandoc could produce numbered sections in its
html output (that is, have the -N option work for html output). IMO, it
would make larger html docs (ones with multiple and nested sections) easier
to navigate.

Google Code Info:
Issue #: 150
Author: [email protected]
Created On: 2009-07-02T18:37:04.000Z
Closed On: 2009-12-08T02:36:22.000Z

ooc syntax highlighting

It would be awesome if pandoc could support syntax highlighting for ooc

Add built-in mathjax support

What steps will reproduce the problem?

1. use custom html template with
   $if(math)$
   $math$
   $endif$
2. add options below to Mathjax.js
   extensions: ["mml2jax.js"],
   jax: ["input/MathML", "output/HTML-CSS"]
3. run pandoc with --mathml option

What is the expected output? What do you see instead?

Expected output is clean mathematical equations. But mathematics displayed via mathml and mathjax does not look good compared to what is rendered via jsmath option.

What version of the product are you using? On what operating system?
pandoc 1.5.1.1. Ubuntu 10.04

Please provide any additional information below.

Google Code Info:
Issue #: 259
Author: [email protected]
Created On: 2010-09-15T10:19:25.000Z
Closed On: 2010-10-27T04:09:39.000Z

pandoc doesn't correctly handle unicode filenames

% pandoc Náó.page
pandoc: N??.page: openBinaryFile: does not exist (No such file or directory)
% ls Náó.page
Náó.page

Google Code Info:
Issue #: 252
Author: [email protected]
Created On: 2010-08-21T16:19:23.000Z
Closed On: 2010-09-11T02:57:21.000Z

problem with #id links when id contains spaces

Bug noted by Colin Adams:

Run pandoc on this input

Several moves have been tried for White, but only [P 4e -4f](#4.P 4e -
4f) works reasonably:

and later:
#4.P 4e - 4f

---

Several moves have been tried for White, but only P 4e –4f works reasonably:</p

and:

4.P 4e - 4f

Google Code Info:
Issue #: 206
Author: [email protected]
Created On: 2010-01-17T17:51:47.000Z
Closed On: 2010-01-17T18:13:44.000Z

latex table layout ends up looking bad, suggest using ordinary l,c,r column kinds

Currently the table output for LaTex uses fixed width columns via things like:

{\PBS\raggedright\hspace{0pt}}p{0.14\columnwidth}

The problem is, this ends up looking terrible when the number of columns
starts to get near to the width of the page. There is far too much space
between columns and (for reasons I do not understand) table entries for the
same row end up on multiple lines. Here's a crude rendering into ASCII of
the latex pdf output:

Col1 Col2 Col3 Col4 Col5 Col6 Col7

Col8

5 1234567 ABC DEF 17:07
01/11/08 30/03/09 18:37

To make it look ok I'm using the following change to the LaTex module, to
just use the ordinary latex tabular 'l', 'r', 'c' column types.

let colDescriptors = concatMap (\align -> case align of
AlignLeft -> "l"
AlignRight -> "r"
AlignCenter -> "c"
AlignDefault -> "r")
aligns

My suggestion is that for Pandoc's "simple tables" (ie not the multi-line
ones), pandoc should not try to compute column widths and just let LaTex do
the right thing. I appreciate that for multi-line tables, one does have to
use p{} and specify a width.

Google Code Info:
Issue #: 180
Author: [email protected]
Created On: 2009-11-12T17:55:08.000Z
Closed On: 2009-11-28T03:22:40.000Z

When I wrote the list in consecutive elements of the first end of the list wrapped in p tags.

write a markdown text as like below,

--- start ---

- a
- b
- c

- x
- y
- z

--- end ----

we get html as

<ul>
<li>a</li>
<li>b</li>
<li><p>c</p></li>
<li>x</li>
<li>b</li>
<li><p>z</p></li>
</ul>

the last element of lists are wraped in p tags.
This is a bug? or spec?

static build of pandoc?

Hi John, does your build system easily permit one to make a completely static build of pandoc? Currently I use this build invocation: http://aur.archlinux.org/packages/pandoc/pandoc/PKGBUILD (ignore the metadata, all that's important here is the build() function). And I think that does eliminate any dependencies on ghc or haskell libraries. Running ldd pandoc gives:
linux-vdso.so.1 => (0x...)
libz.so.1 => /usr/lib/libz.so.1 (0x...)
librt.so.1 => /lib/librt.so.1 (0x...)
libutil.so.1 => /lib/libutil.so.1 (0x...)
libdl.so.2 => /lib/libdl.so.2 (0x...)
libgmp.so.10 => /usr/lib/libgmp.so.10 (0x...)
libm.so.6 => /lib/libm.so.6 (0x...)
libc.so.6 => /lib/libc.so.6 (0x...)
libpthread.so.0 => /lib/libpthread.so.0 (0x...)
/lib/ld-linux-x86-64.so.2 (0x...)

But I need to build pandoc on my linux system (which has ghc and all the necessary libs) and deploy it on an unattended mac server, where it's too much work to get the necessary build chain set up and keep it maintained. If it's not too hard to make a fully static build of pandoc, that might be the easiest solution.

reST comment block

http://www.mail-archive.com/[email protected]/msg571970.html

Debian Bug#500662 submitted by Ben Finney
Package: pandoc
Version: 0.46+2
Severity: normal

The reStructuredText specification allows for comment blocks of
arbitrary indented text
URL:http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#comments.

The following session shows that pandoc is incorrectly interpreting
these comment elements as some other kind of element.

Script started on Tue 30 Sep 2008 18:03:08 EST

$ infile=$(mktemp -t)
$ cat > $infile

Title of document

First paragraph

..
Comment block, should not appear in output
as defined by reStructuredText

Another paragraph

..
Another comment block.

This one spans several
text elements.

It doesn't end until
indentation is restored to the
preceding level.

A third paragraph

$ pandoc --from rst --to markdown $infile

Title of document

First paragraph

..
: Comment block, should not appear in output as defined by
reStructuredText

Another paragraph

..

Another comment block.

This one spans several text elements.

It doesn't end until indentation is restored to the preceding
level.

A third paragraph

$ rm $infile
$ exit

Script done on Tue 30 Sep 2008 18:07:49 EST

The above result is incorrect; instead the comment blocks in the input
should not be visible in the rendered form. For example, this would be
a correct rendering of the above example input:

Title of document

First paragraph

Another paragraph

A third paragraph

Google Code Info:
Issue #: 86
Author: [email protected]
Created On: 2008-10-01T04:26:42.000Z
Closed On: 2008-11-06T22:10:44.000Z

Strip off BOM if present

Check for a byte order mark at the beginning of the document and remove it.
System.IO.UTF8 doesn't strip this out, apparently.
It messes up title blocks if present.

Google Code Info:
Issue #: 131
Author: [email protected]
Created On: 2009-03-03T19:54:47.000Z
Closed On: 2009-05-02T02:40:30.000Z

Markdown reader interprets "A." in "A.B." as ordered list start

What steps will reproduce the problem?

pandoc
A.B.
^D

What is the expected output?

A.B.</p

What do you see instead?

pandoc:
Error:
"source" (line 7, column 3):
unexpected "B"

This is due to the fact that anyOrderedListStart doesn't require a
space after the marker.

Google Code Info:
Issue #: 22
Author: [email protected]
Created On: 2007-08-18T15:14:05.000Z
Closed On: 2007-08-18T15:26:57.000Z

Markdown image markup results in extra caption DIV in HTML output

Converting the following Markdown snippet

![Foo](some-image.png)

to HTML results in an extra paragraph element containing "Foo" being inserted below the image. I would except the above to only cause the alt attribute to be set.

Plugin system

Users should be able to write their own plugins that transform a pandoc
document between reader and writer. These transformations are now made
easy to write by the 'processPandoc' function. The plugin mechanism can be
provided by the plugins library.

Usage examples:

• modifying inline math to work with Wordpress blog ($2+2$ -> $latex 2+2$)
• using delimited code blocks for purposes other than code (e.g. lilypond
  notation, to be converted to an image)
• generating source code snippets programatically (see Issue #90)
• automatically turning CamelCase words into wikilinks

The plugins themselves would be short Haskell programs (which could
themselves call other external programs). It would be included via a
command-line option:
--plugins=FirstPlugin.hs,SecondPlugin.hs

Steps:
_ provide a plugin API, Pandoc.Interface
_ in Main.hs, apply plugin transformations between reader and writer
_ add a "How to Write a Plugin" tutorial
_ possibly add more functions like 'processPandoc' to simplify the writing
of plugins?

Google Code Info:
Issue #: 102
Author: [email protected]
Created On: 2008-11-06T22:22:57.000Z
Closed On: 2009-01-24T20:01:26.000Z

Doesn't properly interpret Textile cell attributes

The Textile table below handled incorrectly in several ways.

| |_\2. colspan |_. header |
|_/2. rowspan | cell 2 | cell 3 | cell 4   |
| cell 2 | cell 3 | cell 4   |
{background:#ddd}. |_/2. rowspan | cell 2 | cell 3 | cell 4   |
{background:#ddd}. | cell 2 | cell 3 | cell 4   |
|_/2. rowspan | cell 2 | cell 3 | cell 4   |
| cell 2 | cell 3 | cell 4   |

E. coli starts a list

According to the User's Guide, an ordered list item starting with a capital
letter and period needs two spaces after a capital letter. The point is to
prevent, say, a paragraph beginning with "E. coli" from starting a list.

This seems no longer to be working.

E.coli now starts a list

Thanks to shamberg for reporting (via gitit).

Google Code Info:
Issue #: 212
Author: [email protected]
Created On: 2010-01-29T20:17:53.000Z
Closed On: 2010-02-03T05:48:55.000Z

pandoc installation on ubuntu completely missing s5 folder - /s5/default/s5-core.css: openFile: does not exist

Hi,

Sorry if there are any details needed here; I'm not a technical guy . Im not sure if this is a packaging issue either or a pandoc one

I installed pandoc successfully on a Ubuntu 64bit, lucid, freshly updated.

When trying to run pandoc like this:
pandoc -w s5 -s in.markdown -o out.html

I get:
pandoc: /usr/share/pandoc-1.5.1.1/s5/default/s5-core.css: openFile: does not exist (No such file or directory)

I did check my pandoc installation and apparently there's nothing related to s5 getting installed

ls -lR /usr/share/pandoc-1.5.1.1/

/usr/share/pandoc-1.5.1.1/:
total 16
-rw-r--r-- 1 root root 9572 2010-04-23 01:30 reference.odt
total 16
/usr/share/pandoc-1.5.1.1/templates:
total 48
-rw-r--r-- 1 root root 1822 2010-04-23 01:30 context.template
-rw-r--r-- 1 root root 520 2010-04-23 01:30 docbook.template
-rw-r--r-- 1 root root 2037 2010-04-23 01:30 html.template
-rw-r--r-- 1 root root 1929 2010-04-23 01:30 latex.template
-rw-r--r-- 1 root root 297 2010-04-23 01:30 man.template
-rw-r--r-- 1 root root 263 2010-04-23 01:30 markdown.template
-rw-r--r-- 1 root root 174 2010-04-23 01:30 mediawiki.template
-rw-r--r-- 1 root root 1874 2010-04-23 01:30 opendocument.template
-rw-r--r-- 1 root root 257 2010-04-23 01:30 plain.template
-rw-r--r-- 1 root root 404 2010-04-23 01:30 rst.template
-rw-r--r-- 1 root root 613 2010-04-23 01:30 rtf.template
-rw-r--r-- 1 root root 814 2010-04-23 01:30 texinfo.template

Unexpected warning using references with a chapter field

When a BibTeX reference has a chapter field, hs-bibutils yields an unexpected warning:

-- test.text
Test [@item].

-- test.bib
@InCollection{item,
author = {Someone},
title = {An chapter title},
booktitle = {An book title},
publisher = {An publisher},
year = 2011,
chapter = 1
}

-- Command line and unexpected warning
$ pandoc -s --bibliography=test.bib test.text -o test.html
hs-bibutils: Ref 1 unused tag: 'TITLE' value: '1' level: 0

-- versions
pandoc: development version
citeproc-hs: development version
hs-bibutils: 4.12

Get rid of template haskell use

Template Haskell can't be used on "stage 1 compilers," and as a result
pandoc can't compile on some debian architectures. This will keep pandoc
from ever entering testing, since 0.46 did compile on those architectures.

Get rid of the use of template Haskell either (a) by using data files or
(b) by creating DefaultHeaders.hs, etc. from templates.

Google Code Info:
Issue #: 186
Author: [email protected]
Created On: 2009-12-15T18:36:55.000Z
Closed On: 2009-12-31T01:33:12.000Z

Including 'amssymb' in the LaTeX template

I'm running an instance of gitit and want to use the mathematical set symbols.
I haven't figured out yet what it needs to use them with MathML, but this is not as important since the unknown seqence '\mathbb{N}' just reduces to a plain 'N'. Exporting such a document as LaTeX or even PDF causes problems due to the missing package 'amssymb'.

I tried just adding '\usepackage{amssymb}' in the pandoc LaTeX template and it works fine for me. So I'm wondering whether there are any objections against doing this addition to pandoc in general.

Markdown link references allow line break before the URL.

Sample input:

a

Markdown.pl makes this a link to yahoo.com; pandoc treats it as an empty link.

Google Code Info:
Issue #: 81
Author: [email protected]
Created On: 2008-08-02T17:53:23.000Z
Closed On: 2008-08-10T23:26:48.000Z

pandoc install via cabal fails

When trying to install pandoc via Haskell's cabal, installation fails badly.
(Using fresh install of Haskell Platform installed via brew install haskell-platform)

cabal update

cabal install pandoc

Resolving dependencies...
Downloading binary-0.5.0.2...
Configuring binary-0.5.0.2...
Preprocessing library binary-0.5.0.2...
Building binary-0.5.0.2...
[1 of 4] Compiling Data.Binary.Builder ( src/Data/Binary/Builder.hs, dist/build/Data/Binary/Builder.o )

src/Data/Binary/Builder.hs:1:0:
Warning: Module Prelude' is deprecated: You are using the old packagebase' version 3.x.
Future GHC versions will not support base version 3.x. You
should update your code to use the new base version 4.x.

src/Data/Binary/Builder.hs:60:0:
Warning: The import of Data.Word' is redundant except perhaps to import instances fromData.Word'
To import instances alone, use: import Data.Word()

src/Data/Binary/Builder.hs:70:0:
Warning: The import of Data.ByteString.Lazy.Internal' is redundant except perhaps to import instances fromData.ByteString.Lazy.Internal'
To import instances alone, use: import Data.ByteString.Lazy.Internal()
[2 of 4] Compiling Data.Binary.Get ( src/Data/Binary/Get.hs, dist/build/Data/Binary/Get.o )

src/Data/Binary/Get.hs:1:0:
Warning: Module Prelude' is deprecated: You are using the old packagebase' version 3.x.
Future GHC versions will not support base version 3.x. You
should update your code to use the new base version 4.x.

src/Data/Binary/Get.hs:99:0:
Warning: The import of GHC.Int' is redundant except perhaps to import instances fromGHC.Int'
To import instances alone, use: import GHC.Int()
[3 of 4] Compiling Data.Binary.Put ( src/Data/Binary/Put.hs, dist/build/Data/Binary/Put.o )

src/Data/Binary/Put.hs:1:0:
Warning: Module Prelude' is deprecated: You are using the old packagebase' version 3.x.
Future GHC versions will not support base version 3.x. You
should update your code to use the new base version 4.x.
[4 of 4] Compiling Data.Binary ( src/Data/Binary.hs, dist/build/Data/Binary.o )

src/Data/Binary.hs:1:0:
Warning: Module Prelude' is deprecated: You are using the old packagebase' version 3.x.
Future GHC versions will not support base version 3.x. You
should update your code to use the new base version 4.x.

src/Data/Binary.hs:66:0:
Warning: The import of System.IO' is redundant except perhaps to import instances fromSystem.IO'
To import instances alone, use: import System.IO()
Registering binary-0.5.0.2...
Installing library in /Users/d2s/.cabal/lib/binary-0.5.0.2/ghc-6.12.3
Registering binary-0.5.0.2...
Downloading digest-0.0.0.9...
Configuring digest-0.0.0.9...
Preprocessing library digest-0.0.0.9...
Building digest-0.0.0.9...
[1 of 2] Compiling Data.Digest.Adler32 ( dist/build/Data/Digest/Adler32.hs, dist/build/Data/Digest/Adler32.o )
[2 of 2] Compiling Data.Digest.CRC32 ( dist/build/Data/Digest/CRC32.hs, dist/build/Data/Digest/CRC32.o )
Registering digest-0.0.0.9...
Installing library in /Users/d2s/.cabal/lib/digest-0.0.0.9/ghc-6.12.3
Registering digest-0.0.0.9...
Downloading utf8-string-0.3.6...
Configuring utf8-string-0.3.6...
Preprocessing library utf8-string-0.3.6...
Building utf8-string-0.3.6...
[1 of 7] Compiling Codec.Binary.UTF8.String ( Codec/Binary/UTF8/String.hs, dist/build/Codec/Binary/UTF8/String.o )

Codec/Binary/UTF8/String.hs:1:0:
Warning: Module Prelude' is deprecated: You are using the old packagebase' version 3.x.
Future GHC versions will not support base version 3.x. You
should update your code to use the new base version 4.x.
[2 of 7] Compiling Codec.Binary.UTF8.Generic ( Codec/Binary/UTF8/Generic.hs, dist/build/Codec/Binary/UTF8/Generic.o )

Codec/Binary/UTF8/Generic.hs:37:0:
Warning: Module Prelude' is deprecated: You are using the old packagebase' version 3.x.
Future GHC versions will not support base version 3.x. You
should update your code to use the new base version 4.x.
[3 of 7] Compiling Data.String.UTF8 ( Data/String/UTF8.hs, dist/build/Data/String/UTF8.o )

Data/String/UTF8.hs:43:0:
Warning: Module Prelude' is deprecated: You are using the old packagebase' version 3.x.
Future GHC versions will not support base version 3.x. You
should update your code to use the new base version 4.x.
[4 of 7] Compiling System.IO.UTF8 ( System/IO/UTF8.hs, dist/build/System/IO/UTF8.o )

System/IO/UTF8.hs:35:0:
Warning: Module Prelude' is deprecated: You are using the old packagebase' version 3.x.
Future GHC versions will not support base version 3.x. You
should update your code to use the new base version 4.x.

System/IO/UTF8.hs:39:26:
Warning: In the use of `bracket'
(imported from Control.Exception, but defined in base:Control.OldException):
Deprecated: "Future versions of base will not support the old exceptions style. Please switch to extensible exceptions."
[5 of 7] Compiling System.Environment.UTF8 ( System/Environment/UTF8.hs, dist/build/System/Environment/UTF8.o )

System/Environment/UTF8.hs:1:0:
Warning: Module Prelude' is deprecated: You are using the old packagebase' version 3.x.
Future GHC versions will not support base version 3.x. You
should update your code to use the new base version 4.x.
[6 of 7] Compiling Data.ByteString.UTF8 ( Data/ByteString/UTF8.hs, dist/build/Data/ByteString/UTF8.o )

Data/ByteString/UTF8.hs:37:0:
Warning: Module Prelude' is deprecated: You are using the old packagebase' version 3.x.
Future GHC versions will not support base version 3.x. You
should update your code to use the new base version 4.x.
[7 of 7] Compiling Data.ByteString.Lazy.UTF8 ( Data/ByteString/Lazy/UTF8.hs, dist/build/Data/ByteString/Lazy/UTF8.o )

Data/ByteString/Lazy/UTF8.hs:38:0:
Warning: Module Prelude' is deprecated: You are using the old packagebase' version 3.x.
Future GHC versions will not support base version 3.x. You
should update your code to use the new base version 4.x.
Registering utf8-string-0.3.6...
Installing library in /Users/d2s/.cabal/lib/utf8-string-0.3.6/ghc-6.12.3
Registering utf8-string-0.3.6...
Downloading xml-1.3.7...
Configuring xml-1.3.7...
Preprocessing library xml-1.3.7...
Building xml-1.3.7...
[1 of 7] Compiling Text.XML.Light.Types ( Text/XML/Light/Types.hs, dist/build/Text/XML/Light/Types.o )
[2 of 7] Compiling Text.XML.Light.Proc ( Text/XML/Light/Proc.hs, dist/build/Text/XML/Light/Proc.o )
[3 of 7] Compiling Text.XML.Light.Output ( Text/XML/Light/Output.hs, dist/build/Text/XML/Light/Output.o )
[4 of 7] Compiling Text.XML.Light.Lexer ( Text/XML/Light/Lexer.hs, dist/build/Text/XML/Light/Lexer.o )

Text/XML/Light/Lexer.hs:7:0:
Warning: The import of ord' from moduleData.Char' is redundant
[5 of 7] Compiling Text.XML.Light.Input ( Text/XML/Light/Input.hs, dist/build/Text/XML/Light/Input.o )
[6 of 7] Compiling Text.XML.Light.Cursor ( Text/XML/Light/Cursor.hs, dist/build/Text/XML/Light/Cursor.o )
[7 of 7] Compiling Text.XML.Light ( Text/XML/Light.hs, dist/build/Text/XML/Light.o )
Registering xml-1.3.7...
Installing library in /Users/d2s/.cabal/lib/xml-1.3.7/ghc-6.12.3
Registering xml-1.3.7...
Downloading texmath-0.5...
[1 of 1] Compiling Main ( /var/folders/E5/E5GdjIotHKKA+D2JnZBot++++TI/-Tmp-/texmath-0.517467/texmath-0.5/Setup.hs, /var/folders/E5/E5GdjIotHKKA+D2JnZBot++++TI/-Tmp-/texmath-0.517467/texmath-0.5/dist/setup/Main.o )
Linking /var/folders/E5/E5GdjIotHKKA+D2JnZBot++++TI/-Tmp-/texmath-0.517467/texmath-0.5/dist/setup/setup ...
Configuring texmath-0.5...
Preprocessing library texmath-0.5...
Preprocessing executables for texmath-0.5...
Building texmath-0.5...
[1 of 5] Compiling Text.TeXMath.Macros ( Text/TeXMath/Macros.hs, dist/build/Text/TeXMath/Macros.o )
[2 of 5] Compiling Text.TeXMath.Types ( Text/TeXMath/Types.hs, dist/build/Text/TeXMath/Types.o )
[3 of 5] Compiling Text.TeXMath.MathML ( Text/TeXMath/MathML.hs, dist/build/Text/TeXMath/MathML.o )
[4 of 5] Compiling Text.TeXMath.Parser ( Text/TeXMath/Parser.hs, dist/build/Text/TeXMath/Parser.o )
[5 of 5] Compiling Text.TeXMath ( Text/TeXMath.hs, dist/build/Text/TeXMath.o )
Registering texmath-0.5...
Installing library in /Users/d2s/.cabal/lib/texmath-0.5/ghc-6.12.3
Registering texmath-0.5...
Downloading zip-archive-0.1.1.6...
Configuring zip-archive-0.1.1.6...
Preprocessing library zip-archive-0.1.1.6...
Preprocessing executables for zip-archive-0.1.1.6...
Building zip-archive-0.1.1.6...
[1 of 1] Compiling Codec.Archive.Zip ( Codec/Archive/Zip.hs, dist/build/Codec/Archive/Zip.o )
Registering zip-archive-0.1.1.6...
Installing library in /Users/d2s/.cabal/lib/zip-archive-0.1.1.6/ghc-6.12.3
Registering zip-archive-0.1.1.6...
Downloading pandoc-1.6...
[1 of 1] Compiling Main ( /var/folders/E5/E5GdjIotHKKA+D2JnZBot++++TI/-Tmp-/pandoc-1.617467/pandoc-1.6/Setup.hs, /var/folders/E5/E5GdjIotHKKA+D2JnZBot++++TI/-Tmp-/pandoc-1.617467/pandoc-1.6/dist/setup/Main.o )
Linking /var/folders/E5/E5GdjIotHKKA+D2JnZBot++++TI/-Tmp-/pandoc-1.617467/pandoc-1.6/dist/setup/setup ...
Configuring pandoc-1.6...
Preprocessing library pandoc-1.6...
Preprocessing executables for pandoc-1.6...
Building pandoc-1.6...
[ 1 of 32] Compiling Text.Pandoc.UUID ( src/Text/Pandoc/UUID.hs, dist/build/Text/Pandoc/UUID.o )
[ 2 of 32] Compiling Text.Pandoc.XML ( src/Text/Pandoc/XML.hs, dist/build/Text/Pandoc/XML.o )
[ 3 of 32] Compiling Text.Pandoc.UTF8 ( src/Text/Pandoc/UTF8.hs, dist/build/Text/Pandoc/UTF8.o )
[ 4 of 32] Compiling Text.Pandoc.CharacterReferences ( src/Text/Pandoc/CharacterReferences.hs, dist/build/Text/Pandoc/CharacterReferences.o )
[ 5 of 32] Compiling Text.Pandoc.Blocks ( src/Text/Pandoc/Blocks.hs, dist/build/Text/Pandoc/Blocks.o )
[ 6 of 32] Compiling Paths_pandoc ( dist/build/autogen/Paths_pandoc.hs, dist/build/Paths_pandoc.o )
[ 7 of 32] Compiling Text.Pandoc.Definition ( src/Text/Pandoc/Definition.hs, dist/build/Text/Pandoc/Definition.o )
[ 8 of 32] Compiling Text.Pandoc.Shared ( src/Text/Pandoc/Shared.hs, dist/build/Text/Pandoc/Shared.o )
[ 9 of 32] Compiling Text.Pandoc.Templates ( src/Text/Pandoc/Templates.hs, dist/build/Text/Pandoc/Templates.o )
[10 of 32] Compiling Text.Pandoc.Writers.Native ( src/Text/Pandoc/Writers/Native.hs, dist/build/Text/Pandoc/Writers/Native.o )
[11 of 32] Compiling Text.Pandoc.Writers.RST ( src/Text/Pandoc/Writers/RST.hs, dist/build/Text/Pandoc/Writers/RST.o )
[12 of 32] Compiling Text.Pandoc.Writers.LaTeX ( src/Text/Pandoc/Writers/LaTeX.hs, dist/build/Text/Pandoc/Writers/LaTeX.o )
[13 of 32] Compiling Text.Pandoc.Writers.ConTeXt ( src/Text/Pandoc/Writers/ConTeXt.hs, dist/build/Text/Pandoc/Writers/ConTeXt.o )
[14 of 32] Compiling Text.Pandoc.Writers.MediaWiki ( src/Text/Pandoc/Writers/MediaWiki.hs, dist/build/Text/Pandoc/Writers/MediaWiki.o )
[15 of 32] Compiling Text.Pandoc.Parsing ( src/Text/Pandoc/Parsing.hs, dist/build/Text/Pandoc/Parsing.o )
[16 of 32] Compiling Text.Pandoc.Readers.RST ( src/Text/Pandoc/Readers/RST.hs, dist/build/Text/Pandoc/Readers/RST.o )
[17 of 32] Compiling Text.Pandoc.Readers.LaTeX ( src/Text/Pandoc/Readers/LaTeX.hs, dist/build/Text/Pandoc/Readers/LaTeX.o )
[18 of 32] Compiling Text.Pandoc.Readers.HTML ( src/Text/Pandoc/Readers/HTML.hs, dist/build/Text/Pandoc/Readers/HTML.o )
[19 of 32] Compiling Text.Pandoc.Readers.Markdown ( src/Text/Pandoc/Readers/Markdown.hs, dist/build/Text/Pandoc/Readers/Markdown.o )
[20 of 32] Compiling Text.Pandoc.Writers.Markdown ( src/Text/Pandoc/Writers/Markdown.hs, dist/build/Text/Pandoc/Writers/Markdown.o )
[21 of 32] Compiling Text.Pandoc.S5 ( src/Text/Pandoc/S5.hs, dist/build/Text/Pandoc/S5.o )
[22 of 32] Compiling Text.Pandoc.Highlighting ( src/Text/Pandoc/Highlighting.hs, dist/build/Text/Pandoc/Highlighting.o )
[23 of 32] Compiling Text.Pandoc.Readers.TeXMath ( src/Text/Pandoc/Readers/TeXMath.hs, dist/build/Text/Pandoc/Readers/TeXMath.o )

src/Text/Pandoc/Readers/TeXMath.hs:50:30: Not in scope: `formula'

src/Text/Pandoc/Readers/TeXMath.hs:54:18:
Not in scope: type constructor or class `Exp'

src/Text/Pandoc/Readers/TeXMath.hs:59:16:
Not in scope: type constructor or class `Exp'

src/Text/Pandoc/Readers/TeXMath.hs:60:14:
Not in scope: data constructor `ENumber'

src/Text/Pandoc/Readers/TeXMath.hs:61:14:
Not in scope: data constructor `EIdentifier'

src/Text/Pandoc/Readers/TeXMath.hs:62:14:
Not in scope: data constructor `EMathOperator'

src/Text/Pandoc/Readers/TeXMath.hs:63:14:
Not in scope: data constructor `ESymbol'

src/Text/Pandoc/Readers/TeXMath.hs:64:17:
Not in scope: data constructor `Op'

src/Text/Pandoc/Readers/TeXMath.hs:65:17:
Not in scope: data constructor `Bin'

src/Text/Pandoc/Readers/TeXMath.hs:66:17:
Not in scope: data constructor `Rel'

src/Text/Pandoc/Readers/TeXMath.hs:67:17:
Not in scope: data constructor `Pun'

src/Text/Pandoc/Readers/TeXMath.hs:72:14:
Not in scope: data constructor `EStretchy'

src/Text/Pandoc/Readers/TeXMath.hs:73:14:
Not in scope: data constructor `EGrouped'

src/Text/Pandoc/Readers/TeXMath.hs:74:14:
Not in scope: data constructor `ESpace'

src/Text/Pandoc/Readers/TeXMath.hs:75:14:
Not in scope: data constructor `EBinary'

src/Text/Pandoc/Readers/TeXMath.hs:76:14:
Not in scope: data constructor `ESub'

src/Text/Pandoc/Readers/TeXMath.hs:80:14:
Not in scope: data constructor `ESuper'

src/Text/Pandoc/Readers/TeXMath.hs:84:14:
Not in scope: data constructor `ESubsup'

src/Text/Pandoc/Readers/TeXMath.hs:89:14:
Not in scope: data constructor `EDown'

src/Text/Pandoc/Readers/TeXMath.hs:89:41:
Not in scope: data constructor `ESub'

src/Text/Pandoc/Readers/TeXMath.hs:90:14:
Not in scope: data constructor `EUp'

src/Text/Pandoc/Readers/TeXMath.hs:90:39:
Not in scope: data constructor `ESuper'

src/Text/Pandoc/Readers/TeXMath.hs:91:14:
Not in scope: data constructor `EDownup'

src/Text/Pandoc/Readers/TeXMath.hs:91:45:
Not in scope: data constructor `ESubsup'

src/Text/Pandoc/Readers/TeXMath.hs:92:14:
Not in scope: data constructor `EText'
cabal: Error: some packages failed to install:
pandoc-1.6 failed during the building phase. The exception was:
ExitFailure 1

[html writer] write footnote tags in better order

atm, the HTML writer will write footnotes as ^label

This means that the label text is raised, but the link's text-decoration
(eg. underline) still applies to the unraised position, which looks quite
weird.

You can fix this by adding some CSS, eg:

/* workaround pandoc bad generation of footnote html */
a.footnoteRef { text-decoration: none; }
a.footnoteRef > sup { text-decoration: underline; }

but it's quite ugly.

If the tags are swapped around to ^{label text}, this will
fix the problem.

Google Code Info:
Issue #: 191
Author: infinity0x
Created On: 2009-12-27T01:34:09.000Z
Closed On: 2009-12-31T01:47:08.000Z

Towards Syntax Highlighting in LaTeX

I have made delightingly few changes to the Text.Pandoc.Writers.LaTeX
to employ the listings package instead of verbatim for code and code
blocks.
Thus, the block

~~~ {.haskell }
f x = x
~~~

is now translated to


\begin{lstlisting}[language=haskell]
f x = x
\end{lstlisting}

And `f 23 = 23`  becomes

\lstinline[]!f 23 = 23!

Likewise for one-language documents you can have a default language by
adding, e.g.,  \lstset{language=haskell} to your header file and then
simply write

~~~
f x = x
~~~


John MacFarlane said that there should be an option to switch between this
and verbatim mode, but I did not come round to add that also.

Google Code Info:
Issue #: 110
Author: [email protected]
Created On: 2008-11-19T15:49:19.000Z
Closed On: 

Cannot omit libraries from install

Trying to update the Arch "pandoc" package, which installs only the pandoc binaries and manpages, without Haskell libs.

Have all Haskell build dependencies, using ghc 6.12.1, trying to build pandoc 1.5.1.1.

This works:
runhaskell Setup configure --prefix=/usr --docdir=/usr/share/doc/pandoc
runhaskell Setup build
runhaskell Setup copy destdir=$pkgdir # supplying Arch's packaging chroot

But then all the libraries get installed. Former versions of this package added the "-f-library" option to the Setup line. However then the build fails with:

src/pandoc.hs:50:0
    error: missing binary operator before token "("

Hence this report.

Please advise what's the proper instructions to build from source (i.e. without cabal) if one wants to install only the executables not the libraries.

Worst case, I can have the build script install everything to the chroot and then delete the libraries before compressing the package. But I'm guessing those aren't the "proper instructions."

problem with HTML before header

% pandoc

Header

^D
<p

Header</p

The Header should be an

. Looks like the HTML inline parser is
gobbling space where it shouldn't. Note that if you put a letter before
the HTML, it works properly: x.

Google Code Info:
Issue #: 124
Author: [email protected]
Created On: 2009-01-30T00:01:53.000Z
Closed On: 2009-01-31T18:31:16.000Z

MoinMoin format support

Purpose: To convert Google Code wiki pages to any format supported by Github

Problem: Missing MoinMoin wiki parser.

Workaround: To render a MoinMoin wiki page into rst via moin2rst (can be used by GitHub, or further converted to any other pandoc supported output format)

• http://moinmo.in/HelpOnMoinWikiSyntax
• http://moinmo.in/FormatterMarket
• http://www.merten-home.de/FreeSoftware/moin2rst/
• http://code.google.com/p/support/wiki/WikiFAQ
• http://code.google.com/p/support/wiki/WikiSyntax

Change types for metadata

author(s) should be [[Inline]]
date should be [Inline]

We might as well make this change while moving to the template-based system.

Google Code Info:
Issue #: 188
Author: [email protected]
Created On: 2009-12-22T01:33:50.000Z
Closed On: 2009-12-31T01:32:06.000Z