- Specialize readWith to String input.
- On error have it print the line in which the error occurred,
with a caret pointing to the column.
- This should help diagnose parsing problems in LaTeX especially.
This articulates strings into Str, Space, allowing them to be
hard-wrapped intelligently by the writers.
This patch also fixes a bug with trailing spaces and newlines.
(See #806.)
if other table options are disabled.
This means you can do
pandoc -t markdown-pipe_tables-simple_tables-multiline_tables
and all tables will render as grid tables.
before treating as a filename. This fixes `--self-contained`
when used with CSS files that include web fonts using the
method described here:
http://paulirish.com/2009/bulletproof-font-face-implementation-syntax/
Examples from reveal.js themes:
"../../lib/font/league_gothic-webfont.eot?#iefix"
"../../lib/font/league_gothic-webfont.svg#LeagueGothicRegular"
Closes#739.
Support unordered and ordered lists with "fragment" elements.
Modified by JGM to remove the --reveal_js-url command-line option.
Instead use -V reveal_js-url=... as with slidy and the other slide
formats. Also cleaned up the list code in the HTML writer.
The _note attribute is supported. This is unofficial, but
used e.g. in OmniOutliner and supported by multimarkdown.
We treat the contents as markdown blocks under a section
header.
Added to documentation and tests.
In 1.11 and 1.11.1, display math in lists rendered as a new list
item. Now it always appears centered, just as outside of lists,
and in proper display math style, no matter how far indented the
containing list item is.
Closes#784.
* Reverts 1.11 change that caused citations to be rendered as
markdown citations, even if `--biblio` was specified, unless
`citation` extension is disabled. Now, formatted citations
are always printed if `--biblio` was specified. If you want to
reformat markdown keeping pandoc markdown citations intact,
just don't specify `--biblio`.
* Reverted now unnecessary changes to Text.Pandoc.Biblio adding the raw
block to mark the bibliography, and to Text.Pandoc.Writers.Markdown
to remove the bibliography if `citations` not specified.
* If the content of a `Cite` inline is a `RawInline "latex"`, which
means that a LaTeX citation command was parsed and `--biblio` wasn't
specified, then render it as a pandoc markdown citation. This means
that `pandoc -f latex -t markdown`, without `--biblio`, will convert
LaTeX citation commands to pandoc markdown citations.
In 1.11, citations would be rendered as pandoc markdown citations,
but the bibliography would still be printed.
We avoid that by adding a `RawBlock "pandoc" "references"` before
the references. This allows the markdown writer to find the references
and strip them off when `citations` is enabled.
They do not generate a Quoted element; instead, the double quote
is just turned into a Str with a curly left quote.
This should satisfy the fiction writers. Closes#99 (again).
Previously, a LaTeX citation would always be parsed as a Citation
element, with the raw LaTeX in the [Inline] part.
Now, the LaTeX citation is parsed as a Citation element only if
`--biblio` was specified (i.e. only if there is a nonempty set
of references in readerReferences). Otherwise it is parsed as
raw LaTeX.
This will make it possible to simplify some things in the markdown
writer. It also makes the LaTeX reader behave more like the Markdown
reader.
Previously citations were rendered as citeproc-formatted citations
by default. Now we render them as pandoc citations, e.g. `[@item1]`,
unless the `citations` extension is disabled.
If you still want formatted citations in your markdown output,
use `pandoc -t markdown-citations`.
* Moved code for translating listings language names to
highlighting-kate names and back from LaTeX reader to Highlighting.
* Text.Pandoc.Highlighting no longer exposed (API change)
* Text.Pandoc.Highlighting exports toListingsLang, fromListingsLang
We convert these to pandoc standard names, e.g. "numberLines"
for "numbers=left", "startFrom=100" from "firstnumber=100".
Still need to add code to convert the language names.
* The TOC is included in `<spine>`, but `linear` is set
to `no` unless the `--toc` option is specified.
* Include `<guide>` element in OPF.
* This should allow the TOC to be useable in Kindles when
converted with kindlegen.
* Results validate with epubcheck 3.0 for both epub and epub3
output.
* Closes#773.
* Cleaned up parsing code.
* '-' in an attribute context = '.unnumbered'. The point of this
is to provide a way to specify unnumbered headers in non-English
documents.
Display math inside a paragraph is now put in a separate
paragraph, so it will render properly (centered and without
extra blank lines around it).
Partially addresses #742.
FootnoteReference -> FootnoteRef.
Hyperlink -> Link.
Why? Because the old names got changed by Word when the
reference.docx was edited. I don't understand why, but this
fixes things.
Closes#414.
This fixes problems that arise when you edit the reference.docx
with Word. Word tends to remove things from the `[Content_Types].xml`
and `word/_rels/document.xml.rels` files that are needed (e.g.
references to the `footnotes.xml` file and image default mime types).
So we regenerate these completely rather than taking them from
the `reference.docx`.
We also now encode mime types for each individual image rather
than using defaults. This should allow us to handle a wider
range of image types.
This mostly addresses #414. The only remaining issue I can see
is the issue of style IDs, which Word inexplicably changes in
some cases when the reference.docx is saved. E.g.
`FootnoteReference` becomes `FootnoteReference1`.
* Headers with "unnumbered" attribute are not numbered.
(Nor do they cause an increment in running numbering.)
* Section numbers now work properly, even when there is
material before the first numbered section.
Also `writerNumberFrom` -> `writeNumberOffset`.
The offset is a list of numbers (0 by default).
These are added to the section, subsection, etc.
numbers that would have been generated automatically.
Previously the numbering restarted from 1 in each chapter
(with `--number-sections`), though the numbers in the table
of contents were correct.
Note that this fix is a bit hackish and possibly fragile:
if the rendering of section numbers in HTML changes in the
future, it may break. But it works, without needing
changes in other modules.
Note: The attributes go on the enclosing section or div
if `--section-divs` is specified.
Also fixed a regression (only now noticed) in html+lhs output.
Previously the bird tracks were being omitted.
Unnumbered sections get [] for their section number.
So far only the HTML writer has been adjusted to be sensitive
to this.
If we keep this change, all the writers will need to be changed
either (a) to directly check for the "unnumbered" class, if they
do section numbering themselves, or (b) to check for a null section
number, if they use hierarchicalize.
