Vincenzo Mantova

(Alternatively, Pathname functions should work on bytes, not strings! Which might be the safer alternative, since detecting the filesystem encoding is not an easy task.)

I should note that this is not a Windows bug, we have replicated it on Linux and macOS.

The math parser is now slightly less broken, but still very broken. The operator precedences are all slightly wrong – they should have been set reading the `\pgfmathdeclareoperator` commands in...

Uhm, the `` error changes with TeX Live version. Is there a standard solution for that particular problem?

> What you can do for the CI test is to add `\let\clearpage\relax` after `\usepackage{pgf}` Done! In the meanwhile, I changed my mind. I can definitely fix the radians operator...

By the way, this should be draft as well – I discovered that it breaks pgfplots somehow! Maybe because of `ExpandedPartially`? I don't know right now, I need to test...

> That said, `vertical-align` is actually specified only for a limited number of display contexts. Quoting [MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/vertical-align): > > > The vertical-align CSS property sets vertical alignment of an inline,...

> in a healthy setting Is raw beamer healthy? Probably not! It's easier to look at the uses of `getSource` because there are only two of them. `DefMathI` uses it...

Quick word: this is actually pretty obvious in hindsight. You are slightly abusing the descent parser by evaluating the fuctions within the subrules. It's normal for a rule to be...

> ``` > .llap { > float: right; > } > ``` That is infinitely better, thanks! I am wondering if we should just promote `\llap` to an inline-block constructor...