SRE special treatment in Braille for mod and rem

[Michael Duffy]

Hi,

I've been playing around with the Braille translation a bit, and noticed a change in recent iterations. I had a document with <m>p \pmod{q} </m>, which should Braille up simply as p (mod q). It used to do this; however, in recent runs there are dot-5 marks in between the letters of mod, i.e. p (m"o"d q).

In the script/mjsre/node_modules/speech-rule-engine/js/semantic_tree/semantic_attr.js, most functions are given SemanticType.FUNCTION, whereas only the keywords "mod" and "rem" are given the SemanticType.OPERATOR. I imagine that this distinction is the source of the behavior, although I don't know how to test the rem keyword to be certain.

Is this something to be done on SRE's end? And/or is this intended behavior?

[Rob Beezer]

Dear Michael,

Thanks for digging into this. Recent changes are likely due to our switch to
MathJax 4 with a newer SRE. I noted lots of changes in the Nemeth. Should be
obcious when if you look at teh log, or holler if that is necessary information.

SRE is sort of a black box as far as Pretext goes. We certainly advise heavily,
but we do not take part in much development work.

I'd suggest an issue on the SRE GitHub site. Please ping me with "@rbeezer" and
I would introduce yourself as working with us, and especially Al M. (Your
handle is not 100% obvious!)

Rob

> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt development" group.
> To unsubscribe from this group and stop receiving emails from it, send an email
> to pretext-dev...@googlegroups.com <mailto:pretext-
> dev+uns...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/pretext-
> dev/3137616f-5fd6-46c7-80fd-2ca42ce7f6bcn%40googlegroups.com <https://
> groups.google.com/d/msgid/pretext-
> dev/3137616f-5fd6-46c7-80fd-2ca42ce7f6bcn%40googlegroups.com?
> utm_medium=email&utm_source=footer>.