aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJonas Smedegaard <dr@jones.dk>2025-05-26 22:18:44 +0200
committerJonas Smedegaard <dr@jones.dk>2025-05-26 22:19:21 +0200
commitcfb64142ddefba1a6c596c145b047dacbc9f885a (patch)
tree9b7c9e72e43ad0d0b9f19d7f2d1b43d76effd151
parent3c6f9af85324b73acdba97c1867a2592e0ad4884 (diff)
clarify Quarto import plugin constraints, thanks to Bernelle
-rw-r--r--_pandoc.qmd10
1 files changed, 5 insertions, 5 deletions
diff --git a/_pandoc.qmd b/_pandoc.qmd
index 0d3c911..74dfea2 100644
--- a/_pandoc.qmd
+++ b/_pandoc.qmd
@@ -194,11 +194,11 @@ with the most commonly used Reader and Writer components.
This is exacerbated when using wrapper tools
since their extensions are likely tailored to those same
most commonly used Reader and Writer components.
-The Quarto framework, specifically,
-allows using any Reader same as Pandoc itself,
-but only when using default Reader --
-a custom derivative of the Pandoc default Markdown Reader --
-do you benefit from Quarto-specific macro expansions.
+The Quarto framework, like Pandoc,
+allows using any Reader.
+However, Quarto-specific macro expansions
+are only available when using the default Reader --
+a custom derivative of the Pandoc default Markdown Reader.
Despite the Reader API being specifically tailored
for implementing a custom source format parser,