W3C home > Mailing lists > Public > public-css-archive@w3.org > March 2019

Re: [csswg-drafts] [css-text] Add new CSS text-transform values for math (#3745)

From: Brian Kardell via GitHub <sysbot+gh@w3.org>
Date: Wed, 20 Mar 2019 13:37:22 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-474831608-1553089041-sysbot+gh@w3.org>
After discussing this with @fred-wang and @mrego, I think that we agree that we probably want the values list to be just 

none | [capitalize | uppercase | lowercase ] || full-width || full-size-kana | math-auto | math-bold | math-italic | math-bold-italic | math-double-struck | math-bold-fraktur | math-script | math-bold-script | math-fraktur | math-sans-serif | math-bold-sans-serif | math-sans-serif-italic | math-sans-serif-bold-italic | math-monospace | math-initial | math-tailed | math-looped | math-stretched

That's more in keeping with what is there today, it's one less character to type, and it doesn't get us into a whole host of other questions about why is it a function, what does the function produce and so on.  Ultimately this is really just a name that identifies the transform, I think, and unless we want to start tackling the thing at the end of section 2

> Note: A future level of CSS may introduce the ability to create custom mapping tables for less common text transforms, such as by an @text-transform rule similar to @counter-style from 

And try explaining these in terms of those then I don't think there is a need for more.  But, I also don't think that's necessary or maybe even desirable because of what/where this sits?

GitHub Notification of comment by bkardell
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3745#issuecomment-474831608 using your GitHub account
Received on Wednesday, 20 March 2019 13:37:24 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:26:58 UTC