New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In case of 'split' bibliographies, defernumbers=true is advised but details of references may be very hard to find #493
Comments
Yes, I think that warning was not really intended to be adequate to such circumstances. I have removed it in the dev version. |
Thanks! |
I'd like to revisit the question whether or not I know and agree that in the situation that sparked this discussion (also https://tex.stackexchange.com/q/332431/35864) On the other hand, here are some links to TeX.SX questions where
Given that
I think it would be extremely useful to reinstate the warning. I'm all for making it slightly more verbose and maybe even for providing a way to 'opt out' of receiving the warning if you have decided that |
None of these examples contain a global bibliography. I guess none of their authors would have complained if they would have added a global bibliography 😃: \documentclass{article}
\usepackage[sorting = ynt,bibstyle=numeric,defernumbers]{biblatex}
\usepackage{filecontents}
\begin{filecontents}{\jobname.bib}
@book{a,
author = "I",
year = "1973"
}
@book{a2,
author = "I",
year = "1923"
}
@book{b,
author = "You",
year = "1959"
}
\end{filecontents}
\addbibresource{\jobname.bib}
\DeclareBibliographyCategory{own}
\begin{document}
\nocite{a,a2}
\addtocategory{own}{a,a2}
\nocite{b}
\printbibliography[category=own,title={A}]
\printbibliography[notcategory=own,title={B}]
\printbibliography
\end{document} That's why I said:
Wouldn't it possible for |
Sure, adding a global bibliography turns the examples into the pathological case, where both settings give sub-par results, but I don't think we can reliably distinguish whether or not there is an additional global bibliography with the current machinery (the way split bibliographies are detected at the moment is very low-tech). I don't doubt that it would be possible in general, but I don't see a quick way and I don't think an investigation into this would be worth it, since this is just about a warning. We basically can only detect split bibliographies in general and decide to warn or not to warn. In my experience the vast majority of users who wants split bibliographies will not have an additional global bibliography. For those users the warning is helpful. I concede that I don't expect that many users will actually read the warning, but for those who do it can be useful (especially if we make it a bit more verbose). People with global bibliographies can choose to ignore the recommendation. I guess my reasoning is as follows.
I think point 2 and 1 together would already justify putting the warning back in, but point 3 puts additional mass on the "desirable" row in the table. |
OK but the current warning:
isn't unbiased :) Hence, it is not only annoying, it could be misleading. Si, if you change it for an unbiased one, why not? BTW, in all the TeX.SE issues you mention, the bibliographies are by categories, keywords or types. Wouldn't |
As I mentioned above, I'm all for making the warning more verbose, precise and useful. So if that's the only thing holding us back, I'm sure we can work something out.
In a way While the setup is usually so that you do not end up with an entry belonging to several bibliographies if you split by categories or keywords (unless you have a global bibliography), there is a real possibility that an entry may belong to several segments. When you split only by section the question of whether or not to use |
Okay. I am very curious to know what kind of warning you have in mind. |
Effectively reverts c7221bd
My suggestion is at moewew@0b4165a. Feedback is welcome. edit: hrmpf, there was a typo moewew@6966ea5. The effect of the two commits together can be seen in dev...moewew:warndefernum |
Well, I would say, still a bit biased ("pathological cases") 😄 but, okay, let's close this issue. |
|
A discussion about the following started on SE.
In case of 'split' bibliographies,
defernumbers=true
is advised but, as shown by the following MWE, details of references may in this case be very hard to find (for instance, just with your eyes, try to find details of reference e.g.[84]
cited in 2nd section).It appears that:
defernumbers=true
could be recommended,defernumbers=false
could be recommended.Hence I suggest to remove the warning:
in any case or, at least, in case of overlapping lists plus a global one.
MWE:
The text was updated successfully, but these errors were encountered: