The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Unix tools to aid in the production of Internet RFCs?
Date: Wed, 2 Sep 2020 19:11:41 -0400	[thread overview]
Message-ID: <CAEoi9W7-0FEt_SMBgM--BjtiUKe8PkpD-pT1PfzV7LSn7ESuXQ@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W7jn06yFP4SPaZ3bxZGWkMc8zgRFRWdLM91yZ1Kgq9V4g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]

Thanks all, for the very interesting responses to this thread. It sounds
like _most_ of the Unix-based preparation efforts centered around an
`nroff`-based workflow until the advent of XML.

        - Dan C.


On Wed, Aug 26, 2020 at 5:24 PM Dan Cross <crossd@gmail.com> wrote:

> Honestly, I'm not quite sure if this is a TUHS, COFF, or IH question. But
> since my background with respect to such things is largely Unix centric, I
> thought I'd ask in that context, hence asking on TUHS.
>
> I assume some of the regulars on this list have authored RFCs (of the IETF
> etc variety). The RFC format seems fairly well fixed: table of contents,
> fixed number of lines per page, page numbers and dates in the footer, and
> so forth. The format is sufficiently complex that it seems like some
> tooling could be usefully employed to aid in producing these documents.
>
> So I'm curious: what tools did people use to produce those documents?
> Perhaps `nroff` with custom macros or something?
>
>         - Dan C.
>
>

[-- Attachment #2: Type: text/html, Size: 1430 bytes --]

      parent reply	other threads:[~2020-09-02 23:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-26 21:24 Dan Cross
2020-08-26 21:30 ` Bakul Shah
2020-08-26 22:02 ` Clem Cole
2020-08-27 17:51   ` Tony Finch
2020-08-27 18:32     ` Clem Cole
2020-09-02  6:03     ` Random832
2020-09-02 15:39       ` Fabio Scotoni
2020-09-02 15:50         ` Richard Salz
2020-09-02 23:11 ` Dan Cross [this message]

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=CAEoi9W7-0FEt_SMBgM--BjtiUKe8PkpD-pT1PfzV7LSn7ESuXQ@mail.gmail.com \
    --to=crossd@gmail.com \
    --cc=tuhs@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).