I'm not sure if there is a reason why these were witheld from the
default beamer template, but it seemed to work when I added it in to my
Beamer project.
There was some previous discussion about this at jgm/pandoc#1600.
Every heading element semantically creates a new section. Three
consecutive heading elements, e.g. `<h1></h1>`, `<h2></h2>`,
`<h3></h3>`, are semantically equivallent to a section with two nested
subsections. This is not the intended meaning of subtitle, author, and
date, making plain `<p>` elements the better choice. This is one of the
W3C's [common idioms].
This change is the result of discussions on issue jgm/pandoc#3119.
[common idioms]: https://www.w3.org/TR/html5/common-idioms.html#common-idiomsFixes: jgm/pandoc#3119
Adding ability to define custom font families. Needed for correct `polyglossia` operation with Cyrillic fonts and perhaps can find some other usages. Example usage in YAML metadata:
```
fontfamilies:
- name: \cyrillicfont
font: Liberation Serif
- name: \cyrillicfonttt
options: Scale=MatchLowercase
font: Liberation Mono
```
The beamerarticle package needs to be loaded directly after the documentclass
declaration. Loading it later (e.g. using the -H option) leads to several
errors due to package dependencies.
This patch also introduces a new variable "beamerarticle" to activate the
beamerarticle package.
Here's a minimal case:
\documentclass[]{article}
\usepackage{hyperref}
\begin{document}
\section{\%á}
\end{document}
Without this change, this fails on the second invocation of xelatex.
See https://tex.stackexchange.com/questions/313266/and-non-ascii-characters-in-headings
This affects inputs this like
# %á
with pdf output via xelatex.
Adding ability to define custom font families. Needed for correct polyglossia operation with Cyrillic fonts and perhaps can find some other usages.
Example usage in YAML metadata:
```
fontfamilies:
- name: \cyrillicfont
font: Liberation Serif
- name: \cyrillicfonttt
options: Scale=MatchLowercase
font: Liberation Mono
```
Thus you can say `papersize: a4` and the latex will contain
`a4paper`.
This change may break some existing workflows; if you currently
specify `a4paper`, you'll get `a4paperpaper` which is meaningless.
However, the change seems worth it, as it will make the
`papersize` variable work uniformly across ConTeXt, LaTeX,
and html->pdf via wkhtmltopdf.
