Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add AST dump as outputter and inputter #2127

Draft
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

alerque
Copy link
Member

@alerque alerque commented Oct 3, 2024

Followup on code and discussion in #2113

alerque and others added 5 commits October 4, 2024 00:35
This also comes with the ability for *any* outputter to pre-process the
AST tree if it wanted to (e.g. for remove leaf types it would not be
able to output. If the outputter doesn't do anything to the AST it is
just a pass-through step.

Note this does *not* yet walk the AST and do any AST munging that
functions might engage in, it only catches the top level tree as parsed
by the inputter.

Additionally it is not a full serialization of the AST that could be
read back in with an input driver. We'd need a new dependency on
something like serpent for that, which would be a lovely next step.
@alerque
Copy link
Member Author

alerque commented Oct 3, 2024

As of this moment this is just a rough POC. It can round trip at least some basic documents from XML/SIL → AST output -> AST input -> PDF.

No ETA on this because there are quite a few questions about how this should work and why and I haven't even given it a spin in my own workflows yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants