On Sun, Oct 5, 2014 at 11:42 AM, Jürgen Spitzmüller <[email protected]> wrote:
> Am Sonntag 05 Oktober 2014, 10:49:47 schrieb stefano franchi: > > I have no idea what is going on. The only logical answer, in my mind, is > > that there are some cached results still lying somewhere. But where? > > I think biber is also caching things. > > That may be the case, as I have now solved the problem (but not found an explanation yet). So it turns out I had a bunch of auxiliary files related to the failing document in the document's own directory. But none related to its successful twin. (These files were left over from the command line compilations). Once I deleted those, compilation finally succeeded. I wonder why this happened though. Biber may have been responsible, even though it escapes me why it should read a file in the document's original directory when it is called on a file in a completely unrelated branch of the directory tree. There is a related thread on SX [1] that mentions issues arising with biber's cache. However, in my case, I didn't touch that cache (I didn't think of checking biber's behavior before erasing the files in the doc's own dir, unfortunately). So the problem is solved, yet the mystery remains. S. [1] http://tex.stackexchange.com/questions/140814/biblatex-biber-fails-with-a-strange-error-about-missing-recode-data-xml-file -- __________________________________________________ Stefano Franchi [email protected] <[email protected]> http://stefano.cleinias.org
