From: steffen@sdaoden.eu (Steffen Nurpmeso)
Subject: [TUHS] TeX/troff/typesetting markups - Re: SunOS 4 documentation
Date: Fri, 14 Apr 2017 01:22:59 +0200 [thread overview]
Message-ID: <20170413232259.53GdF%steffen@sdaoden.eu> (raw)
In-Reply-To: <f4719263-cbbe-f75a-e3ba-3826bec9d8af@telegraphics.com.au>
Toby Thain <toby at telegraphics.com.au> wrote:
|On 2017-04-13 9:41 AM, Steffen Nurpmeso wrote:
|> ...
|> i have no idea of what happened on the TeX side in the last, say,
|> about 15 years. TeXLive has always been too large for me, i have
|
|They have a small "basic" version with the essentials, a hundred
|megabytes or so.
|
|http://www.tug.org/mactex/morepackages.html
Oh, ok, now MacTeX basic, 110 MB. That is really much, much
better, for me, that is. I never used TeX since then, so i cannot
really tell -- my KerTeX repo ball is 11 MB..
...
|> My finding is that, with groff, i can produce papers (mostly
|> letters) of almost identical beauty with some fine-tuning, with
|> almost the identical number of "markup" (which is now also easily
|> typed with the american keyboard). And the fine-tuning i like,
|> because i adore the calligraphic as an art, as an act of devotion
|> of the calligrapher, to some higher spirit or the being as such,
|> and spending some seconds in some text is my simple Boche
|> equivalence to those fine spirits.
|
|Indeed, as a typographer, I believe details matter, no matter what the
|audience. I think Knuth feels the same way. :)
It is really perfectly looking. Maybe too perfect, in the
sense of, maybe even aseptic. At least when having handmade,
artistic calligraphy as a personal optimum. But this is of course
strange for business letters, and doesn't excuse irregular holes
in between words all over the page, as can be seen in
non-optimized roff.
--steffen
next prev parent reply other threads:[~2017-04-13 23:22 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 21:54 [TUHS] " Cory Smelosky
2017-04-12 22:55 ` Cory Smelosky
2017-04-12 23:31 ` Larry McVoy
2017-04-13 2:13 ` Toby Thain
2017-04-13 2:16 ` Steve Nickolas
2017-04-13 2:25 ` [TUHS] TeX/troff/typesetting markups - " Toby Thain
2017-04-13 14:25 ` Nemo
2017-04-13 15:41 ` Andreas Kusalananda Kähäri
2017-04-13 16:35 ` Toby Thain
2017-04-13 2:20 ` [TUHS] " Larry McVoy
2017-04-13 13:41 ` Steffen Nurpmeso
2017-04-13 15:40 ` [TUHS] TeX/troff/typesetting markups - " Toby Thain
2017-04-13 23:22 ` Steffen Nurpmeso [this message]
2017-04-14 0:40 ` Greg 'groggy' Lehey
2017-04-14 1:59 ` Nemo
2017-04-14 3:00 ` Toby Thain
2017-04-14 2:59 ` Toby Thain
2017-04-14 13:38 ` Steffen Nurpmeso
2017-04-14 13:56 ` Michael Kerpan
2017-04-14 16:55 ` Steffen Nurpmeso
2017-04-14 22:24 ` Toby Thain
[not found] ` <CAHfSdrVAnPn3hwFR0ie0o-yuqGX0hu+LWweNZngpoY4=efTSaA@mail.gmail.com>
2017-04-15 14:23 ` Michael Kerpan
2017-04-15 15:09 ` Toby Thain
2017-04-15 16:07 ` [TUHS] TeX/troff/typesetting markups - " Mutiny
2017-04-15 21:48 ` Dave Horsfall
2017-04-15 22:12 ` ron minnich
2017-04-16 0:02 ` Dave Horsfall
2017-04-15 15:27 ` [TUHS] TeX/troff/typesetting markups - " Clem Cole
2017-04-15 17:05 ` Toby Thain
2017-04-15 17:10 ` Toby Thain
2017-04-18 4:49 ` Greg 'groggy' Lehey
2017-04-14 13:07 ` Wolfgang Helbig
2017-04-14 20:56 ` Clem Cole
2017-04-16 13:42 ` Tim Bradshaw
2017-04-13 14:14 ` [TUHS] " Nemo
2017-04-13 16:34 ` Steve Simon
2017-04-13 23:14 ` Steffen Nurpmeso
2017-04-14 8:30 ` Steve Simon
2017-04-14 13:21 ` Steffen Nurpmeso
2017-04-13 13:28 ` John Labovitz
2017-04-17 18:56 [TUHS] TeX/troff/typesetting markups - " Doug McIlroy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170413232259.53GdF%steffen@sdaoden.eu \
--to=steffen@sdaoden.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).