New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Finalise syntax #31
Comments
Other syntax from rST to consider: Substitution references, can be e.g. text, an image, a hyperlink, or (special) directive: |sub|
.. |sub| image:: myimage.png Footnote references (also citation references are similar): A footnote.[#1]_
.. [#1] A numerical footnote Also implemented in some flavours of Markdown (see Extended Syntax): Here's a simple footnote,[^1] and here's a longer one.[^bignote]
[^1]: This is the first footnote.
[^bignote]: Here's one with multiple paragraphs and code.
Indent paragraphs to include them in the footnote. (note its not technically compliant with CommonMark, as discussed here) |
Note to self; in the documentation, should also highlight the fact that MyST can do nested inline markup, which rST cannot, e.g. Here's a link with italic text. |
My 5c: I didn't see a good use for substitution references, aside of counteracting other rst limitations/annoyances. |
I'm "meh" on substitutions...it doesn't seem super useful to me given the added cognitive burden. Footnotes I think are worth implementing - I believe that Pandoc uses
syntax. Sometimes I also wonder if the same syntax style could be used for sidebar notes, like:
but that's for a different issue :-) |
It would be great to finalize the syntax for footnote references since we have a few test cases that use them. Another thing to consider regarding footnote references could be automatic enumerate numbering. |
re: |
@mmcky just a note that I've found that having markdown-style cell fences for directives has helped with this a bit. You have more control over the whitespacing etc which might make it easier to make these complex tables with directives |
I think this is pretty locked in now |
Agree that all the core syntax elements are present, and their format is acceptable
Related issues:
The text was updated successfully, but these errors were encountered: