Comments (4)
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.
from biblatex.
Ah, so I was just not looking in the right place in the manual. Thanks and sorry for the noise.
from biblatex.
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.
from biblatex.
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
- A
- B; C
- D; E
- 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
from biblatex.
Related Issues (20)
- How to transform newcomand \bcite{ref1,ref2} to \cite{ref1:TR,ref2:TR} HOT 2
- Localised url/urlfrom ignored as field format url hardcodes \mkbibacro{url} HOT 6
- `relatedtype`: `translationas` or `translatedas`? HOT 1
- Biblatex fails to detect languages loaded with `\babelprovide` HOT 9
- Feature request: revise_resubmit in pubstate HOT 1
- Change from pidgin-TeX to UTF-8 HOT 7
- Error in portuguese.lbx HOT 2
- improve tagging support if hyperref is not used HOT 11
- Inconsistent month capitalization in Italian with biblatex HOT 5
- `clearlang` is case sensitive
- Typo in finnish.lbx HOT 1
- Case of references in several subdivided bibliographies HOT 6
- Automatic capitalized for datatype=key fields HOT 4
- Create a few small LBX files HOT 10
- Possible bug introduced lately. HOT 8
- Help with the first small LBX -- vietnamese. HOT 1
- Problem with TL'24 HOT 5
- Errors with 'mergedate' option in per-entry scope HOT 1
- `\bbx@opt@mergedate@#1` macros
- hyphenation warning with language variants and polyglossia
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from biblatex.