The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: The Unix Heritage Society <tuhs@tuhs.org>
Subject: [TUHS] Re: pic
Date: Wed, 10 Aug 2022 20:10:57 -0400	[thread overview]
Message-ID: <CAEoi9W5qMuHf5D3NsxpnNo9iwn8+GBYf9jHqWUCANbzkPnHgFA@mail.gmail.com> (raw)
In-Reply-To: <202208101824.27AIOQG81222103@darkstar.fourwinds.com>

On Wed, Aug 10, 2022 at 2:24 PM Jon Steinhart <jon@fourwinds.com> wrote:
> Dennis Boone writes:
> >  > Would that happen to be available somewhere, for posterity?
> >
> > pic2plot, from the plotutils package, will do pic -> various formats,
> > including svg.
>
> Huh.  Wasn't aware of that one, but seems to rely on a groff svg driver
> which I've never seen.
>
> What I've done is pic -> groff -> ps2pdf -> pdf2svg -> inkscape.
> Inkscape is used just to crop bounding box to the image size so
> that there's not a huge amount of whitespace.

Google has built an in-house documentation system
based on extended markdown, and it was very nice:
check your text markdown files into a specially-named
subdirectory in the monorepo and point a web browser
at an internal service for a nicely rendered web version,
available immediately. There was a syntax for including
graphviz markup, and something similar for (I think)
state diagrams, but support for more general drawing
was missing, and I thought pic(1) would be just dandy,
if it could be persuaded to generate SVG.

I wrote to Brian, who works part-time at Google, and
pitched the idea to him, and he extended pic to
generate SVG, though it wasn't clear to what sources
he was modifying, exactly. Then the pandemic hit, and
I ended up leaving Google, so I don't think it went
beyond that, but IIRC he said that coercing pic to
generate SVG wasn't particularly difficult.

        - Dan C.

  reply	other threads:[~2022-08-11  0:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09 22:18 [TUHS] Re: SNOBOL and RATSNO Douglas McIlroy
2022-08-09 22:25 ` Larry McVoy
2022-08-10 15:05 ` arnold
2022-08-10 17:14   ` Larry McVoy
2022-08-10 17:37     ` arnold
2022-08-10 17:44       ` [TUHS] Re: SNOBOL and RATSNO [ really pic ] Jon Steinhart
2022-08-10 18:02         ` Larry McVoy
2022-08-10 18:04           ` Jon Steinhart
2022-08-10 18:13             ` [TUHS] Re: pic Michael Kjörling
2022-08-10 18:19             ` Dennis Boone
2022-08-10 18:24               ` Jon Steinhart
2022-08-11  0:10                 ` Dan Cross [this message]
2022-08-11 12:13                   ` arnold
2022-08-11 14:34                     ` Dan Cross
2022-08-12  1:52                       ` G. Branden Robinson
2022-08-12  6:46                         ` arnold
2022-08-12 20:49                           ` G. Branden Robinson
2022-08-11  7:37           ` [TUHS] Re: pic's One-way Information Flow. (Was: SNOBOL and RATSNO) Ralph Corderoy
2022-08-10 18:24       ` [TUHS] Re: SNOBOL and RATSNO joe mcguckin

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=CAEoi9W5qMuHf5D3NsxpnNo9iwn8+GBYf9jHqWUCANbzkPnHgFA@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).