It is unique from LaTeX and theorem proving languages and has a different goal. See the documentation at www.mathlingua.org for more information.
This post is a follow-up to https://news.ycombinator.com/item?id=23960662 and many changes have been made to MathLingua since that time based on the feedback from that post.
In particular, since that time, I have added numerous improvements to the language to improve its usability, have drilled down on a particular use-case that I have documented more clearly, and have created a `mlg` command line tool to interact with the MathLingua language.
In particular, using `mlg check` one can check their MathLingua documents for errors, with `mlg document` one can create a dynamic static site of their documents suitable to be shared on GitHub pages, and with `mlg edit`, an in-browser IDE is available to edit your MathLingua documents with live previews, auto-complete, etc.
I really appreciate all of the feedback I received previously, and any and all feedback now is greatly appreciated.
As such you can use whatever visual representation you want for operations and definitions.
For a particular math definition, you can also specify multiple different notations for the concept (in this case, MathLingua uses the first one when rendering results).
An example of this is the derivative of a function in the “A Detailed Example” section of the docs.
I am really excited about this project because it makes it very clear how everything hangs together in a way that I haven't experienced before. The visual structure of a single definition/theorem/states is very helpful. Also, knowing how many 'levels' from the original concept I'm currently exploring while unpacking and re-packing just helps everything click into place.
Very, very cool.
MathLingua, on the other hand, focuses on being precise and easy to read and write in its raw form.
Every definition has a ‘written:’ section describing how to express the math idea on paper and a ‘called:’ section describing how it is described when speaking.
Right now the ‘written:’ is used to render how a result looks, and in a similar way the ‘called:’ section can be used to convert a result into a transcript that a screen reader would read.
I haven’t yet been able to implement this feature though, but stay tuned for updates.
Madoko has great support for rendering maths for the web, by far superior to KaTeX and MathJax.
