Add parameters to capture intermediate transformation results #449
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses #440 by adding two new parameters
transformed-docbook-inputandtransformed-docbook-outputto capture the pre-processed DocBook input that will be transformed into HTML and the immediate (HTML-ish) results of that transformation (before chunking).I've adopted @fsteimke 's proposal in #441 slightly. I've only ever wanted these intermediate results for debugging, and I've been satisfied to just tweak the stylesheets when necessary (for example, the block of commented-out code that's been removed in this PR). But making them options seems reasonable and in that case, I can imagine wanting to capture either one, depending on what I'm debugging.
Thank you, Frank!
Close #440
Close #441