Interpretation of DisplayOperatorMinHeight parameter from the MATH table


As discussed in a previous meeting the DisplayOperatorMinHeight does not 
seem enough to get the proper size of large operators in display style. 
At least WebKit, Gecko and XeTeX implementations had to perform 
heuristics to work around issues with existing math fonts. In the past, 
something similar was in the MathML Core specification but was removed 
until we get clarification from Microsoft about the correct way to 
interpret DisplayOperatorMinHeight.

Now that MathML is shipped in Chrome, Edge, Opera, etc (all of them 
implementing DisplayOperatorMinHeight as per current version of MathML 
Core, without extra heuristics) this known issue showed up again, even 
with Microsoft's own Cambria Math font:

Two weeks ago I tried to summarize the status and observation on the 
dedicated spec issue:

I'd really appreciate feedback from Microsoft on this, so we can 
progress on the spec issue and decide how to fix the chromium bug!


PS: As a completely unrelated issue, 
has also remained unanswered for a while.

Frédéric Wang

Received on Friday, 24 February 2023 09:06:18 UTC