The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: David Arnold <davida@pobox.com>
Cc: segaloco <segaloco@protonmail.com>,
	Joseph Holsten <joseph@josephholsten.com>,
	Tautological Eunuch Horticultural Scythians <tuhs@tuhs.org>
Subject: [TUHS] Re: Collecting notes for future “historians” was: Earliest UNIX Workstations?
Date: Thu, 26 Jan 2023 18:35:02 -0700	[thread overview]
Message-ID: <CANCZdfrKN457+HL8pffE66LX_JME6Z5j045z=0yfTDERt9BiHA@mail.gmail.com> (raw)
In-Reply-To: <F0C9F9F3-B9B2-41E4-8C0F-E291496AA263@pobox.com>

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

I've moved to markdown or asciidoc for things like this. So many things can
import them and they are easier to write than roff or TeX.

Warner

On Thu, Jan 26, 2023, 6:29 PM David Arnold <davida@pobox.com> wrote:

> fwiw, Pandoc (https://pandoc.org) claims to be able to translate between
> MediaWiki and both man and ms roff macros.
>
>
>
>
> d
>
>
> > On 27 Jan 2023, at 11:54, segaloco via TUHS <tuhs@tuhs.org> wrote:
> >
> > You just got my head all abuzz on whether a *roff<->MediaWiki
> transpiler would be: 1. Possible and 2. Beneficial.
> >
> > We use a MediaWiki at work for aggregating random tidbits from people
> that they think might get lost in project noise.  There's times I'd love to
> have some way to *roff-ize the materials for white papers, the printouts
> from MediaWiki are uuuuugly.  Benefits on the flip-side would be rapidly
> getting all sorts of documentation into Wiki format pretty quickly.
> >
> > Of course, for an actual documentation project, there would need to be a
> master as diverse edits in different places wouldn't track with one
> another.  In this case, the *roff sources would probably make a better
> master for diff reasons.
> >
> > - Matt G.
> >
> > ------- Original Message -------
> >> On Thursday, January 26th, 2023 at 4:36 PM, G. Branden Robinson <
> g.branden.robinson@gmail.com> wrote:
> >> Hi Joseph,
> >> At 2023-01-26T14:41:50-0800, Joseph Holsten wrote:
> >>> And if I’m writing in troff, is there a preferred macro set for
> >>> articles these days? A decade ago I wrote manuals in mdoc but papers
> >>> in LaTeX; these days I just lean on pandoc to translate. I’ll need to
> >>> knock my rust off.
> >> There's always ms. It's pretty easy to acquire, and will produce
> >> authentic looking traditional Unix papers with little effort. Here's a
> >> manual that Larry Kollar and I wrote, in source and PDF forms. It's
> >> gotten positive feedback from the groff mailing list.
> >> Regards,
> >> Branden
>
>

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

  reply	other threads:[~2023-01-27  1:36 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26  0:31 [TUHS] " Joseph Holsten
2023-01-26  0:51 ` [TUHS] " segaloco via TUHS
2023-01-26  1:06   ` Luther Johnson
2023-01-26  1:15     ` Jon Steinhart
2023-01-26  1:01 ` Larry Stewart
2023-01-26 13:25   ` Marc Donner
2023-01-26 13:58     ` arnold
2023-01-31  2:03   ` Mary Ann Horton
2023-01-31 17:43     ` Marc Donner
2023-01-26  1:12 ` Tom Lyon
2023-01-26  1:47 ` Chris Hanson
2023-01-26  7:20   ` John Cowan
2023-01-26  7:33     ` Dave Horsfall
     [not found]     ` <CAD2gp_QtUPmd78yAixvKK1wzPX67HKZXzU5cJnVUbcWtMounGQ@mail.g mail.com>
2023-01-26 16:35       ` John Foust via TUHS
2023-01-26 17:58     ` Jon Forrest
2023-01-26 18:04     ` Jon Steinhart
2023-01-26 21:29       ` [TUHS] Collecting notes for future “historians” was: " Joseph Holsten
2023-01-26 21:38         ` [TUHS] " Jon Steinhart
2023-01-26 22:41           ` Joseph Holsten
2023-01-27  0:34             ` segaloco via TUHS
2023-01-27  0:36             ` G. Branden Robinson
2023-01-27  0:53               ` segaloco via TUHS
2023-01-27  1:28                 ` David Arnold
2023-01-27  1:35                   ` Warner Losh [this message]
2023-01-26  9:52 ` [TUHS] " emanuel stiebler
2023-01-26  9:58   ` Rob Pike
2023-01-26 10:09   ` Jaap Akkerhuis via TUHS
2023-01-26 15:14 ` Clem Cole
2023-01-28 21:16 [TUHS] Re: Collecting notes for future “historians” was: " Douglas McIlroy
2023-01-30  6:13 ` Phil Budne

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='CANCZdfrKN457+HL8pffE66LX_JME6Z5j045z=0yfTDERt9BiHA@mail.gmail.com' \
    --to=imp@bsdimp.com \
    --cc=davida@pobox.com \
    --cc=joseph@josephholsten.com \
    --cc=segaloco@protonmail.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).