Replies: 3 comments 4 replies
-
I don't see that as an issue but as a requirement. Same as you need Regarding the representation, I wonder if we need to be this explicit (maybe it is a aim for Pandoc) or if we could be more implicit to be simpler. For example, something ::: {#fig-id}
![image caption](foo.png "Title of figure"){alt = "alt text}
Figure environment caption
::: would be
This is more implicit and I see how being more explicit can be good too ::: {#anyid .figure}
![image caption](foo.png "Title of figure"){alt = "alt text}
:::: {.caption}
Figure environment caption
::::
::: I am just wondering: is there any use case where we could need to create a div of class figure in HTML5 for example ? <div class = "figure>
content
</div>
because if
creates what is described in #24 (comment) <figure>
</figure> There would be now more markdown syntax to generate the former. Maybe it is be twisted but I am just sharing my thoughts 😅 Overall, I like the use of Fenced Divs for this ! |
Beta Was this translation helpful? Give feedback.
-
As discussed, this was implemented as a Lua filter. |
Beta Was this translation helpful? Give feedback.
-
Now the |
Beta Was this translation helpful? Give feedback.
-
Hi, I'm starting to work on the code for the markdown reader.
I'm tentatively aiming for this representation:
That should produce:
There is the issue that fenced divs are only parsed when
Ext_fenced_divs
is enabled.Impementation
Explicit notation
As discussed below this was implemented using a Lua filter
md-figure-explicit.lua
:Example run:
Input
Output
Implicit notation
Input
Output
Sample Firefox's HTML rendering
For the implicit syntax example.
Beta Was this translation helpful? Give feedback.
All reactions