-
Notifications
You must be signed in to change notification settings - Fork 188
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
Footnotes don't appear #30
Comments
Footnotes are not implemented in the reveal.js backend. But before we add them, we need to make a design decision. Where should the footnotes appear? Should they appear at the bottom of the slide from which they come? Should they appear on a references slide at the end of the presentation? It is possible to check for new footnotes at the bottom of a slide and add them. The API is a little clunky, but I believe the necessary information is there. |
Good questions / points. I assumed "footnote" would mean "bottom of slide", given that it normally means "bottom of page", but that is a design assumption... |
Let's start with the bottom of the slide. |
I'll add my vote to putting them on the bottom of the slide. For now, I'm just hyperlinking to references. |
Another option to consider: https://github.com/e-gor/Reveal.js-Title-Footer |
With Asciidoctor PDF 1.5.0.beta.1 using Asciidoctor 2.0.10, it goes to the last slide. Why not distinguishing:
|
This would be great to have! I tend to put references to other papers/works at the bottom of slides using footnotes. |
I'll explore this for the next release |
I agree if the footnotes go on the slide, the numbering should be reset (if possible). Being able to put the footnotes on the final slide is an interesting idea. It would match the presentation pattern of putting credits on the last slide. So I think it would be worthwhile to explore. |
Footnotes do not seem to appear:
The text of the footnote doesn't seem to show up in the HTML:
There's more HTML than that, of course, but nothing with the footnote text in it.
The text was updated successfully, but these errors were encountered: