- From: Frédéric Wang <fwang@igalia.com>
- Date: Mon, 11 May 2020 09:21:56 +0200
- To: public-mathml4@w3.org
- Message-ID: <e45cbaaa-4316-73c3-2ea9-f0ddd88d3083@igalia.com>
On 11/05/2020 06:51, Neil Soiffer wrote: > Meeting is at 11am Pacific, 2pm Eastern, 8pm Central European Time. > > Apologies for the late notice, but Frédéric has been busy the last few > days and has raised a number of issues that we should resolve if > possible. The agenda is > at https://github.com/mathml-refresh/mathml/issues/8#issuecomment-626466388. > > The zoom meeting link is the same one we have used at the last few > core meetings. Due to zoombombing, I can't send it out to the public > mailing list. If you would like to join and don't have the link, > please send me email at least 10 minutes before the meeting. > > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > Virus-free. www.avg.com > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > > Note that there are more "should we really include these MathML3 features in Core?" in the list (the spec mentions ISSUEs for mglyph, mlabeletr, compex mpadded syntax or fence/separator). I don't think it's really useful to keep discussing them for now given that 1) There is no plan from implementers to have these in all browsers anyway. 2) The polyfill situation is still unclear so people will keep using the same arguments to try and include MathML3 features to MathML Core. So I'm not interested at all in wasting time on this. As I said, the biggest priority right now is updating the operator dictionary to allow a compact form. I sent pull requests last Thursday that are pending: https://github.com/mathml-refresh/xml-entities/pulls We can go over these PR and discuss each item but it would be much better if people check them before the meeting so that we don't have to postpone this again and again. -- Frédéric Wang
Received on Monday, 11 May 2020 07:22:27 UTC