KaTeX VS unified

I want to resolve this KaTeX issue, so in order to test my ideas, is there some LaTeX test file with just a lot of equations, preferably inline (since this issue is related to inline math) but without fancy libraries or stuff not included in KaTeX?

> Could you elaborate on why you switched away from it?

I started using KaTeX sometime after 2015 because it promised to be fast (the fastest! [1]). I had to change the representation of a bunch of expressions because KaTeX didn't support some environments, whilst MathJax did. It was a trade-off I was willing to accept at the time.

Many years later, I started writing a personal static-site generator. I wanted comparatively lightweight pages, so rendering server-side was an option. I re-evaluated MathJax vs KaTeX again and this time I leaned towards MathJax, as speed was no longer an issue for me. It looks like KaTeX has broader support now [2].

[1] https://katex.org

[2] https://katex.org/docs/support_table.html

Another alternative: Create a WebView by using UIViewRepresentable and Webkit together with MathJax or Katex where Katex is the better option. Here is a link to katex: https://katex.org/

This isn't a LaTeX question. It's a web dev question. Probably best directed at folks who make (or use) KaTeX.

KaTeX

(1) [https://katex.org/

If you want to make it from scratch, go with https://www.slatejs.org/examples/richtext, then use something like https://katex.org/ for rendering the LaTeX, and maybe Mathjs.org for plotting.

The speed of KaTeX is great, but the lack of support for diagrams (a la tikz-cd) is what makes KaTeX unsuitable for general adoption by mathematicians (e.g., mathoverflow.net and all online mathematical wiki I know use MathJax). KaTeX has some rudimentary support for diagrams though the {CD} environment, but something more fully fledged akin to tizk-cd or xymatrix is needed. There's been some discussion on their github (https://github.com/KaTeX/KaTeX/issues/219), but I wouldn't hold my breath.

Haven't personally used it, but have heard of KaTeX

From TFA:

> My idea was that surely it's possible to write a bunch of markdown, and then have that get wrapped in a bunch of JSX tags that come pre-styled, using the styles of your existing repo? For example, what I expected was to be able to write *test* (Markdown for bold) and then get a component that looked liketest where is a library-defined React component

It surely is possible, so perhaps I can share some links if others are wondering the same thing.

If you like to roll your own solution for that, you can use the unified ecosystem: https://unifiedjs.com/

However, if you want JSX just do what everyone does and reach for MDX:

Styling the blog, figure out the eco-system within UnifiedJs, remark-rehype, oh boy, I could write another blog with that.

To build the Markdown editor (and the preview, mostly), I decided to use unified, an ecosystem of tools allowing the developer to parse a format into an abstract tree and back into another format (for example, markdown to html) and modify said tree (for example, to add specific classes to certain html elements before they are converted to an actual html string. The basics of how to do so can be found in this article, but they mostly consist of:

It’ll take you a few hours to become proficient in the “unified” syntax tree libraries. So worth it. Easy fully customized conversion to/from html, react, plain text, markdown, you name it. https://unifiedjs.com/

Why universal? Because a lot of languages are simillar in a bunch of ways and it might be good to reuse existing parts of the compiler to speed up the process of writing new DSLs for example. Also a pretty big use-case is not for compilers itself but just for transformers like Markdown to HTML, there are already a lot of libraries (like https://github.com/unifiedjs/unified for ASTs and https://tree-sitter.github.io/tree-sitter/ for parsing) that try achieve similar goals but they are not working together.

Unified is a framework to process Markdown. It's a plugin-based tool that allows you to inspect and modify the way Markdown is converted to other formats like HTML.

under the hood, the markdown is parsed by the unified remark and rehype processors, which in turn under the hood manipulate the markdown + HTML as an AST, which gives a lot of flexibility on parsing and rendering markdown. The editor uses them as plugins, which allows me to pick the features and inject them into the editor, one such injectable feature is the custom-made "copy from anywhere & paste as markdown" feature.

Having the flexibility to create custom React Components for markdown is essential and with react-markdown, we can achieve this in just a few lines of code. Boosting performance, increasing link security, and having overall increased capabilities for our markdown data are what we achieve here. Aside from the improvements within our application, this component is super easy to use and taps us into the unifiedjs (giving us superpowers!).

The Markdown processor used unified assets.