-
Notifications
You must be signed in to change notification settings - Fork 14
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
review operators stretching along the inline axis #102
Comments
Hmm unicode.xml has an operator dictionary entry for that saying it's stretchy but it doesn't distinguish horizontal or vertical stretch, and the unicode MathClass-15.txt doesn't help either. Probably I should extend the schema used by unicode.xml to allow h/v stretch distinction then we just have to print off the list of characters and decide in each case (or could we get a useful list out of the Opentype tables in say Stix two math rather than doing this by eye? |
yes, probably we could include in unicode.xml The idea is that there is not a lot of horizontal-only characters so it should not be that big to check. We can also rely on STIX Two by checking the horiz/vert contructions in the MATH.MathVariant table ; note however, that MATH fonts use combining code point for accents. I suspect the original list was generated from the "direction:vertical" or "direction:horizontal" of https://searchfox.org/mozilla-central/source/layout/mathml/mathfont.properties |
I added more code points, but that doubled the size of the table! https://w3c.github.io/mathml-core/#stretchy-operator-axis Stretch axis of some operators is not clear for some code point e.g. Compare with this one, which is not stretchy: I'm considering an alternative approach here: |
It seems I like #106 resolved this. @fred-wang can you confirm this is resolved and close the issue if it is resolved? |
I guess this is solved. |
See https://w3c.github.io/mathml-core/#stretchy-operator-axis
For example ⥦ U+2966 LEFTWARDS HARPOON WITH BARB UP ABOVE RIGHTWARDS HARPOON WITH BARB UP is missing but I'm sure many more are.
The text was updated successfully, but these errors were encountered: