Feature: pandoc-native and pandoc-json rawblock and rawinline elements
#9159
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
cscheid
force-pushed
the
feature/escape-pandoc-ast
branch
from
6a3d543 to
e8bae4c
Compare
cderv
added a commit
that referenced
this pull request
Mar 27, 2024
this was introduced in #9159 and help solve case like this where we need to prevent pandoc from parsing as Markdown the metadata fields passed in the YAML file used with `metadata-file:` For context about `--metadata-file` see https://pandoc.org/MANUAL.html#option--metadata-file > Read metadata from the supplied YAML (or JSON) file. This option can be used with every input format, but string scalars in the metadata file will always be parsed as Markdown.
cderv
added a commit
that referenced
this pull request
Mar 27, 2024
this was introduced in #9159 and help solve case like this where we need to prevent pandoc from parsing as Markdown the metadata fields passed in the YAML file used with `metadata-file:` For context about `--metadata-file` see https://pandoc.org/MANUAL.html#option--metadata-file > Read metadata from the supplied YAML (or JSON) file. This option can be used with every input format, but string scalars in the metadata file will always be parsed as Markdown.
cderv
added a commit
that referenced
this pull request
Mar 27, 2024
this was introduced in #9159 and help solve case like this where we need to prevent pandoc from parsing as Markdown the metadata fields passed in the YAML file used with `metadata-file:` For context about `--metadata-file` see https://pandoc.org/MANUAL.html#option--metadata-file > Read metadata from the supplied YAML (or JSON) file. This option can be used with every input format, but string scalars in the metadata file will always be parsed as Markdown.
cderv
added a commit
that referenced
this pull request
Mar 27, 2024
this was introduced in #9159 and help solve case like this where we need to prevent pandoc from parsing as Markdown the metadata fields passed in the YAML file used with `metadata-file:` For context about `--metadata-file` see https://pandoc.org/MANUAL.html#option--metadata-file > Read metadata from the supplied YAML (or JSON) file. This option can be used with every input format, but string scalars in the metadata file will always be parsed as Markdown.
cderv
added a commit
that referenced
this pull request
Mar 28, 2024
this was introduced in #9159 and help solve case like this where we need to prevent pandoc from parsing as Markdown the metadata fields passed in the YAML file used with `metadata-file:` For context about `--metadata-file` see https://pandoc.org/MANUAL.html#option--metadata-file > Read metadata from the supplied YAML (or JSON) file. This option can be used with every input format, but string scalars in the metadata file will always be parsed as Markdown.
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.
Cf. our discussion in today's eng meeting.
Minimal self-describing test document that now passes the test suite:
This is useful as a mechanism for us to more easily circumvent Pandoc's Markdown parsing (see #9117 for a natural use case), and is also useful for third-party software libraries emitting markdown to be read by Quarto, since emitting Markdown robustly is quite hard to do in general.