Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@iitbombay.org>
To: Clem Cole <clemc@ccc.com>
Cc: Computer Old Farts Followers <coff@tuhs.org>
Subject: Re: [COFF] Scribe (Typesetting System) and Unix
Date: Thu, 13 Jan 2022 10:00:15 -0800	[thread overview]
Message-ID: <386AE80E-872F-46D4-B441-97C1A8123176@iitbombay.org> (raw)
In-Reply-To: <CAC20D2O1jhEqEgw+LmhOgxEyACtz2j+kkzTE6dhjshacxGeEEw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2140 bytes --]



> On Jan 13, 2022, at 8:06 AM, Clem Cole <clemc@ccc.com> wrote:
> 
> 
> 
> On Thu, Jan 13, 2022 at 10:08 AM John P. Linderman <jpl.jpl@gmail.com <mailto:jpl.jpl@gmail.com>> wrote:
> Many of us who wrote articles for the Bell System Technical Journal would disagree. The BSTJ  publishers could transform something that made sense when viewed as troff output into unintelligible gibberish. You cannot split a UNIX command line into multiple lines just because it "looks better". Sometimes format really matters.
> I think that is true for any scheme -- professionals and editors need to work together.  That's what Jon was suggesting.  When they don't have shared vocabulary/goals -  bad things can happen.   FWIW: I can not speak for him directly as I never had this conversation with him (Win might have), but from what I knew/know of Brian Ried I think he might agree with what I'm suggesting.  IMO, there will always be cases like the one that you described.  This is not particular to any document compiler system.   The question is how to bring the two sides together and who has the high order bit? 

In one of his blogposts Douglas Crockford has suggested that Scribe would have made a better declarative markup language than SGML!

If you read Bibtex's manual they talk about <some feature> being put in for SCRIBE compatibility. Even the bibliographic reference form looks SCRIBE-like. For example,

@Article{Arrabito:EPODD-1-2-117,
  author =       "R. Arrabito and H. J{\"{u}}rgensen",
  title =        "Computerized {Braille} Typesetting: Another View of Mark-up Standards",
  journal =      j-EPODD,
  year =         "1988",
  volume =       "1",
  number =       "2",
  pages =        "117--132",
  month =        sep,
}

But in a sense the Scribe markup is at a different level than troff or TeX. LaTeX is more declarative, which is one of the reasons for people preferring it to pure TeX.

> My complaint with Word and the like, is that the 'control' is hidden.  It's $%^& magic -- why is it indenting here?  Hey I did not tell it to make it go italics ...

Word is lower level than TeX/troff. 

[-- Attachment #1.2: Type: text/html, Size: 4075 bytes --]

[-- Attachment #2: Type: text/plain, Size: 141 bytes --]

_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff

  parent reply	other threads:[~2022-01-13 18:00 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13  2:04 josh
2022-01-13  2:03 ` Greg 'groggy' Lehey
2022-01-13  3:24 ` Win Treese
2022-01-13 14:56   ` Clem Cole
2022-01-13 15:08     ` John P. Linderman
2022-01-13 16:06       ` Clem Cole
2022-01-13 16:24         ` Warner Losh
2022-01-13 16:39         ` Harald Arnesen
2022-01-13 18:00         ` Bakul Shah [this message]
2022-01-13 15:35     ` Dan Cross
2022-01-13 16:02       ` Warner Losh
2022-01-13 16:20         ` Clem Cole
2022-01-13 16:32           ` Warner Losh
2022-01-13 16:42           ` Lars Brinkhoff
2022-01-13 16:52             ` Larry McVoy
2022-01-13 16:54               ` Clem Cole
2022-01-13 17:06               ` Clem Cole
2022-01-13 18:16         ` Dan Cross
2022-01-13 20:00           ` Larry McVoy
2022-01-13 20:26           ` Chet Ramey
2022-01-13 16:13       ` Charles H Sauer
2022-01-13 22:53     ` David Arnold
2022-01-14  1:53       ` Adam Thornton
2022-01-13  3:26 ` Theodore Ts'o
2022-01-13 16:25   ` Larry McVoy
2022-01-13 16:33   ` Dan Cross
2022-01-13 22:19     ` David Arnold
2022-01-13 13:54 ` Adam Sampson
2022-01-13 16:37   ` Lars Brinkhoff

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=386AE80E-872F-46D4-B441-97C1A8123176@iitbombay.org \
    --to=bakul@iitbombay.org \
    --cc=clemc@ccc.com \
    --cc=coff@tuhs.org \
    /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).