Mapping software Charles McKnight (14 Jul 2014 05:36 UTC)
Re: [TML] Mapping software Andrew Staples (14 Jul 2014 05:47 UTC)
Re: [TML] Mapping software Kurt Feltenberger (14 Jul 2014 11:43 UTC)
Re: [TML] Mapping software Peter Berghold (14 Jul 2014 15:31 UTC)
Re: [TML] Mapping software Kurt Feltenberger (14 Jul 2014 16:50 UTC)
Re: [TML] Mapping software David Shaw (15 Jul 2014 22:31 UTC)
Re: [TML] Mapping software Peter Berghold (15 Jul 2014 22:52 UTC)
Re: [TML] Mapping software David Shaw (16 Jul 2014 06:50 UTC)
Re: [TML] Mapping software Peter Berghold (16 Jul 2014 12:53 UTC)
Re: [TML] Mapping software Peter Berghold (16 Jul 2014 17:41 UTC)
Re: [TML] Mapping software Knapp (20 Jul 2014 19:45 UTC)
Re: [TML] Mapping software Bruce Johnson (14 Jul 2014 17:00 UTC)
Re: [TML] Mapping software Peter Berghold (14 Jul 2014 17:33 UTC)
Re: [TML] Mapping software Bruce Johnson (14 Jul 2014 18:29 UTC)
Re: [TML] Mapping software Tim (15 Jul 2014 03:46 UTC)
Re: [TML] Mapping software Bruce Johnson (15 Jul 2014 16:17 UTC)
Re: [TML] Mapping software Bruce Johnson (24 Jul 2014 18:56 UTC)
Re: [TML] Mapping software Carlos (01 Aug 2014 21:15 UTC)
RE: [TML] Mapping software Anthony Jackson (15 Jul 2014 16:31 UTC)
Re: [TML] Mapping software Evyn MacDude (14 Jul 2014 21:44 UTC)

RE: [TML] Mapping software Anthony Jackson 15 Jul 2014 16:31 UTC

From: Tim
>
> One nice thing about Postscript is that it's a programming language in
> its own right.  For one project long ago, I wrote a sector hex mapper
> in Postscript: put the data in tables within the file, and sent the
> thing straight to the (Postscript) printer.

Heh. I taught myself postscript for my trade map project, though most of the logic is in c.