2

Chaparral.tex:

\documentclass{article}
\usepackage[english]{babel}
\usepackage{fontspec}
\setmainfont{Chaparral Pro}
\begin{document}

Hamburgefonstiv Regular

\textbf{Hamburgefonstiv Bold}

\end{document}

Chaparral.log: http://pastebin.com/wNKG07h0

Result:

Result

Adobe [Caslon/Garamond Premier/Minion/Myriad] Pro come out correctly with equivalent syntax. The .otfs are all present in C:\Windows\Fonts. All came with CS3. LuaTeX beta-0.76.0-2013061707 (rev 4627).

Is this a bug I should report to http://tracker.luatex.org/, or is it an issue with Chaparral, or is it working correctly in a way I don't understand?

Edit: Nevermind. I just found http://tracker.luatex.org/view.php?id=572

closed as off-topic by Torbjørn T., Mensch, cmhughes, Werner, jub0bs Oct 5 '13 at 23:53

  • This question does not fall within the scope of TeX, LaTeX or related typesetting systems as defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.

  • What happens if you are more explicit? E.g.: \setmainfont[UprightFont = ChaparralPro-Regular.otf, BoldFont = ChaparralPro-Bold.otf]{Chaparral Pro}. (Note: I don't have the fonts and I don't use Windows; but your .log clearly shows that it can find these files....) – jon Sep 24 '13 at 3:17
  • It does work if I'm more explicit. Even the name "Chaparral Pro Regular" is interpreted correctly, but naming the files works as well. – Nils Enevoldsen Sep 24 '13 at 4:03
  • 4
    This question appears to be off-topic because it is about a (reported) bug in LuaTeX. – Torbjørn T. Oct 5 '13 at 23:05