-
Notifications
You must be signed in to change notification settings - Fork 1
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 inside Tables #22
Comments
Footnotes in Tables Behaving NormallyAn example of a footnote occurring in table cell but behaving like all other normal notes is note 72 in 26. THE HUGO ENGINE AND HOW IT WORKS. Since the cell containing the note is styled as |
Upcoming Solution in AsciidoctorI've come across the following Issue on the Asciidoctor project: When that will be implemented, the whole problem of footnotes inside table cells will be resolved — the new |
Footnotes ReferencesThis web page discusses in great detail footnotes and their usage: We ought to extract some correct terminology to be able to describe their use in the Styling Conventions document (i.e. avoid ambiguity when referring to note number that appears in the text body and that which appears next to note contents). |
a
-styled cells with newb
style. (See Introduce a new type of AsciiDoc table cell asciidoctor/asciidoctor#2352)When footnotes occur in tables, inside a cell styled as
a
(AsciiDoc), then the footnote will be created at the end of the cell. This happens because AsciiDoc cells are treated as embedded AsciiDoc documents.Although in some cases this might be acceptable, there are tables which contain multiple notes with the same text, which could be externalized as a single footnote — but this would look ugly because they'd appear as a single note pointing to another cell — unless that cell could be styled as
d
(default), which is fine if any of these cells doesn't require the AsciiDoc style.My main concern is having to deal with tables where some notes are placed at the bottom of the cell, while others at the bottom of the section (i.e. in HTML docs). I'd rather have a consistent style throughout the book.
The most significant example of this is Appendix H: CODE PATTERNS, which contains 11 footnotes, all inside table cells, 9 of them being also inside a code-block, and many of the being duplicate.
References
The text was updated successfully, but these errors were encountered: