Fix roundtripping of raw latex blocks #559
Merged
Conversation
This file contains hidden or 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
|
Thanks. This looks good. With that said, I'm starting to wish we had a test suite here. |
4 tasks
jjallaire
approved these changes
Oct 2, 2024
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.
Fixes #558
Update custom pandoc writer to preserve raw latex blocks ({=latex}) when using Visual Editor.
This was due to a Pandoc 3.2+ change that stripped these blocks when we converted from the AST to markdown.
NOTE, we still don't preserve
{=tex}fenced blocks, but that was true before the pandoc change. I tried updating the script to also preserve{=tex}but it didn't work, so the root cause is elsewhere.