I'm new to Harvard style. I've been trying to create a new LaTeX document for an article I'm writing. Unfortunately, I always get errors when compiling the file. The citations are not displayed, and the reference section doesn't show. At first, I thought I was doing something wrong when linking an external .bib file. Still, the error persists even when the reference is inside the document. Here's the MWE:
\documentclass[12pt,spanish,a4paper]{article}
\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}
\usepackage[spanish]{babel}
\usepackage{csquotes}
\usepackage{lipsum}
\begin{filecontents*}{refs.bib}
@inproceedings{Nielsen1994,
author = {Nielsen, Jakob},
booktitle = {Conference on Human Factors in Computing Systems - Proceedings},
doi = {10.1145/259963.260531},
pages = {413--414},
title = {{Usability Inspection Methods}},
volume = {1994-April},
year = {1994}
}
\end{filecontents*}
\usepackage[style=authoryear-ibid,backend=biber]{biblatex}
\addbibresource{refs.bib}
\begin{document}
\title{Article Title}
\author{Name Surname}
\maketitle
\lipsum[1]
\parencite{Nielsen1994}, \textcite{Nielsen1994}, and \cite{Nielsen1994}.
\printbibliography
\end{document}
The error I get is the following:
INFO - This is Biber 2.16
INFO - Logfile is 'harvard.blg'
INFO - Reading 'harvard.bcf'
INFO - Found 1 citekeys in bib section 0
INFO - Processing section 0
INFO - Looking for bibtex format file 'refs.bib' for section 0
INFO - LaTeX decoding ...
INFO - Found BibTeX data source 'refs.bib'
ERROR - BibTeX subsystem: /var/folders/sb/q38wrlkd7jl7mz_c99ktflmw0000gn/T/biber_tmp_tDMZ/8fe4c9854184545302f21ebf0d47516c_82448.utf8, line 11, syntax error: at end of input, expected end of entry ("}" or ")") (skipping to next "@")
INFO - ERRORS: 1
spanish
twice. In thedocumentclass
orbabel
is enough.sigfridsson
frombiblatex-examples.bib
(the file is installed on all systems withbiblatex
and will be found automatically: you don't have to create or download it)? Can you try deleting the Biber cache (tex.stackexchange.com/q/140814/35864). Biber 2.16 is slightly outdated, but not too much. Still, maybe you can update?