You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following example fails if compiled with lualatex. It seems any font with a space in the name will trigger the problem, but only if the class is 'book-like'. So e.g. article is fine.
\documentclass{book}
\usepackage{polyglossia}
\setmainlanguage[variant=british]{english}
\setmainfont{Minion Pro}
\begin{document}
test
\end{document}
The example works if:
fontspec is loaded, but not polyglossia,
article is substituted for book,
default fonts are used,
XeTeX is used rather than LuaTeX,
a font without a space in the name such as Crimson is substituted for Minion Pro.
ref.: https://tex.stackexchange.com/q/730204/ [but there's some sort of fontconfig weirdness there, which isn't relevant to LuaTeX anyhow and XeTeX has no problem].
The log (attached) seems to show fontspec sets the family up correctly, but LaTeX ends up looking for MinionPro rather than Minion Pro. So some interaction with polyglossia causes the space to be lost.
No. I just didn't remember polyglossia changed the renderer until David Carlisle reminded me. I would have deleted this, but that doesn't seem to be possible. Apologies for the noise.
The following example fails if compiled with
lualatex
. It seems any font with a space in the name will trigger the problem, but only if the class is 'book-like'. So e.g.article
is fine.The example works if:
fontspec
is loaded, but notpolyglossia
,article
is substituted forbook
,Crimson
is substituted forMinion Pro
.ref.: https://tex.stackexchange.com/q/730204/ [but there's some sort of fontconfig weirdness there, which isn't relevant to LuaTeX anyhow and XeTeX has no problem].
The log (attached) seems to show
fontspec
sets the family up correctly, but LaTeX ends up looking forMinionPro
rather thanMinion Pro
. So some interaction withpolyglossia
causes the space to be lost.prawf-2.log
The text was updated successfully, but these errors were encountered: