Jean-François B.

@tk0miya will tell better but is seems your code exploits ``is_available()`` call for after-effect. How about this: ```diff --- inkscapeconverter-old.py 2022-08-15 13:58:14.000000000 +0200 +++ inkscapeconverter.py 2022-08-15 14:29:03.000000000 +0200 @@ -33,6...

let's wait for @tk0miya :smile: I expect the idea is that `is_available()` was supposed safe to be called only once, but in your extension it is doing extra set-up. It...

> At thsi stage my guess is that `textcomp` is not aware of relatively recent `zlmtt` font package (2014), I reported the issue to the [`zlmtt`](https://ctan.org/pkg/zlmtt) (a monospace font which...

I understand the management of hooks is powerful concept. And that it is documented. What surprised me is that old legacy usage of `\AtBeginDocument` was not left standing but transmogrified...

The `\everyjob` settings in LaTeX format (as recently updated by yourself) actually destroy the commandline filename safety: ```console $ pdflatex ééé ``` is ok but ```console $ pdflatex \\input{ééé} ```...

> well without the everyjob settings the first form wouldn't work either Would it make sense to delay the everyjob utf8 related activation (I mean by that the activation of...

No I don't have much of an issue but a slight uneasiness about active characters already on command line. For example, pdflatex \\input \\detokenize{é}#1.tex works but is somewhat complicated, and...

The patched latex.ltx appears to work: generation of format defining macro `\foo` worked, and I could use it with another file using `\foo` in document body.

The original had not issue with lualatex. The patch seems to treat xelatex and lualatex engine alike. Is anything lost on lualatex side by so-doing?

I was going to test luatex with OpenType fonts, but already xetex fails, even with patch [from your comment](https://github.com/davidcarlisle/dpctex/issues/15#issuecomment-393842696) ```latex \documentclass{article} \def\abc{abc} \usepackage{fontspec} \setmainfont{Hoefler Text}% I am on a Mac...