- Footnotes separator rather than headline to get around i18n - Warn on footnote redefinition - Do not export footnote definitions at point of definition, only in the footnote section. - Do not automatically exclude Footnotes section to get around possibly hiding other content of such a section - and i18n. The user has the choice of explicitly hiding the section via a :noexport: tag. and some other refactoring
1.7 KiB
1.7 KiB
Using some footnotes
- normal footnote reference 1 2
- further references to the same footnote should not 1 render duplicates in the footnote list
- inline footnotes are also supported via 3.
- Footnote definitions are not printed where they appear. Rather, they are gathered and exported at the end of the document in the footnote section. 4
Footnotes
1
- footnotes can contain markup
-
and other elements
-
like blocks
other non-plain
-
and tables
1 a 2 b 3 c
-
2
Footnotes break after two consecutive empty lines - just like paragraphs - see https://orgmode.org/worg/dev/org-syntax.html. This shouldn't happen when the definition line and the line after that are empty.
3
the inline footnote definition
4
so this definition will not be at the end of this section in the exported document. Rather, it will be somewhere down below in the footnotes section.
5
There's multiple reasons for that. Among others, doing so requires i18n (to recognize the section) and silently hides content before and after the footnotes.