You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you will see, HTML anchors are non-unique. For example, there are many footnotes which each have the anchor #id1. And several sections have the anchor #introduction. This means that is is not possible to create hyperlinks to particular sections of the document. And links to footnotes often point to the wrong place -- the browser takes you to a footnote with the same anchor in another section of the document.
We can work around the non-uniqueness of section anchors by manually specifying unique section IDs for each of our sections, but that does not help with the footnotes issue.
Since Sphinx is an extended Docutils and it can be further extended to change its build behavior. I suppose indexing for footnote, section, etc. are no different. So using tricks like below should enable to fix reported problems for singlehtml build by the document package ;-):
We use
make singlehtml
to produce single page HTML documentation from multiple input files.The output can be viewed here: https://www.debian.org/doc/debian-policy/
As you will see, HTML anchors are non-unique. For example, there are many footnotes which each have the anchor
#id1
. And several sections have the anchor#introduction
. This means that is is not possible to create hyperlinks to particular sections of the document. And links to footnotes often point to the wrong place -- the browser takes you to a footnote with the same anchor in another section of the document.We can work around the non-uniqueness of section anchors by manually specifying unique section IDs for each of our sections, but that does not help with the footnotes issue.
The source is here: https://salsa.debian.org/dbnpolicy/policy/tree/master/policy
Our bug reports: https://bugs.debian.org/879048 , https://bugs.debian.org/876075
Environment info
Thanks!
The text was updated successfully, but these errors were encountered: