The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arnold@skeeve.com
To: tuhs@tuhs.org, crossd@gmail.com
Subject: [TUHS] Re: pic
Date: Thu, 11 Aug 2022 06:13:23 -0600	[thread overview]
Message-ID: <202208111213.27BCDOfi019865@freefriends.org> (raw)
In-Reply-To: <CAEoi9W5qMuHf5D3NsxpnNo9iwn8+GBYf9jHqWUCANbzkPnHgFA@mail.gmail.com>

Dan Cross <crossd@gmail.com> wrote:

> 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.

I'm sure he'd have been messing with his own sources. These
days it'd be best to tr to get new features into GNU pic
(IMHO, of course).

Arnold

  reply	other threads:[~2022-08-11 12:13 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
2022-08-11 12:13                   ` arnold [this message]
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=202208111213.27BCDOfi019865@freefriends.org \
    --to=arnold@skeeve.com \
    --cc=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).