Struggling to find information on LaTeX sections -> Markdown directives #9449
dmca-glasgow
started this conversation in
General
Replies: 1 comment 3 replies
-
It wouldn't hurt for us to increase the length of the colons depending on nesting. (Our syntax doesn't require this, but it permits it.) So that's probably a decent change to consider, especially if it aids compatibility. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there, I'm new to Pandoc!
I'm struggling to find more information on how Pandoc converts LaTeX's
\begin{name} ... \end{name}
sections to Markdown "directives".I have the following LaTeX:
When running the command:
The resulting Markdown looks like this:
Which is almost ideal for my usecase, with one exception: my existing Markdown to HTML conversion tool uses micromark-extension-directive which has a different rule for nesting (search their readme for "nest" to see their example). Its syntax requires outer directives to increment preceding colons, for example:
I had a look at creating a Lua filter for this, but I'm struggling to find the right Pandoc term for this structure.
Also, I don't need to support the nesting logic at this stage, I think I can get away with a special case for
task
, for example:Any pointers? Thanks.
Beta Was this translation helpful? Give feedback.
All reactions