3
A couple of tools combine to figure out what's going on. First string-functions.com, converts your Ansi strings to the seemingly identical μ and µ respectively (set the input encoding to ISO8859-1 and the output to UTF-8). Copy-pasting from your quoted source also works, but I wanted to start from the known-different characters. Pasting those two mus into ...
2
You need to issue \bibliography{<bibfile>} or \addbibresource{<bibfile>.bib} after you have loaded biblatex.
\bibliography{testa}
\usepackage[maxlevel=3]{csquotes}
\usepackage[backend=biber,citestyle=verbose-trad2,bibstyle=verbose-trad2]{biblatex}
will not work, but
\usepackage[maxlevel=3]{csquotes}
\usepackage[backend=biber, style=verbose-trad2]...
1
After a little bit of more investigation, I could reproduce the behaviour outside of lstlisting as well. This brought me to this question.
The answer is, that the font I'm using is missing these unicode characters, which is also shown in the extended log - but not shown as a warning when compiling, such as:
Missing character: There is no μ in font [lmroman10-...
1
There are some excellent answers already. Below are some steps that worked for me on macOS BigSur in March 2021 with TexLive 2020, with the intent of compiling with pdfLatex. It follows closely this 2016 step-by-step guide: https://theoryl1.wordpress.com/2016/01/15/fontawesome-in-pdftex/ and I am posting here for reference for my future self and hopefully ...
Only top voted, non community-wiki answers of a minimum length are eligible
