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
I am working with documents and Islamic commentaries. My goal is to preserve the original footnote numbers or labels so they can be searched and found by the users and so users can also cite the original footnote when needed. So I need to preserve the original footnote.
There are two issues:
For larger works, like books and commentaries, the original text is broken into multiple sections (which can be hundreds or even thousands for multi-volume works) and each section will be stored in its own markdown.
Some works have footnotes that use non-numeric labels. For example, this Quran commentary book (e.g. page 112) uses letters a, b etc. for footnotes.
Based on that, it looks like footnotes need a feature where Footnote.Label can be used in the markup instead of the Footnote.Order property.
Then, based on an option provided, HtmlFootnoteGroupRenderer will either use Order or Label (without the ^ prefix).
If this proposal seems acceptable, I can try to make a pull request (not sure though what the time frame might look like).
I am working with documents and Islamic commentaries. My goal is to preserve the original footnote numbers or labels so they can be searched and found by the users and so users can also cite the original footnote when needed. So I need to preserve the original footnote.
There are two issues:
Based on that, it looks like footnotes need a feature where
Footnote.Label
can be used in the markup instead of theFootnote.Order
property.Then, based on an option provided,
HtmlFootnoteGroupRenderer
will either useOrder
orLabel
(without the ^ prefix).If this proposal seems acceptable, I can try to make a pull request (not sure though what the time frame might look like).
Comments/suggestions/feedback welcome.
I looked at this list of issues and didn't find a similar issue.
The text was updated successfully, but these errors were encountered: