9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "John A. Murdie" <john@cs.york.ac.uk>
To: 9fans@cse.psu.edu, john@cs.york.ac.uk
Subject: Re: [9fans] off topic: troff book
Date: Mon,  8 Jan 2001 10:29:42 +0000	[thread overview]
Message-ID: <E14FZYe-000717-00@minster.cs.york.ac.uk> (raw)


Rob Pike writes:
>I didn't switch to tex when it came out because it just seemed like
>the same thing packaged differently. ... It also has
>many disadvantages, including a screwy chatty user interface

I find this the most immediate unpleasantness of TeX.

>As time has passed, I have come to understand that it
>does equations better,

The LaTeX format (layout) has (macro) packages for a wider range of
equations, but I still find troff's eqn much easier to read and write.
In fact, I think the best part of the troff approach is the use of little
languages by preprocessor, and the worst thing about troff is its use of
interrupt-like traps. If you've written a troff macro package, I think
you'll know that more than expected care is necessary to get trap use right.

Some kind of (procedural markup?) programming language is necessary in
a typesetting system. I often wonder whether something like pic with
better text primitives, and galleying (pagination) functionality, would be
a better approach. Yes, I know, I should make time to experiment.

>Because this at one level so unimportant, but at another is the entire
>point of the exercise - why create a layout language that produces
>only one layout; why create a font language if only one person
>in the world can use it to make a font - it rankles.

Yes, though there are other TeX formats (layouts), such as CONTeXT,
LaTeX is almost universally used. Most effort seems to be put into
writing extra packages for use with the LaTeX format. There is some
use of MetaFont for specification of special symbols, but the TeX
world seems to be moving away from the use of bitmap fonts generated
from MetaFonts and towards the use of commercially-provided PostScript
or TrueType typefaces.

John A. Murdie
Department of Computer Science
University of York
England



             reply	other threads:[~2001-01-08 10:29 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-08 10:29 John A. Murdie [this message]
2001-01-08 15:06 ` Mark C. Otto
  -- strict thread matches above, loose matches on Subject: below --
2001-01-08 15:17 John A. Murdie
2001-01-07 15:17 rob pike
2001-01-08  9:54 ` Luis Fernandes
2001-01-08 16:18 ` Douglas A. Gwyn
2001-01-08 20:07   ` Dan Cross
2001-01-12  9:32     ` saroj
2001-01-12 17:17       ` Douglas A. Gwyn
2001-01-12 17:51         ` Boyd Roberts
2001-01-16 16:25         ` saroj
2001-01-12 18:20       ` William K. Josephson
2001-01-12 18:51       ` Boyd Roberts
2001-01-16 16:31         ` saroj
2001-01-08 17:19 ` James A. Robinson
2001-01-08 19:21   ` Howard Trickey
2001-01-09  9:38     ` Andy Newman
2001-01-09  9:54       ` Boyd Roberts
2001-01-10  0:16 ` Steve Kilbane
2001-01-11  9:50   ` Douglas A. Gwyn
2001-01-02 10:54 steve.simon
2001-01-03  8:29 ` Boyd Roberts
2001-01-05  9:49   ` [9fans] " John E. Gwyn
2001-01-05 14:52     ` Boyd Roberts
2000-12-27 19:26 James A. Robinson
2001-01-02 17:44 ` John E. Gwyn
2001-01-05  9:48 ` Allan J. Heim
2001-01-05 14:54   ` Boyd Roberts
2001-01-05 19:29     ` Steve Kilbane
2001-01-06 17:53       ` Boyd Roberts
2001-01-07  1:20         ` Steve Kilbane
2000-08-19 21:44 Boyd Roberts

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=E14FZYe-000717-00@minster.cs.york.ac.uk \
    --to=john@cs.york.ac.uk \
    --cc=9fans@cse.psu.edu \
    /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).