Peter Williams

@mskblackbelt Yeah, I think my recommendation for your use case would be to do something outside of Tectonic. It wouldn't be too hard to implement your idea, I think, but...

No, we don't. I need to find a way to communicate this more clearly, but all of the TeX and bibtex engine code is integrated into Tectonic — it's a...

The relevant C code is compiled and linked into the Rust binary and called from the Rust code — no external binaries are invoked.

In principle, yes, but there are two reasons I lean against that path: 1. I'm pretty sure that Ghostscript is very large with a lot of interactions with the broader...

Well, the situation still hasn't changed. In fact, one thing I've come to appreciate over time is that Ghostscript is generally considered to be a pretty significant security hazard these...

Glad to hear it. If anyone has any use cases where the generate-PDF-externally approach really seems unworkable, that would be good to know about, but I think I'm going to...

That's too bad. My guess is that LaTeX-Workshop is parsing the output of the TeX program, and isn't recognizing Tectonic's non-traditional output form. Fixing this would very likely require some...

The recommended route is to copy the file to place it next to your main `.tex` file. However, there are some issues that crop up if you're running Tectonic from...

Yeah, sadly this story has not improved over the past, gulp, year. *In principle* I'd like to recommend that you build your files into a custom bundle, but the infrastructure...

It's been a *long* time without followup and we have a variety of similar issues logged, so I'm going to go ahead and close this one.