Skip to content
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

Whether/when to mirror operators #233

Open
bert-github opened this issue Apr 9, 2024 · 4 comments
Open

Whether/when to mirror operators #233

bert-github opened this issue Apr 9, 2024 · 4 comments
Labels

Comments

@bert-github
Copy link
Contributor

(This is part of the I18n WG review.)

According to Arabic mathematical notation (the W3C Note from 2006), certain operators are mirrored in right-to-left formulas. But not all operators have mirrored versions in Unicode. For those operators, Firefox appears to make its own, while Chromium and Safari use the non-mirrored glyphs.

The MathML Core spec doesn't say which is correct, or if both are correct. It probably should.

(Firefox's rendering looks better, and more closely matches the Note, even if the naively mirrored glyphs are not quite as good as the redesigned glyphs that the Note calls for.)

@bert-github bert-github added the i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on. label Apr 9, 2024
@fred-wang
Copy link
Contributor

Firefox determines if the operator is mirrorable, based on https://unicode-org.github.io/icu-docs/apidoc/dev/icu4c/uchar_8h.html#a44a3508a5e40e78d3e767371c32bbc42 which corresponds to Bidi_Mirrored property.

Firefox can either do what's suggested in #67 (comment) or fallback to a scale transform for that purpose (this does not always work e.g. for clockwise integral).

@davidcarlisle
Copy link
Collaborator

@bkardell label as level-2 and postpone review of mirroring until after level-1?

@bkardell
Copy link
Collaborator

From the meeting today: This is a great point and we recognize the importance here, and even have some ideas about how it would move forward, but as @fred-wang and @davidcarlisle noted this was specifically moved to level 2 in order to focus efforts and iterate. We will take this up in level 2.

@bert-github
Copy link
Contributor Author

The i18n accepts that it can be postponed to level 2.

@bert-github bert-github removed the i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on. label Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants