Sie sind hier

Startseite › forum › KOMA-Script › Fehlermeldungen › Erledigt

scrbook v3.26a breaks `refsection=chapter` option to biblatex

Do, 2019-01-17 23:56 — kwsm

Hello everyone

By passing refsection=chapter option to biblatex, \printbibliography prints bibliographies per chapter.
But, it no longer works after update to v3.26a.

\documentclass{scrbook}
\usepackage[backend=biber, refsection=chapter]{biblatex}
\begin{filecontents}{\jobname.bib}
  @misc{B1,
    title = {Bib1}
  }
  @misc{B2,
    title = {Bib2}
  }
\end{filecontents}
\addbibresource{\jobname.bib}
 
\begin{document}
\chapter{Ch1}
\nocite{B1}
\printbibliography
\chapter{Ch2}
\nocite{B2}
\printbibliography
\end{document}

Until v3.25, the above MWE works as expected, i.e. Bib1 in Ch. 1 and Bib2 in of Ch. 2, similarly as book.cls;
however, in case of v3.26a, Bib1 and Bib2 appear in Ch. 1 and Ch. 2.

forum: 
Erledigt
Fr, 2019-01-18 07:48 — Markus Kohm
Bild von Markus Kohm

It seems that biblatex is not able to increase its refsection counter. But I do not know how it works and why it does not longer work. I only found comments in the code of biblatex 3.12, that it has been changed to use new features of KOMA-Script.

I've added an issue to the biblatex bugtracker. I hope they can help to fix it.

Workaround: If you urgently need this, currently the only workaround would be to use exlicite \newrefsection commands or refsection environments. Sorry.

Fr, 2019-01-18 10:07 — kwsm

The version of biblatex is 2018/11/02 v3.12.

I you urgently need this, currently the only workaround would be to use exlicite \newrefsection commands or refsection environments.

Yes, I enclosed in refsection environments, but I'm afraid other packages that hooks \chapter are affected.

Oops, progress in GitHub.

Comments for "scrbook v3.26a breaks `refsection=chapter` option to biblatex" abonnieren

Der Inhalt dieser Seiten ist urheberrechtlich geschützt. Warenzeichen und sonstige Schutzmarken werden ausschließlich zu Zwecken der Information über selbige, sowie deren Rechteinhaber und den damit verbundenen Produkten verwendet. Siehe auch das Impressum mit der Erklärung zum Datenschutz.

Powered by Drupal