# Problem with latest BibLaTeX release? [duplicate]

The bib file from my biblatex-abnt style won't compile properly since I updated BibLaTeX to the latest version.

ABNT's rules are terrible and very inconsistent, so I do a lot of weird stuff in that file to try to replicate them.

Here's one example that doesn't work anymore:

\documentclass{article}

\usepackage{filecontents}
\begin{filecontents}{\jobname.bib}
@book{alves1995,
author    = {Roque {\relax de\nopunct} Brito Alves},
title     = {Ciência criminal},
location  = {Rio de Janeiro},
publisher = {Forense},
date      = {1995},
}
\end{filecontents}

\usepackage{biblatex}

\begin{document}
\nocite{*}
\printbibliography
\end{document}


I can work around this particular example in other ways, but there are others, and I'm not sure what they have in common. Maybe the use of groups within entries? But sometimes that works. I don't know...

Also maybe the problem is related to this one somehow?

• This has nothing to do with tex.stackexchange.com/q/431932/35864, it is the same problem as tex.stackexchange.com/q/425947/35864 and the linked issues. While the issue in the second question linked will be gone in Biber 2.12 I think that your issue will not be resolved, you'll have to find a different way to get the output you want. – moewe May 16 '18 at 21:54
• @moewe Ah! Ok then. I can work around this case already. Another example I was having trouble with was using \mkbibacro within extra braces in the author field; I assume that’ll be fixed along with italics (from the question you linked)? If there are other cases I’ll ask more specific questions then. Thank you! – dbmrq May 16 '18 at 22:06
• In that case an answer that shows the work-around may help future visitors. The general rule with Biber is to avoid braces and macros in name fields as far as possible. Because Biber needs to convert macros to UTF-8 characters for sorting, things can go wrong if braces and macros are used for different purposes. – moewe May 16 '18 at 22:15
• @moewe Alright, I'm still working on it, but I'll post an answer here soon. Thanks again. :) – dbmrq May 16 '18 at 22:42
• Did you find an answer? If so would you mind writing it up for benefit of other people with a similar problem? – moewe May 28 '18 at 16:01