W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2020

Re: [csswg-drafts] [css-text] text-transform's design, intent and reality resolution (#3775)

From: Frédéric Wang via GitHub <sysbot+gh@w3.org>
Date: Fri, 03 Jul 2020 11:01:31 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-653489924-1593774089-sysbot+gh@w3.org>
>     * relying on these transforms to alter the meaning of the document, and to semantically distinguish between `a` and `<span style=text-tranform:math-fraktur>a</span>` is not robust.

This was included in the proposal as I thought it could help motivate the feature for people who for some reason are not interested in native math rendering support or even don't like MathML (but apparently, this had the opposite effect). For example, I believe MathJax or KaTeX generates something like `<span style=font-family: special-woff-font-for-fraktur>a</span>` for special rendering and to infer special semantic.

For native MathML implementation, this use case is not important at all, so I'm happy if the CSS spec say text-transform shouldn't be used for semantics.

>     * Markup is what needs to alter the semantics. The [spec of mathvariant attribute](https://www.w3.org/TR/MathML3/chapter3.html#presm.commatt) is already fairly clear about that, but it could be further clarified that it is expected to affect all renderings, including the accessibility tree and other non visual renderings.

For the record MathML3 is outdated, the reference for CSS-based browser implementation is

mathvariant: https://mathml-refresh.github.io/mathml-core/#the-mathvariant-attribute
text-transform proposal: https://mathml-refresh.github.io/mathml-core/#new-text-transform-values

Note that @bkardell plans to open new CSS issues for the proposals and relaunch the discussion soon, so hopefully we can move "CSS Extensions for Math Layout" to relevant CSS specs instead.

We could improve the MathML Core spec to clarify it is expected that the change for mathvariant affects non-visual renderings as you suggested. Actually we already had that in mind, but were waiting for a consensus on the present CSSWG issue.

GitHub Notification of comment by fred-wang
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3775#issuecomment-653489924 using your GitHub account
Received on Friday, 3 July 2020 11:01:33 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:11 UTC