| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
|
|
|
|
|
|
* CPP around deprecated `parseTime`.
* Text.Pandoc.Compat.Locale -> Text.Pandoc.Compat.Time,
now exports Data.Time.
|
|
- 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.
|
|
This way we don't get an error when this is used as a moveable
argument.
Closes #2136.
|
|
Closes #2363.
|
|
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.
|
|
|
|
HTML, LaTeX writers adjusted.
The special characters are '<','>','|','"','{','}','[',']','^', '`'.
Closes #1640, #2377.
|
|
Closes #2386.
|
|
Previously `<section>` tags were just parsed as raw HTML
blocks. With this change, section elements are parsed as
Div elements with the class "section". The HTML writer will
use `<section>` tags to render these Divs in HTML5; otherwise
they will be rendered as `<div class="section">`.
Closes #2438.
|
|
|
|
Added support for <xref> tag in DocBook reader
|
|
Change variable to polyglossia-lang.name and .options
|
|
The actual definition has been moved to Text.Pandoc.Shared,
but to avoid breaking changes we reexport it here.
|
|
Better man writer (revised)
|
|
Really close #2446.
|
|
Closes #2446.
|
|
closes #2437
|
|
|
|
|
|
See #2401.
|
|
* src/Text/Pandoc/Writers/Man.hs: Set $pandoc-version$ to be pandocVersion.
|
|
`src/Text/Pandoc/Shared.hs`, so that all Writers can access this variable
without importing `src/Text/Pandoc.hs`, preventing circular import.
* pandoc.hs: Import pandocVersion from `Text.Pandoc.Shared`.
* src/Text/Pandoc.hs: Remove the definition of pandocVersion
and relevant import.
* src/Text/Pandoc/Shared.hs: Add the definition of pandocVersion
and relevant import.
|
|
* src/Text/Pandoc/Writers/Man.hs: Set $hyphenate$ to be true.
|
|
|
|
|
|
Support bidirectional text output with XeLaTeX, ConTeXt and HTML
|
|
closes #2191
|
|
|
|
Closes #2395.
|
|
# Header {id="myid" class="foo bar"}
is now equivalent to
# Header {#myid .foo .bar}
Closes #2396.
|
|
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
|
|
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.
|
|
This allows the test suite to work without installing pandoc first.
It also brings the docx writer in line with the odt writer.
|
|
strings are converted for LaTeX and ConTeXt output, closes #1614
|
|
[BUG] Haddock : * and ^ to be escaped in docs
|
