How can I fix this polyglossia/fontscpec conflict?

Question

Here's my MWE, it appears replacing MedeivalSharpwith any TTF file will do the trick.

\documentclass{article}
\usepackage[T1]{fontenc} 
\usepackage{fontspec}
\usepackage[osf,proportional]{Baskervaldx}
\usepackage{polyglossia}

\newfontfamily\msharp[
Path = {/home/kristian/.fonts/},
Extension = .ttf
]
{MedievalSharp}
\begin{document}

{\msharp{This is Medieval Sharp.}}

But this is not Baskerville.

\end{document}

Don't use the Baskervaldx package with xetex, its encoding is not suitable for this engine. — Ulrike Fischer, Jan 14 '20 at 18:00
XeTeX does not use T1, don't load fontenc. Also, as @UlrikeFischer mentioned, don't load Baskervaldx. Use \setmainfont from fontspec. — Oleg Lobachev, Jan 14 '20 at 18:46
@UlrikeFischer, you are right. Now I must find something as good as Baskervaldx.
Oleg Lobachev -- Duly noted, thanks. — Kristian Nordestgaard, Jan 14 '20 at 19:10

score 0 · Accepted Answer · answered Jan 14 '20 at 19:43

0

It seems I figured out a solution thanks to the comments above:

\documentclass{article}
\usepackage{polyglossia}

\usepackage{fontspec}
\defaultfontfeatures{Ligatures={NoRequired}}

\setmainfont[
Ligatures = TeX,
Path = /home/kristian/.fonts/,
BoldFont = Baskervaldx-Bol.otf,
ItalicFont = Baskervaldx-Ita.otf,
BoldItalicFont  = Baskervaldx-BolIta.otf]
{Baskervaldx-Reg.otf}

\newfontfamily\msharp[
Path = {/home/kristian/.fonts/},
Extension = .ttf
]
{MedievalSharp}

\begin{document}
{\msharp{This is Medieval Sharp.}}

And this is \textsc{Baskerville}. 12345. \textit{test} -- \textbf{test}
\end{document}

I added \defaultfontfeatures{Ligatures={NoRequired}} to get rid of the strange (OE, AE) ligatures.

answered Jan 14 '20 at 19:43

Kristian Nordestgaard

1,755

Do you mean in words like Cæsar, œuvre, Phœbe, æther, ælf, Bignoniaceæ? It is strange seeing them typeset without the ligatures, unless there are technical limitations like typewriters. They do activate the spell-checkers, though, and usage is beginning to fade. – Cicada Oct 11 '20 at 05:18
@Cicada See https://tex.stackexchange.com/a/404970/ But this fix is no longer needed: someone seems to have removed the rlig feature from the version of the fonts in TeX Live. – Thérèse Oct 11 '20 at 12:22
You may be interested in Baskervville and Open Baskerville. – Thérèse Oct 11 '20 at 12:35

How can I fix this polyglossia/fontscpec conflict?

1 Answers1