3

EDIT: The problem seems to be solved now. (I've had a test with version 2019.02.14 16:57)


I am having a rather strange problem using Minion Pro with ConTeXt. The following example breaks at {\em Gesammelte Schriften}. There are some lines that I can comment out in order to make the example run, but obviously I really should define the main language. Using the same example with other fonts works just fine. (Note that the font feature definitions were copied from pandoc's context template.)

\mainlanguage[de] % comment this line out and it should work with Minion Pro as well

\definefontfeature[default][default][script=latn, protrusion=quality, expansion=quality, itlc=yes, textitalics=yes, onum=yes, pnum=yes] % comment this line out and it should work with Minion Pro as well
\definefontfeature[smallcaps][script=latn, protrusion=quality, expansion=quality, smcp=yes, onum=yes, pnum=yes]
\setupalign[hz,hanging]
\setupitaliccorrection[global, always] % comment this line out and it should work with Minion Pro as well

%\definefontfamily[mainface][rm][Linux Libertine O] % works
%\definefontfamily[mainface][rm][Adobe Garamond Pro] % works
\definefontfamily[mainface][rm][Minion Pro] % breaks at {\em Gesammelte Schriften}

\setupbodyfontenvironment[default][em=italic] % use italic as em, not slanted
\setupbodyfont[mainface,11pt]

\starttext

Adorno, Theodor {\em Gesammelte Schriften}, % comment this line out and it should work with Minion Pro as well

Adorno, Theodor {\em Werke},

Ernst Bloch {\em Werkausgabe},

Karl Marx und Friedrich Engels {\em Werke}

Friedrich Nietzsche {\em Kritische Studienausgabe}
\stoptext

closed as off-topic by Henri Menke, Mensch, Raaja, Stefan Pinnow, user121799 Feb 13 at 6:05

  • 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.

  • 2
    works fine for me. What do you mean by breaking? – Ulrike Fischer Dec 30 '18 at 22:17
  • Compilation stops after the problematic line. Error messages: "Tex error" and "attempt to compare number with nil". – Denis Dec 30 '18 at 22:24
  • 4
    I tried with a current context standalone. I would recommend that you use that too - context develops rather fast, and the texlive version is quite outdated. – Ulrike Fischer Dec 30 '18 at 22:29
  • 1
    Hm, I can actually reproduce. Here is a slightly more minimal example termbin.com/9m1s7 – Henri Menke Dec 31 '18 at 0:18
  • 4
    I'm voting to close this question as off-topic because this seems to be fixed in the latest beta. – Henri Menke Feb 13 at 3:52

Browse other questions tagged or ask your own question.