Age | Commit message (Collapse) | Author | Files | Lines |
|
This allows custom css to modify themes, instead of being replaced
by themes.
|
|
(Dmitry Smirnov, jgm/pandoc-templates#89)
* Made option "center" configurable.
* Added new options "maxScale" and "slideNumber".
* Added comments to existing options.
|
|
Closes #1949.
|
|
The minified versions no longer ship with the library.
|
|
|
|
Not title page!
|
|
This fixes a bug introduced by the previous fix.
|
|
This aids styling, making it possible for example to set 0 margins
on the title page. Closes jgm/pandoc#1758.
|
|
Closes #1648.
|
|
Fixes jgm/pandoc-templates#70.
Thanks to bluebirch.
|
|
Fixes a bug when there is verbatim inside notes.
Closes #1616.
|
|
Currently, pandoc has hard-coded the following in order to make tight lists in
LaTeX:
```hs
text "\\itemsep1pt\\parskip0pt\\parsep0pt"
```
Which is fine, but does not allow customizations. For example, the `memoir`
class already has a `\tightlist` declaration for this purpose:
```tex
\newcommand{\tightlist}{%
\setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}
```
I'm proposing to use a similar solution:
```diff
@@ In Writers/LaTeX.hs:
-then text "\\itemsep1pt\\parskip0pt\\parsep0pt"
+then text "\\tightlist"
@@ In templates/default.latex:
+\newcommand{\tightlist}{%
+ \setlength{\itemsep}{1pt}\setlength{\parskip}{0pt}\setlength{\parsep}{0pt}}
```
This allows us to customize the tightness to our needs.
Backward Compatibility
If a person is using a custom LaTeX template (not based upon the `memoir`
class), the `\tightlist` declaration must be added.
|
|
Previously we just expected 'title', 'subtitle', 'author', 'date'.
Now we still support those, but also support the format recommended
for epub metadata in the pandoc README:
---
title:
- type: main
text: My Book
- type: subtitle
text: An investigation of metadata
creator:
- role: author
text: John Smith
- role: editor
text: Sarah Jones
identifier:
- scheme: DOI
text: doi:10.234234.234/33
publisher: My Press
rights: (c) 2007 John Smith, CC BY-NC
...
|
|
Closes #1549. Thanks to lemzwerg.
|
|
|
|
The templates are duel licensed, BSD3 and GPL2+.
|
|
|
|
Headers.
We might also want to do this elsewhere (for pars, for example).
|
|
|
|
These can be set to get `\listoftables` and `\listoffigures`.
Closes #1407.
At this point we won't add a command line argument, because
this only affects one writer. But the variables can be set
at the command line with
-Vlof -Vlot
or in YAML metadata.
|
|
They are supposed to be only "advisory" in HTML5, but apparently
kindlegen needs them.
|
|
|
|
|
|
In this first version, all dokuwiki files are straight copies of the
media wiki counterparts.
|
|
This ensures that straight quotes appear as straight, rather than
being treated as curly. See #889.
|
|
Now the `title`, `section`, `header`, and `footer` can all be set
individually in metadata. The `description` variable has been
removed.
Quotes have been added so that spaces are allowed in the title.
If you have a title that begins
COMMAND(1) footer here | header here
pandoc will parse it as before into a title, section, header, and
footer. But you can also specify these elements explicitly.
Closes #885.
|
|
* Depend on pandoc 1.12.
* Added yaml dependency.
* `Text.Pandoc.XML`: Removed `stripTags`. (API change.)
* `Text.Pandoc.Shared`: Added `metaToJSON`.
This will be used in writers to create a JSON object for use
in the templates from the pandoc metadata.
* Revised readers and writers to use the new Meta type.
* `Text.Pandoc.Options`: Added `Ext_yaml_title_block`.
* Markdown reader: Added support for YAML metadata block.
Note that it must come at the beginning of the document.
* `Text.Pandoc.Parsing.ParserState`: Replace `stateTitle`,
`stateAuthors`, `stateDate` with `stateMeta`.
* RST reader: Improved metadata.
Treat initial field list as metadata when standalone specified.
Previously ALL fields "title", "author", "date" in field lists
were treated as metadata, even if not at the beginning.
Use `subtitle` metadata field for subtitle.
* `Text.Pandoc.Templates`: Export `renderTemplate'` that takes a string
instead of a compiled template..
* OPML template: Use 'for' loop for authors.
* Org template: '#+TITLE:' is inserted before the title.
Previously the writer did this.
|
|
|
|
Now it can be used with options, if needed.
Thanks to Bernhard Weichel.
|
|
|
|
|
|
We need the mathspec library, not just fontspec, for this.
We also need to set options for setmathfont. Closes #734.
|
|
|
|
Reason: some browsers have trouble with the gzipped js file,
at least on the local file system.
Closes #795.
|
|
|
|
|
|
|
|
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.
|
|
Minor fixes to OPML writer.
Improved OPML reader tests.
|
|
The template redefines `\includegraphics` to give special treatment
for too-wide images. But this causes problems for literal uses
of `\includegraphics`. This change allows authors to use
`\Oldincludegraphics`, as in the latex template.
|
|
Microtype needs to know what fonts are being used.
Thanks to dfc for the patch.
|
|
|
|
Configure it for toc depth. Thanks to Aditya Mahajan.
|
|
This produced a duplicate toc, in conjunction with `\placelist`.
|
|
This yields behavior equivalent to the other writers, numbering
level 4 and 5 headers too.
Closes #753.
|
|
Thanks to Joost Kremers.
|
|
|
|
Use upquote package if it exists.
|
|
* RTF writer: Export writeRTFWithEmbeddedImages instead of
rtfEmbedImage.
* Text.Pandoc: Use writeRTFWithEmbeddedImages for RTF.
* Moved code for embedding images in RTF out of pandoc.hs.
|
|
The previous default was to use `<q>` tags in HTML5.
But `<q>` tags are also valid HTML4, and they are not very
robust in HTML5. Some user agents don't support them,
and some CSS resets prevent pandoc's quotes CSS from working
properly (e.g. bootstrap). It seems a better default just
to insert quote characters, but the option is provided for
those who have gotten used to using `<q>` tags.
|