Yong-Siang Shih
Yong-Siang Shih
Support `extension.WithFootnoteIDPrefix` (aka `footnoteAnchorPrefix` for Blackfriday) for `goldmark`
Yeah, it would be nice if this feature could be implemented now that blackfriday can no longer be used and therefore `footnoteAnchorPrefix` was also removed (gohugoio/hugoDocs#1704).
Support `extension.WithFootnoteIDPrefix` (aka `footnoteAnchorPrefix` for Blackfriday) for `goldmark`
> Any luck on this please? I've just met the footnote Id duplicating with multiple posts on one single page. @clsty Do you know if this problem is still present?...
Support `extension.WithFootnoteIDPrefix` (aka `footnoteAnchorPrefix` for Blackfriday) for `goldmark`
@jmooring In my case, I wanted to render the full content, including the footnotes, and allow the links to correctly link to the corresponding articles in the same list page....
Support `extension.WithFootnoteIDPrefix` (aka `footnoteAnchorPrefix` for Blackfriday) for `goldmark`
Wondering if it would make sense to create a new issue that directly describe the bug if the description of the current PR is too specific to one particular solution?
Support `extension.WithFootnoteIDPrefix` (aka `footnoteAnchorPrefix` for Blackfriday) for `goldmark`
Got it. To be specific, previously, with blackfriday, we could achieve example 1 with correct links to each article's footnotes in the list page.
Support `extension.WithFootnoteIDPrefix` (aka `footnoteAnchorPrefix` for Blackfriday) for `goldmark`
> Both examples have the same footnote number for each item on the list, which doesn't make any sense to me. I use hugo for blogs, and each article feels...
Support `extension.WithFootnoteIDPrefix` (aka `footnoteAnchorPrefix` for Blackfriday) for `goldmark`
> > previously, with blackfriday, we could achieve example 1 with correct links > > Out of curiosity, was this handled via a front matter field unique to each page,...
Support `extension.WithFootnoteIDPrefix` (aka `footnoteAnchorPrefix` for Blackfriday) for `goldmark`
I've updated the issue description to better reflect the situation.
It turns out the pipeline was not written by the authors, but it was created in https://github.com/Ahmednull/L2CS-Net/pull/18. So perhaps the PR author would know the answer.