v1.5.0
This minor release introduces a few new features.
It provides a Djot extension for symbol-based conditionals.
Such "Djot templates" are notably used by resilient.sile version 2.2 to generate customizable "book matter" pages.
Reciprocally, version 2.2 of the resilient.sile collection introduces new environments for definition lists and verbatim text, which are now used when available. This offers the ability to easily style and customize such elements.
New features
-
Common
- feat: Use resilient.verbatim if available and refactor verbatim calls (#98)
We now use the verbatim environment provided by the resilient.verbatim package, when available, instead of SILE's default implementation, to benefit from its styling features. - feat: Support class- or package-provided definition environment (#99, 100)
This notably allows using the definition environment provided by the resilient.defn package, and to benefit from its styling features. - feat: Improve resilient class detection (#96)
Contributed by @nawordar, this internal change is mostly for class developers wanting to use a resilient class as their base class.
- feat: Use resilient.verbatim if available and refactor verbatim calls (#98)
-
Djot
- feat: Djot extension for symbol-based conditionals (#93)
As earlier versions introduced user-defined symbols, this Djot non-standard extension now allows using such symbols as conditionals, for example to conditionally include a block of text depending on the presence of a symbol. - feat: Support more decorative pendants in Djot (#95)
This allows using other pendants from the couyards.sile collection.
- feat: Djot extension for symbol-based conditionals (#93)
Other notable changes
As usual, the documentation also received a number of improvements. Notably, it now uses a resilient master document with book matter pages and covers (#97).
A few 3rd-party dependencies are updated. Notably, the silex.sile dependency is upgraded. Be aware that the latter overrides some of the core SILE components, changing their behavior — normally for the better, but it may break some workflows.