Michael Hatherly

100% behind making the representation of the AST more standalone, as well as the route you're proposing. > should probably be moved to the AST package is the terminal one...

Thanks for the updates. > The type parameter can be used to add additional fields. Any idea yet whether that's going to require significant changes in `CM.jl` to switch, or...

Yes, this is definitely part of the goals for the package, so I think it should be possible to make it work. A JSON+MD output would be a viable option...

I think if we can spec what's needed in the toc.json file then the rest should be relatively straight forward to cook up in a basic form. My understanding is...

Yeah, I'll see if I can hack something together today, it's unlikely to be very pretty for now, and will likely need heavy refactoring at a later stage, but this...

Yes, that's pretty much how it works. It's definitely something that should really be fixed since the expectation is that markdown output from the AST is roundtripable, technically true by...

> I guess for an implementation, there would need to be a new AbstractBlock for the link reference definitions. And then either Link would need to be expanded so that...

Yeah, 2 looks like a better option perhaps, might be nice to have a general mechanism for hooking into different places during parsing for this kind of stuff. Any idea...

There's some rudimentary support for this already, implemented in https://github.com/MichaelHatherly/Publish.jl/blob/c03914feac59fc3937a752bc68a69f16d5507736/src/load.jl#L19-L39 but undocumented currently since I'm not yet decided on the final public interface for it. It is something I'd like...

https://github.com/MichaelHatherly/Tectonic.jl/pull/4#issuecomment-841635220 > It's not documented anywhere in this package, but the `biber` and `biblatex` versions need to be compatible with each other. See "Compatibility matrix" in https://anorien.csc.warwick.ac.uk/mirrors/CTAN/biblio/biber/documentation/biber.pdf. 2.14 and 3.14...