Currently TexVC creates a parsetrree without math and semantics elemntents.
Add these so native renderer interface can be used properly.
Remove the previous way of generating Math element with Utility function from the tests.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | Stegmujo | T310373 Make Mathoid Client a standalone class | |||
| Open | None | T327098 Implement Math Accessibility Features necessary for Intent attribute usage | |||
| Resolved | Physikerwelt | T302628 Implement native MathML rendering in Math | |||
| Resolved | Physikerwelt | T310211 Deliver visible MathML to the browser | |||
| Resolved | Stegmujo | T331047 Implicitly generate Math elements in MathML from the TexVC parsetree |
Event Timeline
Comment Actions
Change 893788 had a related patch set uploaded (by Physikerwelt; author: Physikerwelt):
[mediawiki/extensions/Math@master] Add minimal native MML mode
Comment Actions
and it uses the new rendering
To test the new rendering mode, one has to add the following line to LocalSettings
$wgMathValidModes[] = 'native';
thereafter one can select the native MathML mode
and it uses the new rendering
Comment Actions
When one adds https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Math/+/893818, one can see the current progress, for example, when looking at the Fourier transform page.
- Most formulae render fine 🙌
- Some contain a paragraph break sign
- Others throw an exception (we need https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Math/+/893818)
Comment Actions
The root cause of the Error is
Error: Call to undefined method MediaWiki\Extension\Math\TexVC\Nodes\DQ::getArg()
I suggest adding types to the respective methods so that phan can spot these errors. Moreover, I would rather avoid using function names as arguments, as this creates in particular several empty arguments.