- From: Daniel Marques <dani@wiris.com>
- Date: Thu, 15 Feb 2018 10:31:23 -0800
- To: "public-mathonw." <public-mathonwebpages@w3.org>
- Message-ID: <CAFGc8v1N3EDZWPDT2L_XM9fyK+_jHgGyWA8wk8oRRs9fOFd7Ew@mail.gmail.com>
Hi everybody, I'm talking about ePub but the ideas are still valid for HTM: 1. It is up to the publisher to use MathML in their internal workflow. A "source" ePub could have MathML (or LaTeX). Why not? 2. Publish ePub with HTML-css-webfonts and svg only (because MathML is not ready and might never be). 3. Find a solution for accessibility and interoperability. There is work here to be done. Here is where the compromises and common solutions have to be taken, not at point 2. Other considerations 1. Publishers should be free to use JavaScript if they thing is a solution or wants to use LaTeX or MathML inside the published ePub. As comparison, is there anything that forbids the creation of <table>'s using JavaScript inside an ePub? 2. Please, do not create a new standard because it will have the same faults as MathML. 3. Again, a publisher should feel free to use Web Components for representing mathematics. 4. Let MathML be as it is right now. Dani -- ------------------------------ WIRIS and Design Science, makers of MathType, have joined forces! Thank you for your patience as we transition from dessci.com to wiris.com.
Received on Thursday, 15 February 2018 18:31:49 UTC