Marcus Rohrmoser 🌻Hi @strifel,
während in Villariba noch geTeXd wird, wird in Villabajo schon gerofft: https://Unix-Freunde.mro.name/#:~:text=groff%2E%20Textsatz%20f%C3%BCr%20%28meine%29%20Beh%C3%B6rdenbriefe%2C%20Rechnungen%20etc #TeX #roff
;-)
a66ey 🇪🇺🏳️🌈 she/her
Felix Palmen 📯@mos_8502 Probably because (even 😏) tex is more readable (and, of course, more verbose) 😉
The only thing that still forces you to use (a limited subset of) #roff (with some macro package) is authoring manpages that should work "everywhere" (read, systems without #mandoc support) 😉
Of course, still an interesting thing to cover. I guess "power users" (having to typeset stuff a lot) would actually like the pretty terse syntax.
www-gem
Matěj Cepl 🇪🇺 🇨🇿 🇺🇦
postmodern
postmodernTIL that roff calls underlined text "italic", and both man7.org and linux.die.net correctly renders roff "italic" text in
#manpages #roff
<i> </i> tags, instead of underlining them (which would be more visually accurate, imo).#manpages #roff
DJ-Bauer
LisPi
lj·rk@ju Goes for #roff or #troff as well, even BWK recommended this back then:
> Most documents go through several versions (always more than you expected) before they are finally finished. Accordingly, you should do whatever possible to make the job of changing them easy.
>
> First, when you do the purely mechanical operations of typing, type so subsequent editing will be easy. Start each sentence on a new line. Make lines short, and break lines at natural places, such as after commas and semicolons, rather than randomly. Since most people change documents by rewriting phrases and adding, deleting and rearranging sentences, these precautions simplify any editing you have to do later.
This has even recently been rediscovered by Brandon Rhodes and Mattt culminating sembr.org.
I've prepared basically all my docs since I started LaTeX in 9th class like this. Such a life saver.