Skip to content

Be more explicit about how to get a largeop glyph #253

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
fred-wang opened this issue Aug 9, 2024 · 1 comment
Open

Be more explicit about how to get a largeop glyph #253

fred-wang opened this issue Aug 9, 2024 · 1 comment

Comments

@fred-wang
Copy link
Contributor

fred-wang commented Aug 9, 2024

From https://w3c.github.io/mathml-core/#layout-of-operators

If the operator has the largeop property and if math-style on the element is normal, then:
Use the MathVariants table to try and find a glyph of height at least DisplayOperatorMinHeight. If none is found, fall back to the largest non-base glyph. If none is found, fall back to the layout algorithm of 3.2.1.1 Layout of .

There is a separate issue #126 about how to actually interpret DisplayOperatorMinHeight, and it seems the conclusion is that MathML Core is correct but Cambria Math font is not.

But even without that, "use the MathVariants table" is vague. First the base glyph is obtained from the "single character c". Then I'm not sure, maybe we can just shape the base glyph to block dimension DisplayOperatorMinHeight which seems to be what Chromium does or maybe we need to introduce a similar "find a display operator glyph" algorithm if it needs to be different.

@fred-wang
Copy link
Contributor Author

I think @icesfont is fixing that as a part of its RTL PR #277

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant