Günter Milde

> Selecting `OT1` as the main encoding and therefore the preferred one effectively makes many other Latin encodings no-op (`T4` and `T5` are exceptions), so I wonder if it makes...

@ivankokan > [...] missing Đđ which is at least handled somehow)? Đđ are handled exactly like the other "adorned" characters: T1 has slots for pre-composed characters while in OT1 they...

> If necessary, the preferred encoding for a language can be set by users, if the font is not a problem or for whatever reason they want. Loading a font...

> If I had to guess at the reason for three space indentation, it is simply that explicit markup in reST uses `\.\. +\w\s*::`, and hence the minimum amount of...

This [other sphinx-doc](https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html#directives) clarifies "the *official* way to do this, with and without :linenos:" in detail. It may be amended with another [indentation](https://docutils.sourceforge.io/docs/ref/rst/restructuredtext.html#indentation) peculiarity: without option block, the least indented...

The error points to `.. automethod:: __init__`. This is a directive added by the "autodoc" Sphinx extension. It seems the docstring of `AlgoDeliverEnum.__init__()` contains an unbalanced inline markup.

I ask for two reasons: a) if I could just re-use what is done in the l3 kernel, handling of literal characters and LICRs would keep in sync also with...

I ask for two reasons: a) if I could just re-use what is done in the l3 kernel, handling of literal characters and LICRs would keep in sync also with...

> `\MakeLowercase{Σ}` will always give a terminal sigma, as there is a string boundary at the start and the end of every entry. Yes. My question is what I could...

> Thanks for the explanation. I believe the two comparable directives are `csv-table` and `raw`. The both allow the content in the body or alternatively inject it via a `:file:`...