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

[csswg-drafts] [Meta] MathML Core related CSS (wip as I create and link them) (#5384)

From: Brian Kardell via GitHub <sysbot+gh@w3.org>
Date: Mon, 03 Aug 2020 19:28:37 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-672292784-1596482916-sysbot+gh@w3.org>
bkardell has just created a new issue for https://github.com/w3c/csswg-drafts:

== [Meta] MathML Core related CSS (wip as I create and link them) ==
After quite a lot of work, the MathML-Core L1 spec, implementation work and discussions have yielded a real strong grip on how everything fits together, and it's gone through a TAG review.  Since this integration has a lot to do with CSS, we have several proposals for the CSSWG that explain and expose what we feel are the important aspects.  Some of these were brought last year, but here I'll make an effort to provide context, clarify and link them all up here in this meta issue so that readers can have and navigate a more  _complete_ picture, as this concerned some people before.... 

## Background to understand for these proposals

MathML, not unlike SVG, was created at a time where it was solving problems that would later be solved by CSS.  Similar to SVG, and HTML at the time - it chose to solve those problems via attributes. The types/values of these attributes were also kind of under-defined. A lot of the work in defining MathML-Core, just as it was for SVG, has been in aligning/mapping those to existing CSS and the larger platform.  Many of these attributes in MathML are in wide use and created by tools and editors today, and are already supported in existing browsers.  Because of this, you'll note that many of these proposals explain a mapping to something in CSS marked as presentational hints where appropriate and the specification strongly encourages use of corresponding CSS instead (for example `mathcolor` and `mathsize` involve no CSS proposals, they are just mappings). In some cases, existing CSS features are not adequate to mathmatical rendering needs, and these are the propsals MathML-Core has in terms of some additions to CSS that make it possible.  

For mathematical rendering, MathML-Core has defined the following necessary minimal values. While their form is pretty maleable, the specific powers they add are important in order to create compatability with widely used features.  Some of these are already used internally in implementations, but we have now well-defined them and would like to expose them to authors, increase their interopability and make them standard and well explained.  The proposals are outlined and rationales explained separately in simple terms, the spec itself contains many details with links in each. 

(all these links are temporary while WIP as I move them into proper issues) 

 * [2 new math oriented display values](https://gist.github.com/bkardell/bab94a45d57ff0ce27814944fe67666a) (inline/block versions)
 * [several new text transform values](https://gist.github.com/bkardell/851d35de699ff0e5e242f0362c9cec9d)
 * 2 new math properties: 
   * [math-style](https://gist.github.com/bkardell/8317c76db494bb80b37799d9f183d51b)  
   * [math-shift](https://gist.github.com/bkardell/7e9353fdcefa8004751ce4847e6c19a6)
 * a new [scriptlevel()](https://gist.github.com/bkardell/47cc456158c6e41efdceb658d2b37f3d) function for font-size value allowing management of mathematical 'scripted forms' (subscripts, superscripts, tensors, etc)


Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5384 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 3 August 2020 19:28:40 UTC

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