From: toby@telegraphics.com.au (Toby Thain)
Subject: [TUHS] TeX/troff/typesetting markups - Re: SunOS 4 documentation
Date: Thu, 13 Apr 2017 12:35:19 -0400 [thread overview]
Message-ID: <4f202ee6-65af-f027-8833-299bc7b0726a@telegraphics.com.au> (raw)
In-Reply-To: <e569f91d-f34a-3ab6-af64-1aec6e704371@telegraphics.com.au>
On 2017-04-12 10:25 PM, Toby Thain wrote:
> On 2017-04-12 10:16 PM, Steve Nickolas wrote:
>> On Wed, 12 Apr 2017, Toby Thain wrote:
>>
>>> You can get really really close to that dream with TeX based tools
>>> like LyX, etc (and indeed Blue Sky Research had a wysiwyg TeX system
>>> back in the late 1980s).
>>>
>>> While troff can get stuff done in its area, for heavy duty work and
>>> exacting typography, TeX's markup blows troff out of the water, I am
>>> afraid.
>>
>> Heh, yeah. I'd defy anyone to typeset a Bible with troff, but I did it
>> reasonably well with XeLaTeX.
>
> I did a 400+ page novel in it once. This had a few benefits. One was
Since it was a bit unclear from context: I'm referring to TeX here and
below.
> that the same markup could generate double spaced typewriter-style
> printouts for the novelist to bind and scribble his corrections on,
> while at the same time producing the final plate-ready negatives for the
> printer.
>
> Sadly I'm not called much to use it any more but it's a tangible
> pleasure when I do.
>
> (Although I have to say that I don't like CMR much.)
>
> --T
>
>>
>> -uso.
>>
>
>
next prev parent reply other threads:[~2017-04-13 16:35 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 [this message]
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
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=4f202ee6-65af-f027-8833-299bc7b0726a@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).