- =Verbatim text= as link description.
- ~200B ZERO WIDTH SPACE~ workaround does not work here.
- It causes issues with pretty quotes in link description even with
#+OPTIONS: ':nil
(info “(org) Export Settings”). With partial verbatim text: (info"(org) Export Settings"
) - An attempt with Special Symbols aka "entities" (
\quot{}
): (info "(org) Export Settings") - To use footnotes1
- Explicitly enable the feature
#+OPTIONS: f:t
- Use separate definitions in the section named “Footnotes”
(or its localized variant, no colon after the name)
for compatibility with
ox-html
.Reference[fn:1] ** Footnotes [fn:1] Text of footnote.
- Labels are used literally, so it is your responsibility to renumber them and perhaps avoid meaningful names if you are going to get numbers in the exported document.
- Avoid anonymous footnotes
Defined as [fn:: Text of anonymous footnote]
They are not supported
- If you have multiple headings then avoid inline footnotes
otherwise they appear in every following section.
Inline[fn:2: Footnote text]
- Explicitly enable the feature
- Link to internal target see [[https://github.com/wallyqs/org-ruby/issues/11][Support cross-references (wallyqs/
org-ruby)]]. Notice that GitHub URL breaks Org markup.
- <<internal-target>>Target for an internal link
- Inline code block src_elisp{(server-start)}
- Export snippets for HTML level markup works, but with custom export backend @@c: e.g. for inline comments@@ they are exported literally.
- Macro {{{comment(another attempt of inline comment)}}}
#+begin_center
is ignored for this paragrapth
#+caption: Org mode logo
is ignored for the image above.
Test of multiple header levels.
Text of heading level 3.
Text of heading level 4.
Text of heading level 5.
Text of heading level 6.
Header level 7Text of heading level 7.
1 Separate footnote text