# Why do\textit and \emph suddenly not work anymore?

I use LaTeX, TeX Studio, LuaLaTex. Yesterday, the document compiled just fine. Although I have changed not a single line of code, \textit doesn't work anymore within the document-environment - neither if used on its own or as part of self-defined commands. It does work in the title, though. Can you help me?

\documentclass[12pt,a4paper,english]{scrartcl}
\usepackage{babel,ulem,libertine}
\usepackage{setspace}
\usepackage[firstinits]{biblatex-chicago}
\title{Outside/In: Pompey outside of Lucan's \textit{Bellum Civile} and Trimalchio in the \textit{Satyricon}}
\author{Patrick Kappacher}
\date{April 14, 2017}
\newcommand{\BC}{\textit{Bellum Civile}}
\newcommand{\Luc}{Lucan}
\newcommand{\Petr}{Petronius}
\newcommand{\Sat}{\textit{Satyricon}}
\newcommand{\HO}{handout}
\newcommand{\CT}{\textit{Cena Trimalchionis}}
\newcommand{\C}{\textit{Cena}}
\newcommand{\lib}{\textit{libertas}}
\newcommand{\umb}{\textit{umbra}}
\newcommand{\umbs}{\textit{umbrae}}
\newcommand{\nom}{\textit{nomen}}

\begin{document}
\maketitle
\nocite{*}
{\doublespacing

\BC~should be in Italics, but it isn't. \textit{Neither is this}.
\emph{Does not work either.}

}

\pagebreak
\printbibliography

\end{document}


• Welcome to TeX.Stackexchange! You have a { which does not have a closing. But otherwise you MWE works fine for me and I get italic text i.stack.imgur.com/MzuIV.png Can you add 1) a screenshot of your output from the above code? 2) the .log file? – samcarter_is_at_topanswers.xyz Mar 24 '17 at 15:36
• mine looks like this: pastebin.com/3vAcHJ0j – Patrick Kappacher Mar 24 '17 at 15:53
• I believe that the libertine package has been undergoing recent updates. You might check that by using some other font and seeing what happens. If that does it, then you can report a bug to the package maintainer. – Charles P. Schaum Mar 24 '17 at 16:08
• OK, so you have a newer luatex version the me. Unfortunately I can currently not update to test, but hopefully someone else with an up to date luatex may test this. – samcarter_is_at_topanswers.xyz Mar 24 '17 at 16:08
• Charles, you are right: Changing the font to the standard LaTeX-font solves the problem! – Patrick Kappacher Mar 24 '17 at 16:13