| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Copied, mostly, from stack's repo.
|
|
(LaTeX, ConTeXt, HTML)
|
|
Support bidirectional text output with XeLaTeX, ConTeXt and HTML
|
|
|
|
Give details of locator terms
|
|
closes #2191
|
|
|
|
|
|
Closes #2395.
|
|
# Header {id="myid" class="foo bar"}
is now equivalent to
# Header {#myid .foo .bar}
Closes #2396.
|
|
Instead of directly using `lang`, we now use `babel-lang` and
`polyglossia-lang` and `context-lang`. These variables are set by
the writers to the necessary values, based on the `lang` variable
(which now always takes a value in BCP47 format).
|
|
docbook-xsl, a set of XSLT scripts to generate HMTL out of DocBook,
tries harder to generate a nice xref text. Depending on the element
being linked to, it looks at the title or other descriptive child
elements. Let's do that, too.
|
|
'xref' is used to create cross references to other parts of the
document. It is an empty element - the cross reference text depends on
various attributes. Quoting 'DocBook: The Definitive Guide':
1. If the endterm attribute is specified on xref, the content of the
element pointed to by endterm will be used as the text of the
cross-reference.
2. Otherwise, if the object pointed to has a specified XRefLabel, the
content of that attribute will be used as the cross-reference text.
|
|
|
|
Having access to the entire document will be needed when handling
elements which refer to other elements. This is needed for e.g. <xref>
or <link>, both of which reference other elements (by the 'id'
attribute) for the label text.
I suppose that in practice, the [Content] returned by parseXML always
only contains one 'Elem' value -- the document element. However, I'm not
totally sure about it, so let's just pass all the Content along.
|
|
I plan to use the parsed and normalized XML tree read in readDocBook in
other places - prepare that commit by factoring this code out into a
separate, shared, definition.
|
|
Closes #2411.
|
|
`lang` variable is now in BCP47 format
|
|
|
|
Make sure verse blocks can contain empty lines
|
|
[RST Writer] Don't normalize heading levels below input minimum
|
|
The previous verse parsing code made the faulty assumption that empty
strings are valid (and empty) inlines. This isn't the case, so lines
are changed to contain at least a newline.
It would generally be nicer and faster to keep the newlines while
splitting the string. However, this would require more code, which
seems unjustified for a simple (and fairly rare) block as *verse*.
This fixes #2402.
|
|
|
|
Closes #829.
|
|
Cloess #2393.
|
|
This allows tests to be run without installing first.
|
|
This allows the test suite to work without installing pandoc first.
It also brings the docx writer in line with the odt writer.
|
|
|
|
Closes #2372.
@cinaeco as the pandoc-citeproc man page describes, the current
behavior if no style is specified is to look in
`~/.csl/chicago-author-date.csl`, and if nothing is found there,
to use a default version of chicago-author-date.csl.
You may want to open a separate issue on jgm/pandoc-citeproc
suggesting the use of `default.csl` rather than
`chicago-author-date.csl`. I agree that this would make sense.
|
|
strings are converted for LaTeX and ConTeXt output, closes #1614
|
|
[BUG] Haddock : * and ^ to be escaped in docs
|
|
|
|
|
|
added selectors for nested emphasis (epub.css)
|
|
See
https://www.reddit.com/r/haskell/comments/3f4bgr/the_version_of_cabal_being_used_has_changed/
Maybe this will fix the Cabal version mismatch problem?
|
|
ghc 7.10.2 isn't whitelisted yet.
https://github.com/travis-ci/travis-ci/issues/4478
|
|
|
|
|
|
|
|
Previously the parser failed on this kind of case
.. role:: indirect(code)
.. role:: py(indirect)
:language: python
:py:`hi`
Now it currectly recognizes `:py:` as a code role.
The previous test for this didn't work, because the
name of the indirect role was the same as the language
defined its parent, os it didn't really test for this
behavior. Updated test.
|
|
Org reader: add auto identifiers if not present on headers
|
|
|
|
Refs #2354
This should also fix the table of contents (--toc) when generating a html file
from org input
|
|
...before Cite and Span elements that begin with a "complex"
element. Closes jgm/pandoc-citeproc#157.
|
|
|
|
This generates a bash completion script.
To use:
eval "$(pandoc --bash-completion)"
|
|
|
|
|
|
E.g. `` [:sup:`3`] `` is okay; you don't need `` [:sup:`3`\ ] ``.
|
|
|
