Open dcpurton opened 5 years ago
I'm generally fine with adding internals to allow more tracking of just about anything as they tend to be useful. @moewew - what do you think?
This sounds like a niche feature, but a useful one nonetheless. I'm all for implementing it and would even want to go a bit further and add a similar function for all cite trackers. I'll see if that is possible without too many disturbances to the internals.
I looked at making all trackers available as ...entry
versions yesterday and hit a few issues.
context
version of the trackers uses \blx@ifcitesingle
, which might not be available or might not apply to the correct/useful entry in the context we call the ...entry
tracker macro.idemtracker
don't rely on the entry key, they need other field info, which might be harder to come by (we need \entrydata
or similar ...).loccit
tracker might also take into account postnote data, so this would need to be dealt with as well (probably by having the user supply the postnote as an additional argument).
biblatex
has\ifciteseen
and\ifentryseen{<entrykey>}
, but it only has\blx@citetracker
for adding the current entry to the list of cited entries.I am playing around with an entry type in
biblatex-sbl
where being able to explicitly add an entry to the list of cited entries would be useful.Would there be a willingness to add a
\blx@entrytracker{<entrykey>}
feature?\blx@citetracker
could call this with the current entry as the argument in much the same way as\ifciteseen
and\ifentryseen
ultimately end up in the same place.Here's a possible implementation: