[kiwi0fruit]

SugarTeX is a more readable LaTeX language extension and transcompiler to LaTeX. Designed to be used instead of $formula$ insertions to Markdown.

I use Markdown with Python code blocks for document programming via [Pandoctools](https://github.com/kiwi0fruit/pandoctools) (like R-Markdown).

Both Python and Markdown are very readable languages. Unfortunately LaTeX is not like this. So I wrote SugaTeX extension+transpiler that is highly readable. In order to achieve this it heavily uses Unicode so that SugarTeX install instructions even have recommended monospace font fallback chains.

[SugarTeX repo](https://github.com/kiwi0fruit/sugartex) with description.

Example of input to output conversion is at the end of [this PDF](https://github.com/kiwi0fruit/sugartex/blob/master/sugartex....).

[kiwi0fruit]

NEW EXAMPLES ADDED ==================

Examples of input to output conversion see in this PDF:

https://github.com/kiwi0fruit/sugartex/blob/master/examples/...

[kccqzy]

> Designed to be used instead of $formula$ insertions to Markdown.

What's the downside of having $formula$ blocks in Markdown?

[orangea]

ˎa/bˎ is easier to read than $\frac{a}{b}$.

[diffeomorphism]

If it is only about reading then why not something like auctex preview (shows rendered graphics in place of commands)?

https://www.gnu.org/software/auctex/img/preview-screenshot.p...

or fold-mode (shows unicode and abbreviations in place of commands)?

https://www.flannaghan.com/2013/01/11/tex-fold-mode

Changing the representation seems more sensible to me than changing the underlying file.

Also, while the a/b syntax is easier for easy cases, I shudder to think how a continued fraction might be type set: https://en.wikipedia.org/wiki/Continued_fraction

This seems to make easy things easier and harder things really hard.

Kinda like https://www.lyx.org/Screenshots or using org-mode for latex. Convenient for simple matters and something you have to fiddle with or work around when you want to do anything more advanced.

[taeric]

Oddly, Knuth prefers ${a \over b}$. I think I agree, if only because it actually reads well.

An odd thing I found, was the once I learned how to verbalize many of the maths that I encountered, reading them became much easier. LaTeX actually helped a lot here, because most of the constructs have good readable macros to typeset them.

[svat]

More on Knuth preferring `\over`: https://tex.stackexchange.com/a/390977/48 (I may have gone a little overboard…) The LaTeX (not TeX) community seems to strongly prefer `\frac` and strongly discourages `\over`, e.g. https://tex.stackexchange.com/questions/73822/what-is-the-di...

[jgtrosh]

Also, if you're interested in readable languages, there's the family of roff languages that might seem terse at first when coming from LaTeX but actually have a very enjoyable grammar. The LaTeX ecosystem is so great that I don't really miss roff but I do have nice memories of writing reports in roff a couple of years ago. More to the point I found it wonderful to write graphics in the roff pic sublanguage.

Edit: actually even more to the point is the eqn sublanguage which really competes with Knuth notation.

[svat]

It's not a coincidence: in fact, eqn (the ACM paper by Kernighan and Cherry was published in 1975) predates the initial design of TeX (1977), and Knuth explicitly based the math notation in TeX on that of eqn. Initially, like eqn he had no backslashes, but quickly (before any code was written) changed it to one with backslashes.

He discuses these matters of syntax in his Gibbs lecture of of January 1978 (https://projecteuclid.org/euclid.bams/1183544082): see Figure 3 on the top of page 344, where the notation of eqn is marked "Type B" (“developed at Bell Telephone Laboratories”) and the third column is "Type T".

[kccqzy]

> I found it wonderful to write graphics in the roff pic sublanguage.

I happen to have fond memories of using lots of TikZ to do lots of graphics, making full-color posters with it. It was only because I was too poor to buy InDesign.