From: toby@telegraphics.com.au (Toby Thain)
Subject: [TUHS] TeX/troff/typesetting markups - Re: SunOS 4 documentation
Date: Thu, 13 Apr 2017 22:59:33 -0400 [thread overview]
Message-ID: <d3c60e80-002c-4b02-253f-b5ea27698163@telegraphics.com.au> (raw)
In-Reply-To: <20170414004048.GC28292@eureka.lemis.com>
On 2017-04-13 8:40 PM, Greg 'groggy' Lehey wrote:
> On Friday, 14 April 2017 at 1:22:59 +0200, Steffen Nurpmeso wrote:
>> Toby Thain <toby at telegraphics.com.au> wrote:
>>
>>> 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.
>
> My issue with TeX output using standard parameters is that it reaches
> out, grabs you by the throat and says "I was formatted with Tex".
> That would be mainly the Computer Modern fonts, but I haven't seen
> that with any other text formatting software.
Yes, the font uniformity is unfortunate. Personally I think we're long
overdue for a replacement default typeface family, or better yet,
diversity (but the underlying engine I think is fine -- and so does
Adobe -- it powers InDesign's paragraph composer :)
--T
>
> Greg
> --
> Sent from my desktop computer.
> Finger grog at lemis.com for PGP public key.
> See complete headers for address and phone numbers.
> This message is digitally signed. If your Microsoft mail program
> reports problems, please read http://lemis.com/broken-MUA
>
next prev parent reply other threads:[~2017-04-14 2:59 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
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 [this message]
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=d3c60e80-002c-4b02-253f-b5ea27698163@telegraphics.com.au \
--to=toby@telegraphics.com.au \
/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).