Jürgen Spitzmüller
Jürgen Spitzmüller
I tried the approach, but the problem with this is that it does not pass the actual command and options, and I can't see how to do that without the...
> but we have not provided a fully-flexible mechanism to pick up arbitrary arguments. I'm not sure it would be easy. For example, here we'd need to expandably parse the...
Thanks, I understand it is more complex than I anticipated. FWIW, as a workaround, I do now lowercase options before passing them to `\setkeys` in `polyglossia`. Since we only use...
#251 is not the culprit here.
Should be fixed.
The problem is fixed, AFAICS
Hit by this as well after an update to 3.9.3. Costed me a 2hr trip through the city as I didn't check whether the sync was successful before going to...
What do you propose? We need those language switches to have correct language markup in the TOC.
I suppose you have checked whether the bugs we had fixed with these writings (such as #309) haven't come back?
> Shouldn't that be `acadian`? Yes, `acadien` is wrong.