Age | Commit message (Collapse) | Author | Files | Lines |
|
`linkcolor` only affects internal links, and `urlcolor` only
affects linked URLs. For external links, the option to use is
`filecolor`.
Closes #4822.
|
|
It is a bit awkward to have a title for every frame, but not for the one
that holds the table of contents. Allow users to specify a title if they
wish.
|
|
This change allows beamer themes to change the
template and font (as Metropolis does).
Closes #4450.
|
|
New variable with same name as comparable variable in (proposed) reveal.js template, so that background images can indicated for both presentation formats with one variable.
|
|
* LaTeX template: Use `pgfpages` package; this is needed for notes on second screen in beamer
* LaTeX template: Add `beameroption` variable in template
|
|
* Provide `bidi` package's option using `\PassOptionsToPackage`. This avoid clash when `polyglossia` loads it first and then it is loaded again for XeLaTeX when `latex-dir-rtl` defined.
* Adjust test suite for LaTeX template change.
|
|
The old template produced numbered sections with some recent
versions of beamer.
Thanks to Thomas Hodgson.
|
|
* Add pagestyle support
* Add pagestyle option to MANUAL.txt
* Moved mention of pagestyle to the section on variables
|
|
Otherwise we seem to get an error; biblatex wants polyglossia
language to be defined.
Closes #4073.
|
|
This caused an error in beamer.
Footnotes already work in tables in beamer, without this code.
|
|
The textcomp package allows pdfLaTeX to parse `€` directly, making the \euro command unneeded. Closes #3801.
|
|
Prevents changes to documents defined using the dvipsnames list (e.g. `Blue` gives a different result with svgnames enabled).
|
|
|
|
It needs to be loaded as late as possible.
Closes #3898.
|
|
Beamer loads `xcolor` rather than `color`, and thus the `dvipsnames` option doesn't take effect. This also provides a wider range of colour selections with the `svgnames` option. Closes #3877.
|
|
All conditionals use the `beamer` variable set by the writer.
Closes #3878.
|
|
...by using the `luatexja-fontspec` and `luatexja-preset` packages. Use
existing `CJKmainfont` and `CJKoptions` template variables. Add
`luatexjafontspecoptions` for `luatexja-fontspec` and `luatexjapresetoptions`
for `luatexja-preset`.
|
|
Avoids an options clash when loading a package (e.g. `tufte-latex`) that uses `hyperref` settings different from those in the template (introduced in <https://github.com/jgm/pandoc-templates/commit/feffd7c64abab863abd3f6458d1c445d6bfe7fc4>).
|
|
Closes #3768.
|
|
See https://github.com/jgm/pandoc-templates/commit/1475299c9aebfe3e47c135d6653202db3b2f6696#diff-c7c27b8e99f898fde7715afd9ae8cd02R126
However, this is not a complete fix:
https://github.com/jgm/pandoc-templates/pull/208#issuecomment-309631622
Thanks to zeeMonkeez. See #2378.
|
|
- reordered `lang` variable handling to immediately before `bidi`
|
|
* LaTeX: Load `parskip` before `hyperref`.
According to `hyperref` package's `README.pdf`, page 22, `hyperref` package
should be loaded after `parskip` package.
* Adjust tests for previous change.
|
|
Declare our redefined `\href` robust.
Fixes #3651. (#3652)
|
|
Previously the LaTeX writer created invalid LaTeX
when `--listings` was specified and a code span occured
inside emphasis or another construction.
This is because the characters `%{}\` must be escaped
in lstinline when the listinline occurs in another
command, otherwise they must not be escaped.
To deal with this, adoping Michael Kofler's suggestion,
we always wrap lstinline in a dummy command `\passthrough`,
now defined in the default template if `--listings` is
specified. This way we can consistently escape the
special characters.
Closes #1629.
|
|
|