ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: Duncan Hothersall <dh@capdm.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: mathcolor attribute in MathML (mkiv)
Date: Thu, 27 May 2021 19:00:26 +0200	[thread overview]
Message-ID: <fd661690-84e8-8962-0019-c680448df5ff@xs4all.nl> (raw)
In-Reply-To: <CAN8fp9W5+gRhCn_h_krsie2mw_vkPaq0EPY6PanOHW6=uEPQcA@mail.gmail.com>

On 5/27/2021 6:30 PM, Duncan Hothersall wrote:
> Apologies Hans.
> 
> MWE:
> 
> \usemodule[newmml]
> \starttext
> \xmlprocessdata{}{<formula>
>   <math xmlns='http://www.w3.org/1998/Math/MathML 
> <http://www.w3.org/1998/Math/MathML>'>
>    <mi>E</mi>
>    <mfenced>
>      <mo mathcolor="red">π</mo>
>    </mfenced>
>   </math>
> </formula>}{}
> \stoptext
> 
> The π symbol does not show in red.
Kind of trivial ... i'll send you a patched module.

If you want you can check with the standard and see where we need to add 
it. I'll then adapt the mkiv file before taking a look at upgrading the 
lmtx one.

For decades this mathml stuff has been a bit of a pain, because when one 
uses it for a mixed web / text project one always needs to satisfy the 
latest greatest either or not bugged web rendering, it disappearing from 
browsers, coming back, rendered remote or in the browser, mixed 
(in/with) asciimath which has its own tweaks. A pitty that content 
mathml never took off, probbably also due to the failure of openmath 
which took away attention from it and that we actually sort of 
support(ed). So when it comes to (reasonable quality) rendering in print 
one always runs a bit behind.

I'm also always a bit hesitant to touch the code because it's actually 
used by a collegue in some (zero budget, so me looking at the mml is 
just hobbying) projects concerning math school books where often the web 
part controls the limitations and enforces weird coding (tens of 
thousands of files with plenty mathml). Btw, especially symbols are a 
mess and interfere with assumed structure, so that's always tricky to 
touch. Especially when you want to have it specific for (mid/high) 
school math.

But anyway things like a bit of color and so are not that hard to 
support (more a matter of making sure performance is not hit).

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2021-05-27 17:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27 15:47 Duncan Hothersall
2021-05-27 16:18 ` Hans Hagen
2021-05-27 16:30   ` Duncan Hothersall
2021-05-27 17:00     ` Hans Hagen [this message]
2021-05-27 17:07       ` Duncan Hothersall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fd661690-84e8-8962-0019-c680448df5ff@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=dh@capdm.com \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).