- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 10 Sep 2020 19:44:29 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `math style`, and agreed to the following: * `RESOLVED: Add math-style: normal | compact` <details><summary>The full IRC log of that discussion</summary> <fantasai> Topic: math style<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/5387<br> <fantasai> NeilS: 2 ways of displaying math, one tries to minimize height to fit in lines better<br> <fantasai> NeilS: one is taller one<br> <fantasai> NeilS: shifts positions / sizing rules, etc.<br> <fantasai> NeilS: Designed so you don't have as much gap in lines if you have math in it<br> <fantasai> NeilS: rules defined in TeXBook<br> <fantasai> astearns: the switch is true or false for displaystyle?<br> <fantasai> astearns: I like normal and compact much better<br> <fantasai> iank_: Makes sense, but seems to also be able to affect the font size?<br> <fantasai> iank_: that will need to be carefully defined<br> <fantasai> NeilS: That effect is through the scriptlevel feature<br> <fantasai> fantasai: Affects the font size, indirectly through another property<br> <fantasai> iank_: Happy to add, pending scriptlevel discussion<br> <fantasai> astearns: ok, any concerns to add?<br> <fantasai> astearns: would it go into display module?<br> <fantasai> iank_: Goes into MathML Core<br> <fantasai> RESOLVED: Add math-style: normal | compact<br> <astearns> zakim, end meeting<br> <Zakim> As of this point the attendees have been dholbert, fantasai, faceless, bkardell_, emilio, NeilS<br> <Zakim> RRSAgent, please draft minutes<br> <RRSAgent> I have made the request to generate https://www.w3.org/2020/09/10-css-minutes.html Zakim<br> <Zakim> I am happy to have been of service, astearns; please remember to excuse RRSAgent. Goodbye<br> <bkardell_> hmm, I guess a few people didn't present+ in those minutes @fantasai @astearns - I see neither iank_ nor fredw<br> <iank_> :)<br> <gsnedders> plinss: https://drafts.csswg.org is claiming there are no specs in the repo!<br> <astearns> TabAtkins: maybe a bikeshed issue? I'm not seeing the generated spec in https://drafts.csswg.org/css-shapes-1/<br> <TabAtkins> it's a temporary server issue<br> <TabAtkins> lemme see...<br> <TabAtkins> hm, looks like server needs kicking<br> <TabAtkins> there's a single process running, but it's orange which I think means something bad, and it's not making progress<br> <TabAtkins> i just did a push to the repo, should hopefully kick off the regen process again? we'll see<br> <TabAtkins> yeah, things look fine now<br> <astearns> thanks!<br> <plinss> @tabatkins yeah, an orange process means it crashed (usually due to a db server issue), when that happens it blocks other processes (to make sure someone looks at it)<br> <plinss> most can be safely deleted, and the server will recover, but an 'UpdateDrafts.py' that has a '--pushId' arg should be manually re-run, so don't delete those, ping me.<br> <plinss> the 'no specs' error generally happens because a repo import crashed and left the db in a weird state, the next import will generally fix it<br> <plinss> (the db code is using transactions so that shouldn't happen, but still does sometimes, not sure why, maybe when the db hiccups it doesn't roll back transactions properly)<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5387#issuecomment-690677637 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 10 September 2020 19:44:34 UTC