Created
June 8, 2018 14:37
-
-
Save gusbrs/764ca695adecf33ec5d8e8b0c4a68c19 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
\documentclass{article} | |
\usepackage{biblatex} | |
\addbibresource{biblatex-examples.bib} | |
\begin{document} | |
\nocite{*} | |
\printbibliography | |
Resulting in a file .bcf file: \verb|file_name_with_spaces.bcf| | |
When biber is run: | |
\begin{verbatim} | |
Running `Biber' on `file name with spaces' with ``biber file\ name\ with\ spaces'' | |
INFO - This is Biber 2.11 | |
INFO - Logfile is 'file name with spaces.blg' | |
ERROR - Cannot find control file 'file name with spaces.bcf'! - Did latex run successfully on your .tex file before you ran biber? | |
INFO - ERRORS: 1 | |
\end{verbatim} | |
Most editors I know will assume the names of the auxiliary files (.bcf among them) | |
from the name of the .tex file. Of course, we could run biber on | |
\verb|file_name_with_spaces|, but that would seriously hinder the workflow | |
usually assumed by the editors. Notice this example does not produce a | |
bibliography (I think, because the .bbl file is also not found). | |
\end{document} | |
%%% Local Variables: | |
%%% mode: latex | |
%%% TeX-master: t | |
%%% End: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment