-
Notifications
You must be signed in to change notification settings - Fork 118
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
Undefined CS with entry sets #1
Comments
Which versiosn of everything are we talking about here? |
The dev branch (also available on SF) with biber 1.0. |
I have just committed an attempted fix to the dev branch - can you check? It's not clear if the addset* macros are really needed with biber, if I revert them to the original 1.7 definitions, the problem seems to be gone with biber. They now don't touch any data structures used when backend=biber. |
biblatex.sty in the dev branch doesn't have the changes needed for related entries. After adding those, I get a different error on the first latex run after biber:
|
Something strange is happening with git branches and merging I think. I have pulled everything and merged related into dev (nothing new to merge it says) and it's fine for me. The dev on github should have all the related entries stuff merged into it and should be completely up to date. That error suggests an earlier biblatex.sty without any of the printbibliography changes in there? Does your active biblatex.sty have: \let\sortlist\blx@bbl@slist ? |
Sorry - I must've been updating wrong. I pulled all of dev this time and built TDS. It now runs without errors, but the backends generate different output. biber gives: [1] Sheldon Glashow. "Partial Symmetries ofWeak Interactions". In: Nucl. Phys. bibtex gives: [1] Sheldon Glashow. "Partial Symmetries ofWeak Interactions". In: Nucl. Phys. In the manual I recall that PL states that citing an entry set does (in part) the equivalent of
So I think the bibtex output is more in line of what is expected. Not sure if this discrepancy is a big deal, though. |
I think that's because bibtex needs some extra fields to deal with sets (se pp. 121-122 of the 1.7 doc). If you add these and do latex-bibtex-latex-bibtex (manual says you will needs extra runs with sets and bibtex), then it looks like the biber version for me? |
I can't seem to replicate the biber output with bibtex. But biblatex 1.7 and bibtex/biber 0.9.9 is consistent with the output above, so I think you've fixed this issue. |
Try with this .bib, just \cite{set}. Run latex, bibtex, latex, bibtex, latex.
|
Ah, got it. Order matters - the set needs to appear in the bib file first. |
Yes, another of the reasons it would be nice to have a biblatex release with no bibtex support - the code is a bit hairy in the .sty and PL was really keen to clean it up and make a biber only release. |
The code did get quite a bit hairier with the new biber-only sorting features. Perhaps we can revisit this discussion with Joseph. |
Since years are always non-negative integers and their sign is stored in the era field, year comparison goes wrong if the years are the same but the era doesn't agree. Comp dates would give weird results with dateera = secular, alldates=comp, and say date = {-0054-06-07/0055-06-09}, Ideally \ifdateyearsequal{#1}{#2} should be used instead of \iffieldsequal{#1year}{#2year}
The solution with \lefthyphenmin would only work paragraph-initially (it seems even more complicated than that: https://tex.stackexchange.com/q/323930/35864). The solution from Peter Wilson's hyphenat/https://texfaq.org/FAQ-hyphoff works with a fake language without hyphenation patterns. The position within the paragraph is not relevant any more, but one shouldn't try to switch lanaguages withing \nohyphenation now and should probably only use it for short passages of text. But that seems fair given the only use case is preventing hyphenation in author names (\def\mkbibnamefamily#1{\textsc{\textnohyphenation{#1}}} in french.lbx).
Citing all of the entries in the documentation bib file generates undefined control sequence errors:
It looks like this is associated with biber and entry sets. Here's an example.
The text was updated successfully, but these errors were encountered: