Update 3 07FEB2020: When I replace Minion Math with Asana Math, it also doesn't compile! Seems like only certain fonts work, so it must be a siunitx or unicode-math issue...

Update 2 of 06FEB2020: It seems that this does compile but only when the \setmathfont is changed from Minion Math to e.g., XITS Math (thanks to Ulrike Fischer for inquiring about this), so the issue blocking this may be use of Minion Math even though it's installed system-wide.

Update 06FEB2020: Removed specific file path (installed font as admin) and replaced with Numbers feature since SizeFeatures actually works now by itself. The stylistic font features (Numbers, Contextuals, Style, Ligatures etc) also work by themselves (and together). But whenever I add a stylistic font feature and SizeFeatures, the issue occurs. Output log file in a gist here.

I use LuaLaTeX and whenever I compile the below (in Sublime) it says it works and no errors pop up, but it generates a broken won't generate a pdf file.


    \usepackage[math-style=ISO, bold-style=TeX]{unicode-math}
    Numbers={Lining, Proportional}, 
        {Size={0.1-8.5}, Font=*Caption.otf},
        {Size={8.6-11}, Font=*SmText.otf},
        {Size={11.1-14}, Font=*.otf},
        {Size={14.1-21.5}, Font=*Subhead.otf},




For some reason, when I take out either the SizeFeatures or the Numbers part of the above code the document compiles as intended. But the font is split into different files so these endings are necessary for the correct font to be used in different sizes, and I also want to use the different font features available, so I don't want to get rid of either SizeFeatures or the stylistic font features (Numbers, Contextuals, etc) if possible. Why is there a conflict between these microtype features and siunitx?

  • 2
    this can not be tested due to the local fonts. Are they need to show the problem? Feb 5, 2020 at 19:35
  • @UlrikeFischer If there is another example of a typeface that uses different fonts for different sizes and is publicly available (i.e., doesn't need this private path) I'd be more than happy to test it out myself. But from what I can see it's any font that uses SizeFeatures that has this issue.
    – airatin
    Feb 5, 2020 at 23:43
  • 1
    You should be able to demonstrate this with EB Garamond, but I get no error.
    – Thérèse
    Feb 6, 2020 at 0:55
  • What does "a broken pdf" mean? And is you tex system up-to-date? Feb 6, 2020 at 7:00
  • @Thérèse seems like the issue lies when I have both the SizeFeatures and a stylistic font feature (Numbers, Contextuals, etc) enabled. So I don't know if I can replicate this issue with EB Garamond since it doesn't have different SizeFeatures as far as I'm aware.
    – airatin
    Feb 6, 2020 at 12:53

1 Answer 1


Thanks to this answer from another question I managed to solve this problem just by changing the sisetup to the following:


Some fonts aren't set up for the default \mathrm to work, and apparently Minion Math (and Asana Math) when used in conjunction with Arno Pro is one of them.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .