Quarto filter extension that lets you automatically search and replace strings in quarto document when rendering, in a similar way as simple LaTeX text macros.
Define pairs of search string and replacement in the document yaml, and let quarto do the work. The filter searches document text, including link targets. Replacements may include markdown text modifiers (emphasis) and math inline formulae.
-
Format dependent replacements are possible now for all formats that are detectable by quarto extensions, notably pdf and html, see the quarto documentation
-
For long lists of replacements, check out extension
mergemeta, which allows you to merge in data stored under a different key (notsearch-replace) in anotheryamlfile, see under Section Tip
quarto add ute/search-replaceThis will install the extension under the _extensions subdirectory.
If you're using version control, you will want to check in this directory.
Include the filter in the document's yaml, and add a key search-replace. Under this key, define your search-replace pairs as subkeys in the form search : replace. It is a good idea to start the search key with a special character, such as "+" or ".", although it is not required.
Upon rendering, every string or sub-string that matches a search key will be replaced in the main text, and in link targets. Search keys should not be contained in each other - this would give ambiguous results.
There are some reserved keys (currently only one, but more may be added) that start with '--':
- '--when-format--' is used to specify abbreviations that are only rendered when the document format matches the following sub-key.
With the yaml
---
format: html
filters:
- search-replace
search-replace:
+quarto: "[Quarto](https://quarto.org)"
+qurl : https://quarto.org/docs
+forml : $\alpha * \beta = \gamma$
+pyth : "*Pythagoras' theorem*: $a^2 + b^2 = \\dots$"
.doo : "- doodledoo - "
--when-format--:
html:
+br : <br>
+form : html
+wewant: "read on screen"
pdf:
+br : \newline
+form : pdf
+wewant: "print on paper"
+dab : "**dab**"
"!dua" : "`duaaah`"
--- document text
+quarto allows us to write beautiful texts
about +pyth or similar complicated formulas (e.g. +forml),
and to [create our *own* filters](+qurl/extensions/filters.html). +br
Even filters that replace text:+br
.doo+dab+dab+dab!dua, +dab!dua!
Since we wanted to +wewant, we chose to render as +form.
gets rendered, if html, as
Quarto allows us to write beautiful texts about Pythagoras' theorem:
$a^2 + b^2 = \dots$ or similar complicated formulas (e.g.$\alpha * \beta = \gamma$ ), and to create our own filters.
Even filters that replace text:
- doodledoo -dabdabdabduaaah, dabduaaah!Since we wanted to read on screen, we chose to render as html.
- search keys and replacement strings that can be interpreted as yaml because of special characters such as
:, or leading-,`,[,!, have to be enquoted. To be on the safe side, you can just enquote all replacement strings. - backslashes in LaTeX formulae have to be escaped with a second backslash if and only if the containing string is enquoted.
Here is the source code for a minimal example: example.qmd.
Store long lists of search-replace items in an extra yaml file and include it in the documents yaml using the metadata-files key.
With the mergemeta extension, the abbreviations can be merged into the search-replace key. This avoids overwriting document specific abbreviations, and allows to combine multiple abbreviation sources files.
For example, file myabbreviations.yml contains search-replace definitions stored under mystuff:
mystuff:
+quarto: "[Quarto](https://quarto.org)"
+qurl : https://quarto.org/docs
# etc and can be used in qmd document mergemeta-example.qmd with the yaml header
---
format: html
filters:
- mergemeta
- search-replace
metadata-files:
- myabbreviations.yml # defines mystuff
mergemeta:
search-replace: mystuff
--- Make sure to list filter mergemeta before search-replace.
Scott Koga-Browes' lovely python-based pandoc filter pandoc-abbreviations that replaces text strings (not links) inspired me to write this quarto extension. He requires the search keys to start with a "+" sign which gives a nice and clear appearance - they are easy to spot in the source text.