[dalai]

Not just LaTeX, groff gets no love even though it can deliver nice output. The syntax is even more arcane, but on the other hand it doesn’t need GBs to install.

Asciidoctor is a good modern proposition that can handle more than markdown can, but it’s not without shortcomings. Unfortunately markdown, asciidoc, rst and friends have been focusing too much on publishing to the web. Conversion to PDF is mostly over html (in some cases by firing chromium in the background) and the results are not as great.

It is difficult to compete with Word for non-technical people, if the alternative is to install and learn multiple tools, configure a dev environment and setup build toolchains.

[guitarbill]

> groff gets no love even though it can deliver nice output. The syntax is even more arcane

I think you've answered it yourself. Also damning is that groff doesn't support UTF-8 directly.

Most groff guides only do very basic formatting. Complex math/equation layout can be awful. Image files apparently need to be ps/eps. I just keep running into issues.

There's also no accessible ecosystem for groff. CTAN. Code highlighting (ideally, I want to use pygments - i guess i could write a backend if i was really invested). TikZ is great and something I've invested in a lot. Bibliography management. Also, not an issue for me, but an issue for adoption is Windows support.

As for competing with Word's workflow, at least with some TeX variant I have a chance. Installer frameworks. Editors with previews. So a few GiB to not run into these limitations sounds worth it to me to be productive.

I'm not saying groff couldn't be used for complex stuff, but I wouldn't know where to begin, or want to work around all those limitations.

[dwcnnnghm]

Plan 9 troff might work! It works with utf8 out of the box[0], and while I haven't used it for complex math typesetting, there is a command (eqn [1]) that was developed for it. I'd recommend Ali Rudi's port (neatroff [2][3]) for a minimalist implementation. There's also Heirloom Documentation Tools [4] which is an implementation of *roff-and-friends that uses Knuth's paragraph-at-once algorithm (instead of the original line-wise one) for typesetting, plus some other interesting features.

The authors of eqn wrote a paper about it: "Typesetting Mathematics" by Brian Kernighan and Lorinda Cherry. Kernighan also wrote two manuals (one in 1976 with a revision in 1992, and one in 2007 with updates for the Plan 9 version). [5].

[0] utf8 was developed by Ken Thompson and Rob Pike during the creation of Plan9. The entire OS is compatible. Story here: http://doc.cat-v.org/bell_labs/utf-8_history

[1] http://man.cat-v.org/plan_9/1/eqn

[2] https://github.com/aligrudi/neatroff

[3] PDF manual for neatroff: http://litcave.rudi.ir/neatroff.pdf

[4] https://n-t-roff.github.io/heirloom/doctools.html

[5] These (and more) can be found here: http://www.kohala.com/start/troff/troff.html

[guitarbill]

thanks. i do appreciate the effort, but i feel like this just underscores my point how *roff isn't a viable ecosystem like TeX is.

this is maybe slightly unfair, since i don't use TeX or even LaTeX, but XeTeX/XeLaTeX. however, those work out of the box with MacTeX/MiKTeX. i just want pretty PDFs.

[dwcnnnghm]

My apologies. I think I misunderstand what you mean by "ecosystem". All of your requirements are fulfilled by the tools I suggested. The guides I provided show complex typesetting (mathematics and otherwise), eqn does complex math expressions (more powerful than TeX according to Lorinda Cherry, the neateqn implementation by Ali Rudi allows for using TeX bracket syntax as well), pic and grap provide complex (2D) graphics, refer and bib2ref/ref2bib provide bibliography management, and all of it installed from a single repository and makefile (maybe this is different than an installer framework?) to under 43MB (including demos and acm fonts). XeTeX/XeLaTeX seem to only add support for utf8 (as I mentioned, natively supported by the plan9 *roffs) and various font formats (at least supported by neatroff, I haven't checked the others). Of course, pretty PDFs was the original point you quoted in the parent.

You should at least check out the neateqn guide for examples of math typesetting (even output in Computer Modern). But the original guide, as well as the others will show many more and different examples. These aren't groff guides. You might be surprised.

[guitarbill]

It's funny, I looked at the "Typesetting Mathematics -- User's Guide (Second Edition)" postscript document, and - at least with macOS' Preview - some big brackets are segmented (Neatroff brackets don't seem to do this, although I've seen it in other troff generated documents), and they even say this:

> Warning — square roots of tall quantities look lousy, because a root-sign big enough to cover the quantity is too dark and heavy

The solution is naturally to rewrite big roots as powers.

pic does seem close to Tikz, although I had to look in the GNU pic doco to figure out how to do colors. Even then, transparency didn't seem to be supported?

Heirloom actually looks the most useful/mature. At least the output looks pretty/someone cared enough to make the example files pretty, there's actual documentation. Limitations are still there (having to convert bitmaps to EPS?). I will say I'm at least slightly impressed by `gpresent`, which is like beamer (so for making presentations), and built-in hyphenation support.

I still don't get Neatroff. It's compatible with/implements a lot that Heirloom does, but then the font support is worse again? It's an impressive project though, the source is very readable, and RTL/LTR support. Less impressive is the lack of a license - I think it's ISC, based on a single comment, but who knows?

---

A repository and a makefile are distinctly different than an installer. Random macro packages that may or may not be on GitHub are different than `tlmgr`. Piping stuff around and having to convert images is different than just one command. GUI editors. Example documents (like https://texample.net/). That is what I mean by ecosystem.

XeTeX outputs PDFs by default (granted, via xdvipdfmx), and can also include bitmaps directly (again, granted it needs graphicx or something). All TeX stuff isn't without it's warts, and seems overly complex (pdfTeX/XeTeX/XeLaTex/LuaTeX/ConTeXt, etc). But in practice, it kinda somehow just works (until it doesn't).

[0] https://github.com/rhaberkorn/gpresent

[dwcnnnghm]

I appreciate you having a look! I totally understand if it's not enough to make a switch, but I'm glad you were able to see that it's not so bad on this side of things. There's definitely not enough niceties for the average computer user (GUI editing and installing) and some missing for any user (package manager). I will stand by piping as a matter of taste (the biggest benefit for me is it allows for using the tools I'm already familiar with, awk and grep or plain c/zig).

---

My interest in neatroff is mostly the code itself. A tiny and opinionated project with readable source that still achieves quite a lot (all that I need anyways). But it's definitely not for everyone! The author doesn't use a windowing system, for example, and instead uses the framebuffer for pdf viewing and editing (both custom implementations). It is ISC, by the way. It's included in the bottom of the readme.