Tag Info

Hot answers tagged

5

In absolute terms utf8 does slow down the processing as (if you have any non ascii characters) you have to handle 2 (or more) bytes rather than 1, and it can not possibly take less time to process two bytes than 1 byte. But unless you have millions of non-ascii characters and your document does nothing but write them out to files and read them back in ...


2

The answer is in the comments, but since nobody wrote an complete answer, I will. Bibtex requires ascii encoding. If your document is set to utf8 encoding, bibtex will assume the bib file also is utf8. Therefore, you have to be sure your bib file is ascii encoded, and you have to tell bibtex to consider it as ascii. In your case, biblatex package should be ...


2

I don't know if this will solve all such issues, but simply adding \usepackage{marginfix} package solves the problem in your MWE at least. Sidenote: with some exceptions -- see Which packages should be loaded after hyperref instead of before? -- hyperref should be the last package in your preamble. \documentclass[a4paper,twoside]{scrbook} % packages ...


2

Just for an answer so the question can be closed. When the format dictates YYYY-MM-DD, then it is required (packing with zeros if needed) that the year is four digits, and month and day are two digits. Thus 1998-6-15 is the wrong format as the month is single digit. One might argue that it is redundant information when we have the dashes. But it is a lot ...


2

Systematic automated approach for finding the problematic entry It was suggested to eliminate half of the bibtex entries and this way reduce the number of suspects further. As I am lazy (and would not know how to do that in an easy way), I used the following semi-automatic method (all done in Terminal in MacOS X 10.6: created a copy of my .bib file in an ...


2

The screen output one gets from running Biber is almost always the same; the difference in whether one uses no option, --debug or even --trace is found in the .blg file. For a --tool run on a stand-alone .bib file, you will find the information in <file name>.blg, so biber --tool --debug lorem.bib gives a lorem.bib.blg with all the log output you ...


1

It seems that using backend=biber is causing the amazing slow down, I've asked a new focused question here to discuss this issue: Why does biber increase compilation time (pdflatex) dramatically? Performance comparison biber / bibtex8: Test setup my LaTeX document, limited to one long chapter by \includeonly, 98 pages with many many references, ...



Only top voted, non community-wiki answers of a minimum length are eligible