3

I'm using Cochin as main font in a XeLaTeX project, and having Cochin glyphs for common ligatures such a fi and fl, I would expect those ligatures to be used by the fontspec package—but that's not happening.

\documentclass[border=1cm]{standalone}
\usepackage{fontspec}
\begin{document}

\fontspec[Ligatures=TeX]{Cochin}

Testing common ligatures: ``fi'' or ``fl''.

Explicitly pasted glyphs: ``fi'' (\texttt{U+FB01}) and ``fl'' (\texttt{U+FB02}).

\end{document}

enter image description here

  • Welcome to TeX SX! Cochin is a commercial font, and cannot be tested. – Bernard Mar 18 '16 at 22:33
  • It should be the same as Ligatures=TeX, but does using Mapping=tex-text instead have any effect? I don't own the font and cannot test. – Paul Gessler Mar 18 '16 at 22:51
  • The question is whether they are set up correctly in the font. If the tables are correctly configured, it should work. If not, I don't know if there's a way of working around it. Use of system fonts is beholden to the quality of the fonts installed in a way that use of traditional TeX fonts is not. (The latter are beholden instead to the quality of the support package installed or created.) – cfr Mar 18 '16 at 23:05
  • @Bernard - A minor detail, in the grand design of things: Cochin is a system font on MacOSX computer systems. – Mico Mar 18 '16 at 23:46
  • 1
    If you’re looking for a Cochin in which the ligatures work, I can say that ligatures do work in Linotype’s Cochin LT Pro. – Thérèse Mar 19 '16 at 0:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.