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

Explain the mapping tables (appendix C) #234

Open
bert-github opened this issue Apr 9, 2024 · 1 comment
Open

Explain the mapping tables (appendix C) #234

bert-github opened this issue Apr 9, 2024 · 1 comment
Labels
i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.

Comments

@bert-github
Copy link
Contributor

(This is part of the I18n WG review.)

C. Mathematical Alphanumeric Symbols
https://www.w3.org/TR/mathml-core/#new-text-transform-mappings

The following tables enumerate the mathematical alphanumeric symbols with form bold, italic, fraktur, monospace, double-struck etc that are available in Unicode. For each of them, the character in its normal form is provided as well as the difference between the code points of the transformed and original characters.

The italic mapping table is used to implement the 'text-transform' property (section 4.2). The other mapping tables are not explained, but appear to implement various values of the mathvariant attribute (section 3.2.2) that are defined in MathML3, but not in MathML Core (‘bold’, ‘double-struck’, ‘fraktur’, etc.). Some browsers use them that way.

The spec suggests that those MathML3 values must be ignored. If that is the case, why are those tables in the spec? And if browsers are allowed to support those values, shouldn't the role of the tables be explained?

@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

Except for italic, this is mostly legacy and non-normative stuff from the original mathvariant / text-transform proposal.

This is not implemented in Chromium and is being tentatively removed from Firefox. I believe some legacy WPT tests still use it. Ultimately, we should remove them from MathML Core and probably only have them to web-developer-oriented doc.

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

No branches or pull requests

2 participants