mdbook-katex is a preprocessor for mdBook, pre-rendering LaTeX equations to HTML at build time. It allows for very fast page loading, compared to rendering equations in the browser.
This preprocessor uses the katex crate; see this page for the list of supported LaTeX functions.
First, install mdbook-katex
Non-Windows users:
shell
cargo install mdbook-katex
Windows users:
The recommended way is to download the latest x86_64-pc-windows-gnu.zip from Releases for the full functionality. See #67 for the reasons.
Then, add the following lines to your book.toml file
```toml [output.katex]
[output.html]
[preprocessor.katex] renderers = ["html"] ```
You can now use $ and $$ delimiters for inline and display equations within your .md files. If you need a regular dollar symbol, you can escape delimiters with a backslash \$.
```
Here is an inline example, $ \pi(\theta) $,
an equation,
$$ \nabla f(x) \in \mathbb{R}^n, $$
and a regular $ symbol. ```
LaTeX equations will be rendered as HTML when running mdbook build or mdbook serve as usual.
The preprocessor supports passing options to the katex-rs crate in order
to configure its behaviour. These options are specified under the
[preprocessor.katex] directive.
The currently supported arguments are:
| Argument | Type |
| :- | :- |
| output | string |
| leqno | boolean |
| fleqn | boolean |
| throw-on-error | boolean |
| error-color | string |
| min-rule-thickness | number |
| max-size | number |
| max-expand | number |
| trust | boolean |
There are also options to configure the behaviour of the preprocessor:
| Option | Default | Description |
| :- | :- | :- |
| static-css | false | Generates fully static html pages with katex styling |
| macros | None | Path to macros file (see Custom macros) |
| include-src | false | Include math expressions source code (See Including math Source) |
| block-delimiter | {left = "$$", right = "$$"} | See Custom delimiter |
| inline-delimiter | {left = "$", right = "$"} | See Custom delimiter |
For example:
toml
[preprocessor.katex]
renderers = ["html"]
static-css = false
include-src = false
block-delimiter = {left = "$$", right = "$$"}
inline-delimiter = {left = "$", right = "$"}
Custom LaTeX macros must be defined in a .txt file, according to the following pattern
txt
\grad:{\nabla}
\R:{\mathbb{R}^{#1 \times #2}}
You need to specify the path of this file in your book.toml as follows
toml
[preprocessor.katex]
macros = "path/to/macros.txt"
These macros can then be used in your .md files
```
$$ \grad f(x) \in \R{n}{p} $$ ```
This option is added so users can have a convenient way to copy the source code of math expressions when they view the book.
When include-src is set to true, each math block is wrapped within a <data> tag with class="katex-src" with the included math source code being its value attribute.
For example, before being fed into mdbook,
```markdown Define $f(x)$:
$$ f(x)=x^2\ x\in\R $$ ```
is preprocessed into (the content of the katex spans are omitted and represented as …)
```markdown Define …:
… ```
The math source code is included in a minimal fashion, and it is up to the users to write custom CSS and JavaScript to make use of it.
For more information about adding custom CSS and JavaScript in mdbook, see additional-css and additional-js.
If you need more information about this feature, please check the issues or file a new issue.
To change the delimiters for math expressions, set the block-delimiter and inline-delimiter under [preprocessor.katex].
For example, to use \(and \) for inline math and \[ and \] for math block, set
toml
[preprocessor.katex]
renderers = ["html"]
block-delimiter = {left = "\\[", right = "\\]"}
inline-delimiter = {left = "\\(", right = "\\)"}
Notice that the double backslash above are just used to escape \ in the TOML format.
The build artifact of the book will be in a folder named html inside the directory you specify instead of being directly there.
Consider this when you use mdbook_katex in your CIs.
$\backslash$ does not work, but you can use $\setminus$ instead.
Only the x86_64 Linux, Windows GNU, and macOS builds have full functionality, all other builds have compromised capabilities. See #39 for the reasons.