Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

observations on Stylesheets/docx/from/omml2mml.xsl #711

Open
Gertone opened this issue Nov 7, 2024 · 0 comments
Open

observations on Stylesheets/docx/from/omml2mml.xsl #711

Gertone opened this issue Nov 7, 2024 · 0 comments

Comments

@Gertone
Copy link

Gertone commented Nov 7, 2024

Using this stylesheet I have some observations.

I mainly picked this one since it already is an XSLT3 variant of the XSLT1 stylesheet Microsoft delivers with MS Office.
I wanted to leave the actual stylesheet intact, so I can use future versions in my project. For that I have it embedded in an XProc pipeline and decided to do some postfixing on the MathML coming out of this XSLT after.

That worked for some issues I found

  • mfenced is generated, but not supported in browsers, I patch that by adding brackets, accolades, pipes as operator (mo) in the post-process
  • all variants of the minus operator are replaced by a short hyphen. Again I can patch that in the post process

However I noticed that for an mml n-ary (m:nary), MS Word occasionally uses an m:grow/@m:val = 1 to indicate munderover instead of msubsup. The stylesheet has no support for m:grow. This I can not fix in a postprocess

As for that issue I needed to make changes to this particular stylesheet, the whole idea of plug/play is gone and I started to really make it a 3.0 stylesheet for myself: using the lower-case() function instead of the translate() alternative, using typed booleans...
having a few hundred formulas in a single word document, this already has an interesting effect on the performance of this stylesheet

Would a real update to this stylesheet be welcomed here?
Has anyone plans to change this particular stylesheet?
Are there known variants that are up to date somewhere else?
Is there a tactical reason to keep this stylesheet close to the microsoft one (to enable easier updates when MS does one?)
Or is the status of this stylesheet mainly due to lack of resources? (as I would be willing to put those in)

Apologies for many questions
Thanks for any suggestions

Geert

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant