ibid mechanism with multicite commands

[schtandard]

ibid mechanism with multicite commands

[moewew]

That's the result of the strict bit of ibidtracker=constrict,

strict Enable the tracker in strict mode. In this mode, potentially ambiguous
references are suppressed. A reference is considered ambiguous if
either the current citation (the one including the ‘ibidem’) or the
previous citation (the one the ‘ibidem’ refers to) consists of a list of
references.

Usually that makes sense, but if like in this case all citations in the list are to the same source, then I must admit the feature might be seen as going a little too far.

Consider

\documentclass{article}

\usepackage[style=verbose-ibid, ibidtracker=context]{biblatex}
\begin{filecontents}{\jobname.bib}
@Book{panbread,
  author = {Pan, Thomas},
  title = {The History of Bread},
  date = {1984},
}
@Book{cookwine,
  author = {Cook, Charles},
  title = {How I Single-handedly Invented Wine},
  date = {2003},
}
\end{filecontents}
\addbibresource{\jobname.bib}

\begin{document}

% Using \footcites:
Bread tastes nice.\footcite{panbread}
Bread as we know it today was invented in August~1927.\footcites[85]{panbread}[earlier variants of bread go back to the eighteenth century, cf.][177-183]{panbread}
The innovation of slicing it was made two decades later largely by accident.\footcite[207]{panbread}

% Cite something else to reset the ibid mechanism.
Did you know that wine was only invented in~2003?\footcite[1]{cookwine}

% Imitation using several \cite calls.
Bread tastes nice.\footcite{panbread}
Bread as we know it today was invented in August~1927.\footnote{\cite[85]{panbread}; \cite[earlier variants of bread go back to the eighteenth century, cf.][177-183]{panbread}}
The innovation of slicing it was made two decades later largely by accident.\footcite[207]{panbread}

\printbibliography

\end{document}

with the strict feature disabled.

[schtandard]

Ah, so I was just not looking in the right place in the manual. Thanks and sorry for the noise.

[moewew]

In this specific (and probably very rare) case an argument could be made that the strict check is excessive since the "ibid." is not ambiguous if all cites are to the same work. We could look into catching that case - not sure how difficult that it. But then again, I'm not sure if it would be a good idea to change this - maybe we'd need to implement a new almoststrict?

If you think this an investigation into this worth our while, you can reopen the issue.

[schtandard]

I'd say that's worthwhile, so I'll reopen. I'd go further and say that the only ambiguous case is when the last citation was in an earlier multicite command. That is, in a citation pattern like

1. A
2. B; C
3. D; E
4. F

the only places where an "ibid." would be ambiguous are D and F. While the logic is clear from the description in the manual, I still find it especially surprising that B is considered ambiguous in the default ibid styles.

The argument could be made that D is not ambiguous if B and C are the same source, but I think it's reasonable for this to be an edge-case that is not covered by the logic.

Name suggestion in case a new option is necessary: semistrict