You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am writing to kindly request the addition of the \dagger symbol to the AsciiMath standard, similar to its usage in LaTeX. As a frequent user of AsciiMath for mathematical typesetting, I find this symbol indispensable for my work.
Additionally, I have noticed some discrepancies on AsciiMath.org. Specifically:
The keyword "mlt" is rendered as "m <", whereas I was expecting behaviour equivalent to the \ll command in LaTeX.
A similar issue occurs with "mgt", which does not align with my expectations of LaTeX's \gg functionality.
Could you please review these cases and provide clarification or potential updates to the standard?
The text was updated successfully, but these errors were encountered:
For dagger, you're welcome to make a pull request to add it to the symbol table. If you're not comfortable doing this, I can try to add it when I have the time.
As for mgt and lgt, they are part of the asciimath scripts in this repo. But these scripts were designed to generate MathML, so aren't used directly many places, since most browsers can't display MathML. So most websites, including Asciimath.org, use MathJax for rendering the Asciimath. Unfortunately they don't always keep their implementation up to date with our scripts. You'd have to raise an issue with them to address that. Or, if you're using Asciimath on a website you host, there are ways to extend the MathJax symbol table with symbols you need support for.
I am writing to kindly request the addition of the \dagger symbol to the AsciiMath standard, similar to its usage in LaTeX. As a frequent user of AsciiMath for mathematical typesetting, I find this symbol indispensable for my work.
Additionally, I have noticed some discrepancies on AsciiMath.org. Specifically:
Could you please review these cases and provide clarification or potential updates to the standard?
The text was updated successfully, but these errors were encountered: