Yeah, that’s pretty awful. Thanks for reporting. Obviously, I did my testing with i7tohtml configured. I suppose I could define it as a requirement and “fix” the bugs! (Not serious.)
Invoking a separate process and introducing a dependency on another language was never ideal. I had imagined I’d just translate the relevant bits from i7tohtml.py, which seemed easy enough… but pygments for ruby just invokes a separate Python process anyway so there didn’t seem to be much advantage. I have a half-written lexer for Rouge, a ruby-native syntax highlighter… but I’ve been focusing on the extension directory testing feature in recent development.
I’ll look into ensuring i7tohtml is really optional this weekend. It’ll probably be easy to fix. If it’s harder than I think (which it might be – the extension-parsing code in the release branch is kind of ugly – the worst of that is cleaned up in dev) I’ll push a doc change noting that i7tohtml is functionally a requirement for now (as a work-around, not a fix).