Age | Commit message (Collapse) | Author | Files | Lines |
|
Simplify the approach of #5212, ensuring that `mainfont` is used as the base font for scaling and that LuaLaTeX does not display the mono font with TeX ligatures (as it does not use the `Mapping=tex-ansi` option).
With a modified version of `\defaultfontfeatures`, fontspec will continue to report scaling against the old default font in the log, but it nonetheless displays main font at the specified size. Using this rather than setting `Scale=MatchLowercase` for each family individually means that users will not lose scaling when upgrading to the new template if they were using other font options. Scaling can be disabled for an individual family by adding the option `Scale=1` to `sansfontoptions`, `monofontoptions`, etc.
Remove the `\setromanfont` command added in #4665, as this is not documented in the fontspec manual and appears to be a deprecated alias for `\setmainfont`.
For the release notes, I should also add that one can imitate the previous appearance with `-V mainfontoptions="Scale=MatchLowercase"`.
|
|
Addresses closed issues #4675, #3896, #1327.
This renders `\subtitle` using the `etoolbox` package if `\subtitle` is not already
defined by the documentclass (as it is in beamer, KOMA, memoir classes).
Based on an example from Enrico Gregorio, <https://tex.stackexchange.com/a/50186>.
Update list of LaTeX packages.
Note that `etoolbox` must be loaded outside the command definition.
Putting it inside causes an error if `\title` is placed after `\begin{document}`.
It's already loaded on LuaLaTeX/XeLaTeX in any case.
|
|
When `Scale=MatchLowercase` is set as a default font option, this scales `mainfont` against the old default, meaning that it resizes whatever is set as the main font to match the metrics of Latin Modern. This can result, for example, in a document set to 12pt appearing in 11pt or 13pt. Setting this option for individual families allows everything to scale against the main font, and permits the user to override the setting if desired. Note that it is not necessary to specify `Ligatures=TeX`, as this is already set by default for the appropriate families. See the `fontspec` manual: <https://ctan.org/pkg/fontspec>.
Those who specify font-options in metadata may need to add `Scale=MatchLowercase`, which will now only be provided if `(roman|sans|math|mono)fontoptions` aren't given explicitly.
|
|
Closes #4249. Thanks to @reagle.
|
|
* Use Babel for LuaTeX. There are a number of bugs in Polyglossia under LuaLaTeX with common languages, e.g. <https://github.com/reutenauer/polyglossia/issues/182>.
* Load xcolor. The `xcolor` package must be loaded before the `footnote` package, which we load to fix foonotes in tables. Closes #4861.
* Load xurl if available. This breaks URLs in more locations. Only available with TeX Live 2018 and later.
* Remove obsolete fixltx2e package
* Reindent. Use two spaces to be consistent internally and with other templates.
* Use `bookmark` if available. The `bookmark` package can sometimes correct the levels of headings where `hyperref` cannot: see <https://komascript.de/release3.26>.
* Update LaTeX tests
|
|
|
|
* Add 'landmarks' id attribute to the landmarks nav.
* Replace old default CSS removing numbers from ol.toc li
with new rules that match `nav#toc ol, nav#landmarks ol`.
* We keep the `toc` class on `ol` for backwards compatibility.
|
|
Partially addresses #5179
|
|
The `bookmark` package can sometimes correct the levels of headings where `hyperref` cannot: see <https://komascript.de/release3.26>.
|
|
Use two spaces to be consistent internally and with other templates.
|
|
|
|
This breaks URLs in more locations. Only available with TeX Live 2018 and later.
|
|
The `xcolor` package must be loaded before the `footnote` package, which we load to fix foonotes in tables. Closes #4861.
|
|
There are a number of bugs in Polyglossia under LuaLaTeX with common languages, e.g. <https://github.com/reutenauer/polyglossia/issues/182>.
|
|
Closes #5146.
|
|
This fixes the previous commit for parskip and KOMA classes.
|
|
This is just a change to the default latex template.
|
|
Closes #5104.
|
|
Many of these borrowed from the Chicago Manual of Style 10.42, 'Scholarly abbreviations', <https://www.chicagomanualofstyle.org/book/ed17/part2/ch10/psec042.html>.
|
|
Equality of Lua objects representing pandoc AST elements is tested by
unmarshalling the objects and comparing the result in Haskell. A new
function `equals` which performs this test has been added to the
`pandoc.utils` module.
Closes: #5092
|
|
Closes #5088.
|
|
This opens up the possibility of setting the romanfont in xelatex/lualatex.
Note that mainfont actually oversets sansfont in headings
|
|
The underline style is now deprecated.
Previously `--atx-headers` would enable the single-line
style; now the single-line style is always used.
Closes #5038.
|
|
|
|
|
|
This makes it possible to iterate over all field names of an AST element
by using a generic `for` loop with `pairs`:
for field_name, field_content in pairs(element) do
…
end
Raw table fields of AST elements should be considered an implementation
detail and might change in the future. Accessing element properties
should always happen through the fields listed in the Lua filter docs.
Note that the iterator currently excludes the `t`/`tag` field.
|
|
Methods usable on Lists can also be used on MetaList objects.
|
|
Passing a MetaList object to the constructor `pandoc.MetaList` now
returns the passed list as a MetaList. This is consistent with the
constructor behavior when passed an (untagged) list.
Previously, the constructor used to create a new MetaList with the
passed MetaList as its only element.
|
|
Custom writers have access to the global variable `PANDOC_DOCUMENT`. The
variable contains a userdata wrapper around the full pandoc AST and
exposes two fields, `meta` and `blocks`. The field content is only
marshaled on-demand, performance of scripts not accessing the fields
remains unaffected.
|
|
Custom writers can specify an optional `Setup` function. The function
takes the full Pandoc document as input and should not return any value.
Users can use this function to configure the writer depending on the
given document's content or its metadata.
data/sample.lua: add sample use of Setup function.
The change allows to control the image format used to encode the image
produced from dot code.
Closes #4957
|
|
|
|
Make ListAttributes a datatype. The type is similar to Attr.
|
|
So far, we don't actually write any custom properties,
but we have the infrastructure to add this.
See #3034.
|
|
|
|
Introduce a new variable `hyperrefoptions` to pass to the hyperref package.
This allows us (for example) to specify `hyperrefoptions: linktoc=all` in a YAML block.
|
|
I suppose that you copy-pasted the Russian translations from babel[1] package. Actually, it has two versions — `captionsrussian@ancient` and `captionsrussian@modern`, the former contains translations for the pre-revolution (1918) orthography.
[1]: http://ctan.math.utah.edu/ctan/tex-archive/macros/latex/contrib/babel-contrib/russian/russianb.ldf
|
|
Add the `title-block-header` identifier to the `header` element, to make it easier to style precisely.
|
|
Fixes #4798
|
|
epub:type of first section epub:type of body
-------------------------- ------------------
prologue frontmatter
abstract frontmatter
acknowledgments frontmatter
copyright-page frontmatter
dedication frontmatter
foreword frontmatter
halftitle, frontmatter
introduction frontmatter
preface frontmatter
seriespage frontmatter
titlepage frontmatter
afterword backmatter
appendix backmatter
colophon backmatter
conclusion backmatter
epigraph backmatter
Otherwise body will have epub:type 'bodymatter'.
This only affects epub3.
See http://www.idpf.org/epub/profiles/edu/structure/#h.l0bzsloklt10
Closes #4823.
|
|
|
|
Add support for publisher, address, pubPlace, and date variables.
|
|
- Ensure that title element is always present, even if empty.
- Put author tags in the template, rather than adding them in
the writer.
Closes #4839.
|
|
`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.
|
|
Closes #4803
After this commit use `$titleblock$` in order to get what was contained
in `$title$` before, that is a title and subtitle rendered according to
the official rST method:
http://docutils.sourceforge.net/docs/user/rst/quickstart.html#document-title-subtitle. from
With this commit, the `$title$` and `$subtitle$` metadata are available and they
simply carry the metadata values. This opens up more possibilities in templates.
|
|
This change allows beamer themes to change the
template and font (as Metropolis does).
Closes #4450.
|
|
Fix (add) the missing option 'rollingLinks' in reveal.js template.
|
|
* Edited FR translation, Cc (Carbon Copy) translates to 'Copie carbone' : Cc
* Edited FR translation, 'Chapter' translates 'Chapitre' (typo)
* Edited FR translation, 'Figure' translates to 'Figure'
* Edited FR translation, 'Glossary' translates to 'Glossaire'
* Edited FR translation, 'to' translates to 'à'
* Edited FR translation, first letter to uppercase
* Edited FR translation, 'Table' translates to 'Tableau'
|
|
Fixes #4728
|
|
...provided by the argument to `--mathjax` or the normal
pandoc default, rather than a hard-coded one in the template.
Closes #4701.
|