5 ms·
As a t/roff and eqn and tbl user I never found the story compelling. The uplift cost to latex in 1982 was north of my painpoint and in 1990 I managed to do thin
by ggm 8y ago
As a t/roff and eqn and tbl user I never found the story compelling. The uplift cost to latex in 1982 was north of my painpoint and in 1990 I managed to do things in tbl and eqn I never imagined possible. Tex font fascism was also a bummer. A phototypesetting expert I knew preferred the actual type to digital type, the microfilm typeset stuff was amazing (I saw galley proofs in bromide and they were crisp and clean)
I think I "get" it better now. It's just at that time there was another school of more pragmatic engineering aligned thought in Unix using Dec10 RUNOFF derived concepts which morphd into t/roff and stuck there.
Maybe it's like Emacs and vi? Dec 10 SOS editor was like ed which led to ex and vi. If you walked into the TECO door you went lisp and Emacs.
To launch into Tex and latex you needed a professor leading you there rather than an engineer doing nroff and t/roff
- sampo 8y agoSystems engineers (for example the K&R "C Programming Language" book) didn't need elaborate math notation, like Knuth needed.
- ggm 7y agoEqn was invented precisely to do elaborate math notation. Integrals, sweeping braces, majuscule and minescule letters, suffixes, Greek..
- pjc50 8y agoInteresting to hear from the pre-Tex world. I'd like to see some examples of expert use of tbl and eqn; outside of manpages the roff ecosystem seems to have vanished.
- cpach 7y agoroff is probably very uncommon in these days. But not unheard of. A recent example is Donovan and Kernighan’s book The Go Programming Language which was typeset using an XML and groff toolchain. It was featured on HN a few years ago, see https://news.ycombinator.com/item?id=11470905 https://news.ycombinator.com/item?id=11470905
- fanf2 7y agoThe BSDs ship with a lot of the original non-man-page Unix documentation: the system manager’s manual, the programmer’s supplementary documentation, and the user’s supplementary documentation. These are written to be typeset with troff, not printed on a teletype like the man pages can be, so they tend to be a bit more refined. https://svnweb.freebsd.org/base/head/share/doc/ https://svnweb.freebsd.org/base/head/share/doc/ They are missing some chapters (eg eqn and tbl) due to copyright disputes but you can find them in TUHS archives https://minnie.tuhs.org/cgi-bin/utree.pl?file=V7/usr/doc https://minnie.tuhs.org/cgi-bin/utree.pl?file=V7/usr/doc
- wglb 7y agoThis http://www.nesssoftware.com/home/mwc/manual.php http://www.nesssoftware.com/home/mwc/manual.php was set with the Coherent version of nroff. Result is damned excellent.
- ggm 7y agoSince xml2rfc and the rise of markdown I would agree in std land because troff markup for RFCs was a big thing